Thanks to Jerome who sent me a few patches, and Matt who noticed that the templates produced non-XHTML compliant pages, I am releasing 0.99.0 beta1. Documentation is still in the works, expect it for the final 0.99 release. There's still work to be done on trackbacks (they don't seem to work anymore here, they work on Jerome's site), but I hope we're not far from a stable release. As for speed, Jerome confirms my measurements of a 5x speed increase over a stock WP installation on his production site (2x on his development site). YMMV.
Wow, I made the contributors list in the default template! :)
Beta-1 looks good, although the % signs still need to be removed from the call to gmdate() in PostComment.php.
Hehe you're contributor #1 at the moment, Luca only worked on the feed page two months ago.
Will fix gmdate tonight from home. How did you spot all the bugs? Did you read the source code line by line, AND redesign your templates in one and a half days?
The template conversion didn't very long, really. Most of the bugs were spotted during the conversion - an advantage of having two different server setups.
And yes, I did a quick read-through! :)
I wanted to figure out how the heck your plug-ins work (pretty slick) and to determine where/how queries occur vs. template assignment - more thoughts on that later.
The size of WPFF was helpful, if it was the size of WordPress I wouldn't have gotten very much done this weekend.
:)
While you're at it, if you five minutes to spare give a thought to trackback: better leaving it as a separate file (easier for robots.txt) or merge it to the PostComment plugin?
Oh, there's another bug related to XHTML validation: multi-line comments are submitted with <br> (not <br />) as line breaks. A simple str_replace() fixed this on my site.
OMG, I changed PostComment to use your paragrapher() method, guess I haven't updated the site from CVS...
Guess I forgot to commit the plugin from the office, now it should be ok. Gonna wait a couple of days for the next release in case you find more bugs :)
Re: trackbacks, I haven't read through that one yet... :)
The URI would certainly be nicer if you used the same scheme as PostComment (that one took quite a while to figure out). E.g. http://qix.it/~ludo/wpff/post/unstable-099-beta1#trackback
Of course, you could also use mod_rewrite to achieve the same result. I would lean towards a solution that offers the most code re-use. Keep trackback.php, for instance, and somehow link it to the comment submission routine in PostComment.php. Then you only have to fix the gmdata() % signs in one place!
LOL! I was leaning towards the same solution, even though the request variable names are different, and I'm a bit too lazy to modify the comment forms and code :)
Make an "add comment" routine that takes the comment data as parameters and does all validation and the insert query. Then the trackback and PostComment routines can use it without worrying about request variable names and such.
Now that I've looked at it, trackback.php could use some internationalization too.
Just posted some additional WPFF info on my site, thought you might be interested. Still a few more issues to iron out before I make the complete switch, but but so far it's very promising.