<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>Serendipity - Plugins</title>
    <link>http://blog.s9y.org/</link>
    <description>The official Serendipity blog</description>
    <dc:language>en</dc:language>
    <admin:errorReportsTo rdf:resource="mailto:" />
    <generator>Serendipity 1.3-alpha1 - http://www.s9y.org/</generator>
    <managingEditor>Jannis Hermanns jannis@gmail.com</managingEditor>
<webMaster>Jannis Hermanns jannis@gmail.com</webMaster>
<pubDate>Fri, 16 May 2008 14:33:42 GMT</pubDate>

    <image>
        <url>http://blog.s9y.org/templates_s9yorg/default/img/s9y_banner_small.png</url>
        <title>RSS: Serendipity - Plugins - The official Serendipity blog</title>
        <link>http://blog.s9y.org/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>Netmirror.org Outage, Spartacus affected.</title>
    <link>http://blog.s9y.org/archives/194-Netmirror.org-Outage,-Spartacus-affected..html</link>
            <category>Announcements</category>
            <category>Development</category>
            <category>Plugins</category>
    
    <comments>http://blog.s9y.org/archives/194-Netmirror.org-Outage,-Spartacus-affected..html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=194</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=194</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;As of today, the netmirror.org server seems to be having a hiccup. The serendipity Plugin &lt;em&gt;Spartacus&lt;/em&gt; by default requires this server to provide automatic plugin and theme updates and downloads. The inavailibility of this server can lead to timeouts and not being able to install new plugins.&lt;/p&gt;

&lt;p&gt;The issue should resolve itself once netmirror.org is up again. Temporarily you can either reconfigure your Spartacus-plugin to use the SourceForge-Mirrors, or completely disable the Spartacus plugin. Using the &lt;em&gt;s9y.org&lt;/em&gt; mirror will not help you, as this server is currently not hosting any files.&lt;/p&gt;

&lt;p&gt;I will post an update once the server is up again. Sorry for the inconvenience.&lt;/p&gt;  
    </content:encoded>

    <pubDate>Fri, 16 May 2008 16:33:42 +0200</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/194-guid.html</guid>
    
</item>
<item>
    <title>Spamblock and blogg.de blacklist</title>
    <link>http://blog.s9y.org/archives/188-Spamblock-and-blogg.de-blacklist.html</link>
            <category>Development</category>
            <category>Infrastructure</category>
            <category>Plugins</category>
    
    <comments>http://blog.s9y.org/archives/188-Spamblock-and-blogg.de-blacklist.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=188</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=188</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;The Serendipity Anti-Spam plugin allows to utilize the blogg.de IP blacklist service to block spam. Their service seems to have ceased existence, or at least is rejecting connections. This can lead to comments to your serendipity blog to be rejected. You can easily disable the blogg.de blacklist service in your Anti-Spam plugin configuration.&lt;/p&gt;

&lt;p&gt;Note that this option is by default disabled in Serendipity since blogg.de announced that they are no longer actively maintaining the blacklist. A well fit alternative to this service is the &lt;a href=&quot;http://www.akismet.com/&quot;&gt;Akismet API&lt;/a&gt;, which the spamblock plugin also supports.&lt;/p&gt;  
    </content:encoded>

    <pubDate>Sat, 08 Dec 2007 10:16:00 +0100</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/188-guid.html</guid>
    
</item>
<item>
    <title>SEO and meta tags for s9y, updated plugin</title>
    <link>http://blog.s9y.org/archives/186-SEO-and-meta-tags-for-s9y,-updated-plugin.html</link>
            <category>Plugins</category>
    
    <comments>http://blog.s9y.org/archives/186-SEO-and-meta-tags-for-s9y,-updated-plugin.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=186</wfw:comment>

    <slash:comments>6</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=186</wfw:commentRss>
    

    <author>carlgalloway@gmail.com (Carl Galloway)</author>
    <content:encoded>
    Recently there has been a lot of discussion about using SEO on Serendipity powered blogs, which has resulted in at least one plugin update and many suggestions for SEO improvements in templates.
&lt;br /&gt;&lt;br /&gt;
The meta description event plugin has been updated by Don Chambers, Jude Anthony and Garvin Hicking, and now provides a separate title, meta keywords, and meta description on a per entry basis, as well as a default title and description for all other pages.
&lt;br /&gt;&lt;br /&gt;
Previously users were only able to adjust the meta keywords and description per entry, and other pages would miss out, leading many users to install the HTML head nugget as well if they wanted meta keywords and descriptions on overview pages.
&lt;br /&gt;&lt;br /&gt;
Don has written up a full description of the &lt;a href=&quot;http://www.optional-necessity.com/archives/3-Better-search-results-with-meta-details.html&quot;&gt;updated meta description plugin&lt;/a&gt; on his own site, and is promising to continue developing plugins and templates, so bookmarking his site might be a great idea.  
    </content:encoded>

    <pubDate>Tue, 13 Nov 2007 08:54:49 +0100</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/186-guid.html</guid>
    
</item>
<item>
    <title>Your help in sorting serendipity plugins</title>
    <link>http://blog.s9y.org/archives/180-Your-help-in-sorting-serendipity-plugins.html</link>
            <category>Announcements</category>
            <category>Development</category>
            <category>Infrastructure</category>
            <category>Plugins</category>
    
    <comments>http://blog.s9y.org/archives/180-Your-help-in-sorting-serendipity-plugins.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=180</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=180</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;Like &lt;a href=&quot;http://blog.s9y.org/archives/176-Feedback!.html&quot;&gt;announced earlier on the serendipity blog&lt;/a&gt;, fellow usability expert Joachim Harloff is currently trying to improve the listing of Serendipity Plugins so that they are more accessible to users.&lt;/p&gt;

&lt;p&gt;He needs your help to fulfill them. Initially he planned to personally meet with serendipity users, but this proved more complex than initially hoped. Thus he has created a smaller, text-based version of it.&lt;/p&gt;

&lt;p&gt;You can download the file at &lt;a href=&quot;http://www.softuse.com/serendipity_sorting.zip&quot;&gt;http://www.softuse.com/serendipity_sorting.zip&lt;/a&gt;. It contains detailed instructions. You can also feel free to personally contact Joachim about any questions you have.&lt;/p&gt;

&lt;p&gt;Joachim estimates this questionnaire to take you about 1,5 hours of your time. You could greatly help to improve the serendipity usability, so please participate! Joachim wants to evaluate your responses starting on September the 8th.&lt;/p&gt;  
    </content:encoded>

    <pubDate>Thu, 16 Aug 2007 10:20:05 +0200</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/180-guid.html</guid>
    
</item>
<item>
    <title>Serendipity 1.1.4 released, security bug in entryproperties plugin</title>
    <link>http://blog.s9y.org/archives/178-Serendipity-1.1.4-released,-security-bug-in-entryproperties-plugin.html</link>
            <category>Announcements</category>
            <category>Plugins</category>
            <category>Security</category>
    
    <comments>http://blog.s9y.org/archives/178-Serendipity-1.1.4-released,-security-bug-in-entryproperties-plugin.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=178</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=178</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;Thanks to Erich Schubert, we were made aware of a bug and security issue in the Plugin &lt;strong&gt;Extended properties for entries&lt;/strong&gt;. Since this plugin is delivered with the core release, we have created a new Serendipity release for both the current stable 1.1 version tree, as well as a new 1.2 beta version.&lt;/p&gt;

&lt;p&gt;Serendipity Users that are using the mentioned plugin do not need to upgrade the full release, they can just fetch the updated version of the plugin through &lt;a href=&quot;http://svn.berlios.de/viewcvs/*checkout*/serendipity/trunk/plugins/serendipity_event_entryproperties/serendipity_event_entryproperties.php?rev=1831&quot;&gt;this direct link&lt;/a&gt;. Put that updated file into your &lt;strong&gt;plugins/ serendipity_event_entryproperties/ serendipity_event_entryproperties.php&lt;/strong&gt; file.&lt;/p&gt;

&lt;p&gt;The actual bug was, that people were able to deliver custom entryproperties settings to the Serendipity Frontend via a HTTP-Request, which made them able to bypass a possibly used passwort protection. Any other restriction of viewability of entries done via category read-privileges were not affected, though.&lt;/p&gt;

&lt;p&gt;Bottom line is: If you are using password protection for entries, this security update is mandatory for you. Also if you were generally using the entryproperties plugin (which is not installed by default in Serendipity), you are urged to update your plugin. Only people not using this plugin need not care about this issue.&lt;/p&gt;

&lt;p&gt;You can download the new full releases as always on &lt;a href=&quot;http://www.s9y.org/12.html&quot;&gt;the Serendipity download page&lt;/a&gt;.&lt;/p&gt;  
    </content:encoded>

    <pubDate>Wed, 08 Aug 2007 11:14:34 +0200</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/178-guid.html</guid>
    
</item>
<item>
    <title>Show staticpages via smarty function</title>
    <link>http://blog.s9y.org/archives/172-Show-staticpages-via-smarty-function.html</link>
            <category>Plugins</category>
    
    <comments>http://blog.s9y.org/archives/172-Show-staticpages-via-smarty-function.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=172</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=172</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;I upgraded the staticpage plugin in CVS to version 3.50 yesterday (which should be available via Spartacus now already).&lt;/p&gt;

&lt;p&gt;It now supports to use a custom smarty function to show static pages. This can be used in your custom template files (like the userprofile .tpls) to emit specific staticpages depending on variables.&lt;/p&gt;

&lt;p&gt;Go ahead and play with it. The API is quite basic and described in the new &#039;smarty.inc.php&#039; file. It basically works like this:&lt;/p&gt;

&lt;p&gt;{staticpage_display template=&quot;$TEMPLATE&quot; pagevar=&quot;$PAGEVAR&quot; id=&quot;$ID&quot; permalink=&quot;$PERMALINK&quot; pagetitle=&quot;$PAGETITLE&quot; authorid=&quot;$AUTHORID&quot; query=&quot;$QUERY&quot;}&lt;/p&gt;

&lt;p&gt;The API is quite fundamanetal right now. If you want to access more properties/parameters, please let me know, and I&#039;ll implement them. Please discuss this feature on our forums in &lt;a href=&quot;http://board.s9y.org/viewtopic.php?p=57362&quot;&gt;this thread&lt;/a&gt;.&lt;/p&gt;
  
    </content:encoded>

    <pubDate>Thu, 14 Jun 2007 12:37:00 +0200</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/172-guid.html</guid>
    
</item>
<item>
    <title>OpenID - Testing help needed</title>
    <link>http://blog.s9y.org/archives/167-OpenID-Testing-help-needed.html</link>
            <category>Development</category>
            <category>Plugins</category>
    
    <comments>http://blog.s9y.org/archives/167-OpenID-Testing-help-needed.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=167</wfw:comment>

    <slash:comments>4</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=167</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;rrichards from the forums published his first public OpenID-Plugin results. Check out &lt;a href=&quot;http://board.s9y.org/viewtopic.php?t=9836&quot;&gt;this thread&lt;/a&gt; on the forums. If you&#039;re interested in testing the plugin or are interested in OpenID, please give it a look and report about it.&lt;/p&gt;

&lt;p&gt;Many thanks to rrichards and all volunteers!&lt;/p&gt;  
    </content:encoded>

    <pubDate>Wed, 09 May 2007 11:51:03 +0200</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/167-guid.html</guid>
    
</item>
<item>
    <title>Serendipity 1.0.4 released!</title>
    <link>http://blog.s9y.org/archives/154-Serendipity-1.0.4-released!.html</link>
            <category>Announcements</category>
            <category>Development</category>
            <category>Plugins</category>
            <category>Security</category>
    
    <comments>http://blog.s9y.org/archives/154-Serendipity-1.0.4-released!.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=154</wfw:comment>

    <slash:comments>4</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=154</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;This new Serendipity release addresses a local file inclusion security issue discovered yesterday. It was possible to give a special parameter to a serendipity file to include a file on your own web-tree (or other files the webserver has read access to). If used on clear-text files, this could be used to disclose information like the apache logfiles on your website.&lt;/p&gt;

&lt;p&gt;This error can only happen in a scenario with two prerequisites: Register_Globals needs to be turned on in your PHP configuration AND your webserver must ignore the default Serendipity .htaccess file. This .htaccess file usually prevents to directly call Serendipity&#039;s include files via HTTP. Thus we feel that only a very low percentage of installations should be affected by this bug.&lt;/p&gt;

&lt;p&gt;However, Serendipity 1.0.4 is a &lt;strong&gt;recommended upgrade for everyone taking security responsibly&lt;/strong&gt;, like we do. We are thankful to the community for inspecting Serendipity, searching for bugs and security issues and reporting them to us. In this case, many thanks to &lt;a href=&quot;http://www.s9y.org/forums/viewtopic.php?t=7922&quot;&gt;Majestic from the forums&lt;/a&gt; for notifying us.&lt;/p&gt;

&lt;p&gt;Most of the plugins (both bundled and available via spartacus) were upgraded to also circumvent that bug, so you should upgrade all of your active plugins to the recent versions as well.&lt;/p&gt;

&lt;p&gt;The Serendipity 1.1 release tree was also modified with a patch for this issue. It will be contained in todays snapshot, and the 1.1-beta6 release file. The easy steps to perform an upgrade are documented in our FAQ on http://www.s9y.org/.&lt;/p&gt;  
    </content:encoded>

    <pubDate>Fri, 01 Dec 2006 10:37:00 +0100</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/154-guid.html</guid>
    
</item>
<item>
    <title>Freetag plugin: Automatted keywords</title>
    <link>http://blog.s9y.org/archives/153-Freetag-plugin-Automatted-keywords.html</link>
            <category>Plugins</category>
    
    <comments>http://blog.s9y.org/archives/153-Freetag-plugin-Automatted-keywords.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=153</wfw:comment>

    <slash:comments>4</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=153</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;Thanks to Robert from the forums he convinced me to implement a feature for him. Well, actually he &lt;a href=&quot;http://wishes.garv.in/&quot;&gt;bribed me&lt;/a&gt; to do it. ;-)&lt;/p&gt;

&lt;p&gt;Nevertheless, now that I implemented the feature, I kinda like it. The enhancement to the Freetag plugin (version 2.7, should be available via Spartacus now) allows you to enter a list of comma seperated keywords for each tag you have available on your blog.&lt;/p&gt;

&lt;p&gt;Whenever you save an article now, the plugin will analyze the content of your entry. For each keyword that you entered and that is found in the article, the corresponding tag will be auotmatically assigned to your entry (taking care that no duplicate tags happen).&lt;/p&gt;

&lt;p&gt;So, if you have the Tag &quot;PHP&quot; you could enter keywords like &quot;Serendipity,php,s9y,phpbb,xss,sesser&quot;. When you now create an entry where you use the keyword &quot;Serendipity&quot;, the freetag plugin will automatically assign the tag &quot;PHP&quot; to this entry.&lt;/p&gt;

&lt;p&gt;Thus, especially if you have a low count of tags you can save a lot of time by assigning meaningful keywords to your tags. Beware that if you enter a lot of keywords for a lot of tags, that this might slow down saving an entry. This happens because a list of EVERY available keyword needs to be compiled and matched against your saved article to be able to see which keywords were used.&lt;/p&gt;

&lt;p&gt;Have fun!&lt;/p&gt;  
    </content:encoded>

    <pubDate>Sun, 19 Nov 2006 21:26:00 +0100</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/153-guid.html</guid>
    
</item>
<item>
    <title>Updated Google Sitemap plugin</title>
    <link>http://blog.s9y.org/archives/150-Updated-Google-Sitemap-plugin.html</link>
            <category>Plugins</category>
    
    <comments>http://blog.s9y.org/archives/150-Updated-Google-Sitemap-plugin.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=150</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=150</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;Google seems to have changed their URLs where pings to the sitemap webmaster helper tool are sent to.&lt;/p&gt;

&lt;p&gt;Thus, the Serendipity Google Sitemap plugin requires you to either manually update to the right URL. The updated plugin in Spartacus has been committed today and should be available tomorrow.&lt;/p&gt;

&lt;p&gt;The new URL to use is: &lt;strong&gt;http://www.google.com/webmasters/tools/ping?sitemap=%s&lt;/strong&gt; (see &lt;a href=&quot;http://www.s9y.org/forums/viewtopic.php?t=7724&quot;&gt;this thread&lt;/a&gt;)&lt;/p&gt;  
    </content:encoded>

    <pubDate>Tue, 14 Nov 2006 19:16:16 +0100</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/150-guid.html</guid>
    
</item>
<item>
    <title>New plugin &quot;QuickNotes&quot;</title>
    <link>http://blog.s9y.org/archives/146-New-plugin-QuickNotes.html</link>
            <category>Plugins</category>
    
    <comments>http://blog.s9y.org/archives/146-New-plugin-QuickNotes.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=146</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=146</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;I&#039;ve committed a new plugin to Spartacus that allows users to use a very simply Notification System.&lt;/p&gt;

&lt;p&gt;Users can create text (HTML formatting configurable) that will appear on the Admin Backend. A small goodie is a feature that notifications are subject to specific usergroups - only the usergroups for which the creator intentionally posted the message will see it.&lt;/p&gt;

&lt;p&gt;The plugin also allows to configure whether normal users are allowed to use the messaging system. In the future this could be enhanced for more granular control, but for the time being it should proove a nice tool. The display of the messages can be controlled via a bundled notes.css CSS file.&lt;/p&gt;

&lt;p&gt;CSS formatting also allows to format new incoming messages differently. Now try it out and have fun&lt;/p&gt;  
    </content:encoded>

    <pubDate>Tue, 17 Oct 2006 13:14:00 +0200</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/146-guid.html</guid>
    
</item>
<item>
    <title>Plugin Execution Permissions</title>
    <link>http://blog.s9y.org/archives/141-Plugin-Execution-Permissions.html</link>
            <category>Development</category>
            <category>Plugins</category>
    
    <comments>http://blog.s9y.org/archives/141-Plugin-Execution-Permissions.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=141</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=141</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;Despite my downtime, I was able to find the time to commit some changes I was having up my sleeve to the 1.1 beta version.&lt;/p&gt;

&lt;p&gt;It involves, what many people have asked for: Specify, which user/usergroups are able to have access to certain plugins. My standpoint until now was, that plugins should implement the versatile permission management of Serendipity, available since version 0.9.&lt;/p&gt;

&lt;p&gt;However, reality got me when I saw that no plugin was really ported yet to use that permission management setup to provide custom permission sets. But people wanted to have the ability to say &quot;The staticpage plugin is only available to user XY&quot;.&lt;/p&gt;

&lt;p&gt;Thus, I implemented a rather hackish way into the groupmanagement: You can now specify complete plugins, or specific event hooks which are forbidden for a usergroup. This way, you can say that group X is not allowed to execute a &#039;Staticpage&#039; plugin.&lt;/p&gt;

&lt;p&gt;This approach should work quite well for many usage scenarios - the upside is, that all old plugins are supported instantly. However, the neater approach of course is to modify plugins so that they provide their own permissions for more granulate control of what you want to achieve.&lt;/p&gt;

&lt;p&gt;To enable this functionality you must first enable the option &quot;Enable Plugin ACL for usergroups&quot; in the serendipity configuration. The reason why you must explicitly enable this is, because those plugin checks decrease the performance of the plugin API. Every executed plugin hook must be checked against the blacklist, and those checks would hurt bloggers that do not intent to use this feature. To satisfy everyone, you have an option for this.&lt;/p&gt;

&lt;p&gt;You can try the feature in the nightly builds created today, or using an SVN checkout. The feature is contained in 1.1-beta4.&lt;/p&gt;  
    </content:encoded>

    <pubDate>Thu, 24 Aug 2006 15:09:00 +0200</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/141-guid.html</guid>
    
</item>
<item>
    <title>Cronjob functionality</title>
    <link>http://blog.s9y.org/archives/135-Cronjob-functionality.html</link>
            <category>Development</category>
            <category>Plugins</category>
    
    <comments>http://blog.s9y.org/archives/135-Cronjob-functionality.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=135</wfw:comment>

    <slash:comments>9</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=135</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;Two new plugins have been added to CVS by me:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;serendipity_event_metadesc / &quot;HTML META-Tags&quot;&lt;/strong&gt; allows you to define meta-description and meta-keywords per entry. Those will then be shown on the detailed entry page within the HTML head. As a nice bonus, if you leave the fields empty, the plugin tries to auto-detect keywords and description based on your text. For that it evaluates Bold/Strong tags in HTML to auto-guess your content.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;serendipity_event_cronjob / &quot;Cronjob scheduler&quot;&lt;/strong&gt; finally offers some cronjob functionality that people have sometimes requested. A lengthy explaination of this plugin follows. :-)&lt;/p&gt;
 &lt;p&gt;For anyone that does not know what &quot;Cronjobs&quot; are: This is a service, one of the UNIX/LINUX server oldies, that permanently runs on a webserver and executes scheduled scripts at a given time/period. With this you can setup repetitive tasks, like to purge all your SPAM E-Mails every day.&lt;/p&gt;

&lt;p&gt;Now, such cronjobs usually require you to have administrative privileges on the server where it is operated on. The Cron Daemon needs to run all the time, because only then it can execute a job at the exact configured time. Now a common use some people want is: &quot;Fetch my E-Mail account every day to see if there are mails that shall get blogged!&quot;.&lt;/p&gt;

&lt;p&gt;If you only own a usual PHP webspace, this will get problematic. You cannot create cronjobs there, and since PHP only gets activated when someone visits your blog, you can&#039;t really say &quot;Execute this script at 00:00&quot;, because you don&#039;t know if your script is called at that time. This is the reason, why &quot;cronjobs&quot; are usually not encouraged to use on a PHP-basis.&lt;/p&gt;

&lt;p&gt;The best way it can be emulated is like this: Every page call to your serendipity Blog can contain an invisible image that your visitors call again and again, and each time the script is called, it calculates the difference between the last script call and will then check which cronjobs need to be executed.&lt;/p&gt;

&lt;p&gt;If your blog is low on visitors, this means that maybe a cronjob that is scheduled every 5 minutes would only get executed once an hour. There&#039;s nothing you can really do about that, unless you own a server were you can create a remote cronjob that calls WGET or similars on your URL, to fake regular visits to your blog.&lt;/p&gt;

&lt;p&gt;Now that the principle bheind this is clear, here&#039;s what the cronjob plugin does: It emits exactly the invisible picture, and servers up multiple plugin API hooks that other plugins can use. Currently, only the popfetcher (1.13) and aggregator (0.7) plugins support cronjobs. Once you have the cronjob plugin installed you can configure these plugins inseid their own configuration to be executed on the available cronjobs.&lt;/p&gt;

&lt;p&gt;Feedback about this functionality is appreciated. Be warned that this script of course creates extra requests to your blog. So if there&#039;s any way for you to setup &quot;real&quot; cronjobs, you are advised to do so.&lt;/p&gt;
 
    </content:encoded>

    <pubDate>Thu, 06 Jul 2006 14:41:00 +0200</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/135-guid.html</guid>
    
</item>
<item>
    <title>Lightbox, Thickbox, Lightbox2</title>
    <link>http://blog.s9y.org/archives/136-Lightbox,-Thickbox,-Lightbox2.html</link>
            <category>Plugins</category>
    
    <comments>http://blog.s9y.org/archives/136-Lightbox,-Thickbox,-Lightbox2.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=136</wfw:comment>

    <slash:comments>9</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=136</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;Yesterday, Andyman77 from the forums brought the &lt;a href=&quot;http://codylindley.com/Javascript/257/thickbox-one-box-to-rule-them-all&quot;&gt;Thickbox&lt;/a&gt; project to my attention. Using his plugin, I intermingled that with the existing &lt;a href=&quot;http://www.huddletogether.com/projects/lightbox/&quot;&gt;lightbox&lt;/a&gt; plugin so that you can now choose which JS library to use to format your links. Plus, lightbox2 got also added to the plugin.&lt;/p&gt;

&lt;p&gt;What, you don&#039;t know what Lightbox is? It&#039;s a nifty javascript that will transform links to images into small &quot;popup&quot; links. When you thus link to a thumbnail images (&amp;lt;a href=&quot;large.jpg&quot;&amp;gt;&amp;lt;img src=&quot;thumb.jpg&quot; /&amp;gt;), lightbox will take on that image link, and once clicked on it, the large image will be shown on your page instead in a separate browser window. It sounds boring when explained, so just go to the lightbox pages and look at their installations.&lt;/p&gt;

&lt;p&gt;The plugin installation is seamless, as all image links in serendipity will get automatically rewritten so that links from thumbnails will show up as lightbox links.&lt;/p&gt;

&lt;p&gt;Thickbox brings fun into this thing by offering to also popup HTML links inside neat popups. Just add a &#039;class=&quot;thickbox&quot;&#039; attribute to your HTML links in your entries, and that&#039;s it.&lt;/p&gt;  
    </content:encoded>

    <pubDate>Wed, 05 Jul 2006 14:54:46 +0200</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/136-guid.html</guid>
    
</item>
<item>
    <title>Using Serendipity with Flock</title>
    <link>http://blog.s9y.org/archives/132-Using-Serendipity-with-Flock.html</link>
            <category>Plugins</category>
    
    <comments>http://blog.s9y.org/archives/132-Using-Serendipity-with-Flock.html#comments</comments>
    <wfw:comment>http://blog.s9y.org/wfwcomment.php?cid=132</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://blog.s9y.org/rss.php?version=2.0&amp;type=comments&amp;cid=132</wfw:commentRss>
    

    <author>mail@garv.in (Garvin)</author>
    <content:encoded>
    &lt;p&gt;Basically, Serendipity should support the &lt;a href=&quot;http://www.flock.com&quot;&gt;Flock&lt;/a&gt; browser.&lt;/p&gt;

&lt;p&gt;Sadly, due to a bug in their parsing/sending routine, applications that rely on PEARs XML-RPC extension won&#039;t work with flock. Serendipity falls under that category. It would work without flock auto-detecting a blog, but because flock&#039;s autodetection is blocking to successfully add Serendipity, this is a devil&#039;s circle.&lt;/p&gt;

&lt;p&gt;This flock bug had been reported in February, but sadly no progress has yet been made. All the people who&#039;d might like to use their Serendipity Blog and the XML-RPC posting plugin with Flock, please raise your kind voice here:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://bugzilla.flock.com/show_bug.cgi?id=2754&quot;&gt;Flock Bugtracker&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I am pretty sure the nice people of Flock will report to popular demand - I&#039;d really like to see progress in this issue :)&lt;/p&gt;  
    </content:encoded>

    <pubDate>Mon, 26 Jun 2006 11:42:49 +0200</pubDate>
    <guid isPermaLink="false">http://blog.s9y.org/archives/132-guid.html</guid>
    
</item>

</channel>
</rss>