For anyone running a Wordpress site, you might want to check out the prerender plugin by jens persson. Instead of fetching content and performing the rendering when a page is requested, it renders the page the first time it’s requested and stores the prerendered content in the database. From then on, it just has to grab the prerendered stuff, rather than reapplying markdown, acronyms, validation, whatever rendering tools you use. It can really cut down server processing time for your page loads, and I haven’t noticed any rendering bugs yet.
One important note, though - if you use any <span id="more-111"></span> tags to split up your content, you’ll need this addition by mike lu. I did find a few bugs in that script… get my updated copy here and save with a php extension, replacing your prerender.php plugin.
Jens himself tried to comment here, saying he was going to update the plugin, while making it work with WP 1.5. Unfortunately, my spam plugin was a little overzealous and munched on his comment. Sorry jens. I think I fixed the plugin - it wasn’t syncing times correctly, making the server think it was a spammer.
January 19th, 2005, at 10:08 pm #No problem, I know the spam blues too.
I have started to update the plugin, first by moving it to wp-plugins.org and importing all old versions into svn. The next step is adding support for 1.5 but first I have to learn how to handle branches in svn.
January 21st, 2005, at 10:21 am #Unfortunately, I’ve just had nothing but problems with spam plugins. Both Spam Karma and Spaminator are eating every comment people try to post. I’ve disabled them for now, hoping that my own spam killing methods will be enough. If not, I’ll try plugins again, but for now I don’t want to risk it. (Sorry again jens =/)
January 21st, 2005, at 10:23 am #btw, svn is great - branches are just like copying a directory. No trickery like cvs…
January 21st, 2005, at 10:25 am #