I’ve managed to work out all the issues with WordPress 2.8.
This version should also spell an end to sql query and memory issues people might have seen in previous versions as I’ve replaced the use of get_posts() with custom sql.
Nothing much more to say other than please let me know if you find any issues with it. Now I’m off to bed 
Download: WP Subdomains 0.6.2
Everytime I fix one thing something else breaks.
Now for some reason rewrite rule filters aren’t being executed which means certain permalink settings wont work.
I’m hoping to get this sorted tonight, but it may be tomorrow as I was up very early to catch a bus from Singapore to Melaka this morning and then spent most of the afternoon wandering around in greater than 30 degree heat.
Anyway, fingers crossed I’ll run out of issues soon and be able to make a fully working release.
A quick update.
There was a fairly key change in WordPress 2.8 to when wordpress creates the default Taxonomies. It now does it at a time after when my plugin first needs them. It would be nice to just change my plugin to do it’s work after this. However, the part of the plugin that needs to change themes depending on the subdomain needs to run early because of the way wordpress has been written.
I have created a ticket on the wordpress bug tracker explaining my problem and asking if the way they first initiate the themes can be delayed at all (http://core.trac.wordpress.org/ticket/10160). I’m not sure what the outcome will be of this, I haven’t looked into it enough to know how vital it is that the themes are initiated at that precise point.
My backup option is that I’m going to have to come up with some custom SQL to get around the problem for now. I should be releasing this fixed version of the plugin tomorrow.
I will keep my fingers crossed that my feature request is accepted and then I can go back to using the nice wordpress API.
Check back in the next 24 hours for a WordPress 2.8 compatible version of the plugin.
Thanks to everyone who informed me about the plugin not working with WordPress 2.8.
Clearly this is quite serious. Luckily I’ve just finished my teaching job and I will look at this problem this weekend and try my best to have it fixed for Monday.
Also now I’ve finished working for the next 4 months updates to this plugin should continue again.
Thanks for hanging in there.
