First time here? Check out the FAQ!
1

Signin template is ignored

Hi, how do I skin the signin/signout templates?

The files from the templates directory are ignored!

Thanks in advance.

s's avatar
11
s
updated 2011-03-05 08:23:00 -0500, asked 2011-03-05 08:22:30 -0500
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

1 Answer

0

Hey, sorry for the delay. The way templates are read is different from Django standard, because there is an attempt to implement skin support.

Skin is composed of templates and media. At this time edit the default skin directly and keep your changes in git - this is the most sane way to customize skin and at the same time be able to upgrade them. Try to do as much as possible in the file style.css. The template signin is askbot/skins/default/templates/authopenid/signin.html.

What do you want to change? If you need to enable/disable certain login providers - there will be such function by Monday.

Some older answers that you will find for query "skins" or "customization" may help you, but if something is not clear - please do ask.

Thanks.

Evgeny's avatar
13.2k
Evgeny
updated 2011-03-05 12:00:54 -0500, answered 2011-03-05 11:59:08 -0500
edit flag offensive 0 remove flag delete link

Comments

Thanks for the answer. But the problem is that I forked the initial `default` skin, renamed it and start working on it. The code is in bzr, but I can put it on github if you really want to have a look: http://bazaar.launchpad.net/~sushkov/ubuntu-website/light-askbot-theme/files It looks basically like this: http://intreaba.ubuntu.ro/questions/ (Work in progress...)
s's avatar s (2011-03-06 06:39:09 -0500) edit
And doesn't matter what I change in `askbot/skins/default/templates/authopenid/signin.html` it doesn't show up (just renders the old `default` file)...
s's avatar s (2011-03-06 06:43:31 -0500) edit
Most likely it is using a copy from your forked skin, it contains that file as well. You will save yourself a lot of trouble if you put your custom skin in the place of default and keep it in git, I know it sounds strange, but being able to merge skin upgrades helps a lot. Imagine in askbot skin javascript changes tomorrow - you will not be able to use that unless you copy the changed files manually. Also, templates themselves, in particular question.html and user profile will change. The bottom line is that until the templates are considered "stable" use of git is the only reasonable method.
Evgeny's avatar Evgeny (2011-03-06 12:34:22 -0500) edit
In your skin design one more thing seems to be missing - when you enter search query - the page is rendered by the javascript. Unfortunately at this point any layout changes in html must be replicated in the javascript (file live_search.js - there are several functions with name starting with prefix render_ , it is not too difficult though). Also in some places tags are deletable - notably when you search by tags - somehow that is lost on your site.
Evgeny's avatar Evgeny (2011-03-06 14:01:55 -0500) edit
Thanks. I know about lack of styles for delete buttons, and I also merged the new live-search, and in fact, I'm ready to make merges every time a new version comes out, Im just trying to understand why it has to be the `default` theme...
s's avatar s (2011-03-06 15:42:36 -0500) edit
add a comment see more comments