Site Config

I disabled some experimental features:

disabled feature_charts
disabled feature_drawings
disabled feature_friends
disabled feature_games
disabled feature_mailin
disabled feature_mobile
disabled feature_sheet

I enabled blog comments:
enabled feature_blogposts_comments

List authors in wiki pages: disabled to make cleaner

Since TikiWiki 2 supports more than one PHP Layers menu at a time, there was no need to continue using the filtering code in the menu module, so it was commented out and can be deleted. I also updated the menu demo pages and in particular removed the tables showing browser and theme behavior. I believe the menus work fine in all compatible themes and in all browsers.

The next step will be to add demos and docs for CSS (suckerfish) menus.

As we move toward making Site Identity activated by default, I've found that SI custom code needs to vary quite a bit depending on the theme. To accomodate this here at the theme demo site, I replaced the one-code-for-all data input in the SI configuration page with an include statement:

missing page for plugin INCLUDE

Now there can be a sicustomcode.tpl file in a theme's template directory if that theme needs its own SI custom code. I realize this is a step backward from the no-template-editing, Web-based customization emphasis of Site Identity, but something like this is needed at a site that has SI enabled and uses and needs to accomodate multiple themes. I have more themes in the pipeline that need to specify unique SI custom code.

In future theme releases, which will all use SI, a sicustomcode.tpl file will be included. Users can either use the include statement method, or paste the content of the file into the SI custom code textarea and then edit it as they want. The tpl file will be a backup/reference in that case.

-- Gary

greenmetal.css & jello.css were missing from Theme-o-rama module

and Gary added BRTiki.css lately

I just removed vidiki.css because it's being pulled out of Tiki. (broken & unmaintained)

Hi!

I spent several hours making sure we could access/test all menu types with all the themes on this site.

We have 4 menu types:

• Basic menu
• Tree menu
• Dynamic vertical menu
• Dynamic horizontal menu

On this site, we have

• 7 new themes
• 20 legacy themes
• 34 bundled themes

For a total of 61 themes.

4 x 61 = 244 combinations!

And each of these combinations needs to be tested with several browsers

PhpLayersMenu horizontal -> phplayersmenu horizontal
PhpLayersMenu vertical -> phplayersmenu vertical

Why?

Most places in Tiki, page names are case insensitive, which is good. But I was having trouble with some Smart code in modules. It wasn't always doing what I wanted.

The plus (+) vs space ( ) also can cause confusion.

DogFood:
tiki-view_chart.php?chartId=1

Doc:
http://doc.tikiwiki.org/Charts

Bugs/RFEs
http://dev.tikiwiki.org/Charts

So when you are logged in, you will have a link to see what the template (.tpl) looks like. You can't change it however.

Note to Tiki devs: we need to check that this works as expected everywhere.

There are over 100 of these changes which must be done:

{if $feature_view_tpl eq 'y'}

->

{if $feature_view_tpl eq 'y' and $tiki_p_view_templates eq 'y'}

{if $feature_edit_templates eq 'y'}

->

{if $feature_edit_templates eq 'y' and $tiki_p_edit_templates eq 'y'}

Similarly, for editing the CSS, the feature needs to be on and the permission given

{if $feature_editcss eq 'y' and $tiki_p_create_css eq 'y'}