[geeklog-devel] 1.3.10 to do list

[Tony Bibbs]

Dirk Haun wrote:

>Inclusion of the SpamX plugin - what's the status here? We probably need
>a new plugin API function so that plugins can filter or reject comments
>before they will be saved. Also, a method to make it easier to package
>plugins with Geeklog would be nice, e.g. by making the install script
>read the SQL for the plugin from some predefined directory (if we do
>that, it also needs to be able to handle plugin updates).
>  
>
I say add something like the following:
PLG_preSaveComment_<pluginName>
PLG_postSaveComment_<pluginName>
PLG_preSaveStory_<pluginName>
PLG_postSaveStory_<pluginName>

The first one is the one we needed the most.  I figured adding a 
postSaveComment would complete the cycle, though, I can't think of an 
immediate use for it now.  I also added the two story-related methods as 
I don't think it would be a stretch to think someone may want those at 
some point.  Just a suggestion...we can simply add the one and worry 
about the rest as needed...I just figured we might try being a bit more 
proactive by adding a few more.

>PDF: Currently, the PDF-related files all produce XHTML, which is
>inconsistent with the rest of Geeklog which produces plain ol' HTML. From
>the documentation, the PDF add-on doesn't understand XHTML either (but
>only HTML 3.2), so I don't see the need for this. Tony? Anything else
>that needs to be done on the PDF support?
>  
>
Agreed, I misunderstood that much.  With that, nothing else is really 
needed then.

>A few features have been mentioned in the past as being possibly ready to
>go into the next release. Most notably spell checking and archiving of
>old stories. Tony, Blaine - any updates?
>  
>
Count the spellchecker out.  I've dusted it off and have a few fairly 
big bugs that will take some time...not worth holding off the .10 release.

--Tony