Kommentare
New plugins: Markread, Showentries
Garvin am um :
Please read http://www.s9y.org/29.html for information about this. The plugins are hosted in CVS@SourceForge, not in SVN@BerliOS. SourceForge can take up to 24 hours to show new CVS plugins.
Serendipity 0.9 released
Garvin am um :
Hello all!
Thanks for the great and positive feedback, and of course for your best wishes :)
You keep us (..me...) going on!
Garvin am um :
Paul, Bugs an questions can be reported on our Forums at http://www.s9y.org/forums/ or in our Bugtracker. The link to that can be found on many places on www.s9y.org and in this blog on the right sidebar.
Your bug with Safari has been resolved a few weeks ago and will be part of an upcoming 0.9.1 release, but can also already be fetched through our nightly downloads.
Regards, Garvin
Serendipity 0.9-beta3 released
Garvin am um :
Spartacus would require full write-privileges on the whole s9y tree with all files, which would impose a security risk, so I'd rather not do this.
An idea of a user on the forums was to support automatted updating via FTP; this might be an option we'll look into in the future.
Regards, Garvin
Extended Properties for Entries: Custom Fields
Garvin am um :
I'm replying here in english, hope you don't mind.
Rembrandt asked, that it would be great if you could associate external plugins with the new CustomFields.
This is already possible! Your plugin can just hook into one of the events where entries are fetched ('entrydisplay' or 'frontenddisplay' or even 'frontend_entryproperties') and then just set your $eventData property index to what you want to be displayed later on.
However, this was already possible even before CustomFields got invented. You can add your very own plugin hooks easily into the entries.tpl template, like this:
{serendipityhookPlugin hook="customnow_playing" hookAll=true"}
Then just let your plugin to all the work. http://www.s9y.org/78.html describes this as well.
Regards, Garvin
garvin am um :
Please use the forum for support questions. It seems your error is coming from a bad PHP install. More on the forums.