Great - actually 1.0 should also have a validate() method that can check configuration errors. Any errors found then should be displayed natively in the interface...

That's good news! I'll have a look at the beta then and see if I can use that in my plugin :)

You are right, this really sounds ...

Hi Garvin,

Thanks for the info, I will use the templates_c folder then and create a subfolder for my plugin there.

Hi Garvin,

Thanks for the info! Items 1, 2 and 3 seem to be good solutions that one can choose depending on the type of error. I think plugin configuration issues can be checked via the example() method while functional errors can be mailed/displayed...

Otherwise, I don't like swallowing errors ...

Sure, outside the www-root is better for cache files, but automatically determining a folder location is not practical anymore then - the user has to set a path in the plugin's configuration then, and I would prefer to avoid that... I guess there is no other way unless Serendipity offered file ...

I a writing a plugin that needs to create a number of files for caching purposes as well as storing other data. Is there a standard location for plugins to save files to, or can I decide on my own where to put them? An ideal location would be any of those that have to be writeable for serendipity to ...

I have started writing a plugin, and was wondering how any errors occurring in the plugin should be handled. Ideally, any errors occurring in the plugin should not bubble up to the user nor halt the script. But how do you communicate the error 1) to the user 2) to the developer? Is there a standard ...