Ziyad has setup a Frappr-Group for Serendipity.
There people can register their own blog so that people can see, where in the world Serendipity is being used. Feel free to enlist yourself, so that we can see who's using us! ;-)
Thanks to Ziyad for notifying us about the service and for registering the group.
I've committed two new plugins to the repository. First the serendipity_event_markread ("Show read/unread state of entries for visitors"), which is a plugin that allows to you mark entries as read for your visitors. Just as the description says *g*. This is very usable for aggregator-sites; the plugin offers new smarty variables (look at the PHP code for info) so that you can custom style your entry layout depending on the read state of an entry.
You could, for example, show the extended body for all unread entries, and only show the first 20 characters for all read entries. Use the power!
The read state is saved in an additional DB table and sets a cookie to remember your visitor ID. If you're a registed author/user of a blog, it will set your cookie in a way that you can also log on to other computers where the read state will also be carried over to. As anonymous user, your read-state will be per-computer.
The second plugin is serendipity_plugin_showentries ("Show entries in sidebar"). It allows you to show an entry listing with body texts and so on of certain entries inside the sidebar. You can show entries of a specific category there, which makes it great for moblogging sidebars, where you can fetch all entries of a "Moblog" category
Have fun and a nice weekend, Garvin
Serendipity 0.9-beta3 has been released. This should be the last release candidate for Serendipity 0.9, which is scheduled to be out next Friday.
Fixed issues in beta3 are:
Updating from any Serendipity version is easy: Backup first, then extract the release files over your old installation, make sure the files .htaccess/serendipity_config_local.inc.php are writable, login to Serendipity and be guided through the automatic upgrade process.
Have a nice weekend, and thanks in advance for reporting bugs to us!
As a response to a Feature Request from Karotte, I have just committed an enhancement to the entryproperties plugin to 0.9-beta3 of our SVN (which will hopefully be turned into a 0.9 final at the end of this month).
The plugin configuration has now been altered so that you can add a comma-separated list of custom fieldnames, which you can then fill in when creating an entry.
That means, you can create two custom fields called Listening and Playing (don't use whitespace or special characters for fieldnames). Create an entry, and fill in values for those two fields. Now edit your entries.tpl template and place the Smarty Codes
Now listening to: {$entry.properties.ep_Listening}
Now playing: {$entry.properties.ep_Playing}
anywhere you like inside the entry loop. Remember to prefix your property keyname with ep_. Then you'll see those fields at the place you configured. You can also add the usual Smarty markup to check if a variable is empty, and add some DIV or other tags to surround your output.
This brings Serendipity a bit closer to CMS-features, once again. :-)
(The SVN nightlies will be built tomorrow, containing the new patch. SVN checkouts contain the change already at this time - users familiar with SVN only need to fetch the plugins/ serendipity_event_entryproperties/ serendipity_event_entryproperties.php file)
Serendipity 0.9 is still in beta-testing, but getting close to the final release. Thus a 0.9-beta2 version has been released, which mainly fixes two problems with beta1: Spartacus not indicating new plugin versions and the "easy installer" inserting invalid configuration values that lead to the dreadded "function serendipity_mb not found" error.
On top of that, the second beta contains:
Updating from any Serendipity version is easy: Backup first, then extract the release files over your old installation, make sure the files .htaccess/serendipity_config_local.inc.php are writable, login to Serendipity and be guided through the automatic upgrade process.
If all things go smoothly with the 0.9 betas (which it basically seems right now), you can expect a final release at the end of this month. We need your feedback, please testdrive the new version!