thought {TEMPLATE_PATH} was some kind of constant or variable.... never... Is the accidental overwrite really a risk? Can't really say .. but it is definitely better to make it an inner array by template name. You'll also never know if $serendipity['template_loaded_config'] wont be used for somethi...

Since the sync XLM file was ok, I investigated this sync issue down to netmirror.org, which hasn't synced the files yet - why ever. All other mirrors have. http://netmirror.org/serendipity/additional_plugins/serendipity_event_lightbox/serendipity_event_lightbox.php If you set your Spartacus mirror p...

Oh ... and since being an example for others too, it might be better( ! ) to replace all occurrences for get of $serendipity['template_loaded_config'] with $serendipity['template_loaded_config'][$serendipity['template']] and set it like this $template_global_config = array('navigation' => true); $te...

Right. Since outside the normal routine, you need to do this on your own in this case... case 'css': .... // load colorset file (with fallback scope) $tfile = serendipity_getTemplateFile($serendipity['template_loaded_config']['colorset'] . '_styles.css', 'serendipityPath'); // or the way defined you...

Don Chambers wrote:Was there a change in s9y recently, or have I been doing this wrong for awhile?

I don't think so... we just did not have that situation yet, I assume.
Its somehow related to serendipity_loadGlobalThemeOptions() I think and may be some referencing "issue"...

yellowled wrote:in case you need a reason to increment the version again.

Fine, but no good until Garvin had a look into the sync commands and their output again.

[It looked for me as of the xml file is not the same as before....]
Edit: I checked the xml and it looks good to me...

Oh - I see we were heading to some similar approach...
Using a constant is as much global too, I assume - but not as good as an additional $serendipity subarray.

yes, after. Still no good. Strange... I think I got it: function serendipity_plugin_api_event_hook($event, &$bag, &$eventData, $addData = null) { global $serendipity; switch($event) { case 'frontend_footer': echo "\n<!--PLUGIN API-->\n"; break; case 'css': // by file #echo file_ge...

Deshalb meine Frage: kann man bei dem von uns benutzten Theme, das wäre Bulletproof, nur auf der einen statischen Seite, wo die Tabelle ist, die rechte Seiten-Menüleiste abschalten, damit die Tabelle bis zum rechten Rand "Platz" hat ? Das hängt davon ab ob der mittlere Content wirklich ga...

Strange ... we should find out whats wrong and get Garvin to fix that..

Anyone else with the same?

Is the function placed in config.inc before or after the $template_loaded_config creation ? :) I should be placed below, IMHO. $template_global_config = array('navigation' => true); $template_loaded_config = serendipity_loadThemeOptions($template_config, $serendipity['smarty_vars']['template_option'...

Did it work by now..?

I thought I was onto something with this: [...] Problem I am having is that $template_loaded_config['colorset'] is empty, even though the config option is set to a selected color.... I've probably missed something really simple, but it is late, and I need sleep. Any suggestions appreciated. Yes, th...

Users should be able to override ANYTHING a theme offers, including the ability to override stylesheets other than style.css Again, since this being a very edge case, you still are able to do this (even when being loaded before), by using cascading styles with id / class specifity or even use the &...

I think everything is ok! Styles are added to serendipity.css by fallback, styles.css, plugins styles, user.css, and in this order. Every other styles are based to a user decision: a) by adding them manually to the index.tpl or b) by using a config option in the template config. Why should a user wa...