These are of course my opinions, but ones that I think have some validity, as I've been involved with s9y as a user and plugin author since around version .05-06. First off, I agree heartily that branding is important. The efforts you've made are fantastic. The new wiki/portal/logo looks great, but ...

This is a permissions problem. Serendipity wasn't able to write its config file into the serendipity directory. What you need to do depends on your environment, but if you want a surefire solution, change that directory to have 777 permissions, and the same for the exising serendipity_config_local.i...

Probably another plugin (the serendipity markup?) is colliding with GeSHi, and overriding its behavior. The GeSHi plugin has no issue with the preprocesor directives in C. Try bumping the gehsi plugin up towards the top, and make sure it comes before the serendipity markup, bbcode and nl2br plugins ...

I get Fatal error: Cannot redeclare class pear in (real path removed) /bundled-libs/PEAR.php on line 86 displayed at the top after a number of plugins are displayed. The rest of the form is truncated, so there's nothing I can reallly do in the plugin area right now. Any help getting this functional ...

Discussed in detail here: http://www.gizmola.com/blog/archives/67-Serendipity-GeSHi-Plugin-update-.05.html I advise that people upgrade, both to get the latest version of the core geshi engine, and to get the numerous new language files. Ruby programmers for example, now have support for their code ...

I had to get my host to go in and reset permissions, etc. As far as I could tell, the fetched plugins were assigned an owner of 'nobody', hence I couldn't go in and change permissions. Weird... Thanks for the help Garvin! It's actually not weird at all, sounds like the apache server for your host r...

Ok, I feel like a goob after this :oops:. Did indeed turn out to be a perms issue, even though I was so *sure* I'd triple checked that. I was a bit flustered after wrestling with Gentoo emerge borking my entire apache configuration. I've finally got things working although I still can't say why they...

Garvin, Ok, I thought it was curious, but the real problem is that the files can't be written by spartacus, even though the plugin directory is 777. Is there anything you can think of that would cause this to happen? Notice: Cannot write to file /sites/gizmola.com/blog//plugins/serendipity_event_con...

I have been having problems with Spartacus attempting to upgrade existing plugins. Here's an example of the output of one failed upgrade: Trying to open URL package_event_en.xml... Fetched 140196 bytes from already existing file on your server. Saving file as /sites/gizmola.com/blog/templates_c/pack...

I suspect it may be a php memory issue. Try going into your php.ini file, and finding the memory_limit parameter. Increase that from 8m to 16m and see if that helps. Don't forget to restart apache.

That's defined in your language file. Look in the lang folder, and find the language file you're using. Assuming it's english, it's named serendipity_lang_en.inc.php.

Look for the define for 'VIEW_EXTENDED_ENTRY'. Change the verbage before the "%s" to be whatever you prefer.

Update on my problem: I finally figured out the problem on my server, and it was that the ttf files were corrupt. I'm not 100% sure how they got that way. I got them from cvs, and I verified that they were set to ascii, which of course is wrong. This would explain why they were garbage when I upload...

I just updated an installation, and there were no alerts I noticed. I'm guessing this is a problem when you have all the plugins installed including the additional group, and maybe not one that happens out of the box. As I'm assuming a lot of people will install the additional plugins, I'm guessing ...

I think it would be good to make this note visible, because I think this is going to be happening to a lot of people, and it will save a lot of head scratching.

Odd, I have had no problem with that plugin. Are you using the option that displays your output as an article? Are you sure you have the latest version of the plugin installed? That plugin had some changes added to it, so unfortunately, you might have to redo your static pages, although I'd start by...