Plugin Status: Busy with work :(

All quiet on the western front recently. I started a new freelance web development job in April and have been quite busy with that and my teaching job, so development on WordPress Subdomains has ground to a halt.

I hope to get back on it sometime this week. I’ve decided that 0.6.2 will be mainly fixing bugs and other minor issues. New features will come in 0.7.0 which will probably be the next release after 0.6.2.

One thing has come to my attention is that the use of the wordpress get_posts function was a big mistake. Using less custom SQL and more wordpress API calls seemed like the right thing to do. Unfortunately they didn’t have a function that gave me exactly what I wanted and get_posts is basically overkill. My use of it has caused memory problems and increased SQL queries quite a bit. I suspect a lot of the extra sql calls are actually caused by other plugins that make use of the filters whenever posts are fetched. They think I’m using the get_posts to fetch posts to generate a page, not that I’m fetching posts to make use of their data. I’ve already run into this problem with one plugin which I pointed out to the developer and now has a fix in it’s development trunk. I can’t investigate every plugin, so I’m just going to have to go back to using custom SQL and drop my use of get_posts. If you’re experiencing problems due to this then search for WPS_CUSTOM_GET_POSTIDS in the readme file.

Another problem is that attachments to posts end up being linked back to the main domain even if clicked on in a subdomain. I’ve had a request that these be kept on the subdomain you’re on. I think I’ll make this an option as it may lead to duplicate content (which may cause SEO issues).

I’ll try and get these two pieces fixed in the next week and see if there are any other things that need fixing out there. Please let me know if you can think of anything.