Honeymonster's Lair

another post about my dabblings with fotobook, this time to announce my publishing of a patch which adds thickbox support to fotobook 3.1.5.

See the page of the same name for the latest download: WordFotobook. Basically, I’ve made minor modifications to the Wordbook and Fotobook plugins to wordpress. These mods allow both plugins to operate simultaneously by virtue of their sharing of the Facebook library in a common location, rather than (as shipped) using their own internal versions which conflicted by redeclaring the same class names.

As part of my ongoing efforts to improve my blog site; I have moved from hosting it myself on a system at home to having it hosted by XYZ Internet (my own entity) on a premium hosting package, and now it is hosted for FREE by the combined might of IND-Web.com and XYZ Internet using the socially aware hosting platform that we are developing together.

Martin of our sister company has written a nice howto for setting up wordpress cron jobs to run properly when using services similar to our own, which prevent loopback access to the same machine. The way that wordpress usually runs, is that when a user clicks onto your site after the scheduled time for cron to be fired has gone past the engine opens a loopback http request to itself. This is to prevent needlessly locking up the server leaving the user staring at a blank screen while pingbacks are fired before they see the page. This means that when services are configured like XYZ Internet’s and IND Web’s servers, the wp-cron just times out and doesn’t fire any pingbacks or do any other maintenence commands. The solution is to add a system scheduled command which uses the commandline php interpreter to call the wp-cron page directly. XYZ Internet and IND Web’s system allows 3 of these scheduled commands, so the cron can be fired once every 20 minutes.