Site Config

The XtratoVeil design has a header with four buttons. In the original design, these are part of a Flash file, but for Tiki I thought we should stay with normal HTML so site admins could customize it easily. The "screen" area on the right of the header gets its content from Look and Feel custom site header text area. To make the four buttons to the left of the screen easy to program, in the tiki-site_header_options.tpl file for this theme there is

< div class="site_header_right_button" id="site_header_right_button1" >
{wiki}{content label=siteheader_button1}{/wiki}
< /div >

(four times of course, once for each button). Then the site admin can go to the Dynamic Content system (tiki-list_contents.php) and make four items with labels "site_header_right_button1", etc., and program each of these with a link for something.

Only a few characters will fit in the button space, so probably an image should be used as an icon. These could actually be from the XtratoVeil design, or from FamFam or some other collection.

(The XtratoVeil theme is just about ready, and will probably be available when Tiki 4 is released.)

I upgraded the site and added new and updated themes. There is a page for each theme, mostly displaying an included Sample Page. I'll try to add specific information for the themes.

The docs for configuring Look & Feel in Tiki 2 need to be improved. This should be a doc.tw.o but maybe relevant info here also. And docs on theme modification need to be added for each theme, as necessary.

The phpl menu is too wide for a few of the narrow themes, so I'll make a narrower one and put in their templates.

Search: no longer have choice of features (feature_search_show_object_filter disabled). -> This will be good to test if themes handle this well.

Plus, I deleted a test blog.

Not all the theme files at this site have been updated to Tiki 5, and Tiki 5 itself is still in flux, so as the page-top note says, there could be some weirdness happening.

The Judy theme in particular needs updating. The site header items were overlapping the theme-switching module, which made escape from the theme problematic, so I moved that module down a position and moved Registration info up one. Now it should be possible to switch themes using the module even in the Judy theme.

-- Gary

Special thanks to Cyril who started translating to French!

http://themes.tikiwiki.org/tiki-all_languages.php?no_bl=y&page=Les+feuilles+de+styles+CSS

In my experience, the Infinite Carousel on the homepage, which displays theme images and download links, wasn't working correctly on the initial page load. The images were displaying side by side, making a really wide page. I checked this in several browsers and all showed the same problem.

The carousel works fine in a normal HTML page, so apparently the problem is due to something not loading initially. To see this, clear your browser caches and visit Tiki 3 Themes, the wiki page that holds the carousel now. For me anyway, in all my browsers, the images all display at once, left to right, and there's no motion, no apparent javascript happening for them. Notice also that the module-flip icons aren't there and and working (but do after a page refresh), which I think is another symptom of the same problem. (Of course if the carousel and module-flipping are working for other people on first page load in a cleared-cache browser, then I need to figure out what the difference is with my experience - and all my browsers have default javascript settings.)

As a workaround, I moved the carousel wiki lines from the homepage to Tiki 3 Themes, and edited header.tpl to load the necessary ))JavaScript(( and CSS on both pages. Then I made an iframe on the homepage with the carousel page as the source, using index_p so only the wiki content displays. (I tried using the INCLUDE plugin, which would have been a neater solution, but then the carousel page's head section doesn't load, which defeats the purpose of the second page.

Now I'm getting the effect I wanted - the carousel loads and works correctly on initial homepage display, but at the cost of a really kludgy workaround. I need to check with our experts about solving the problem of ))JavaScript(( not loading or anyway not being effective initially.