I’ve been wondering what sort of bug I’ve had in my WP installs for the last few weeks, and only now figured out what’s going on.The Turbo mode for WP is done through Google Gears. There’s a bug in the Turbo mode that will not allow you to change your blog’s theme. It works by not displaying the “x” (Close) or the “Activate …” options in the DHTML layer that opens up when you preview a theme.
Try it out if you want. Enable Turbo mode, then go to Design >> Themes and click on a theme that you’d like to preview and possibly activate. It’ll open as a full page instead of opening in a separate layer above the regular page, and the option to activate it will not display. In essence, you’re locked out of switching themes. You have to hit the Back button to get back to the Admin panel, else you’re stuck in a Live Preview mode.
This has nothing to do with file permissions, as I originally thought, or with corrupt theme files. No, it has everything to do with Turbo/Google Gears and the way WP implemented this. It’s a bug that needs to get fixed. The only way to enable theme-switching for now is to disable Turbo mode. After that, things work just fine.
This bug is present even in the latest WP version, 2.6.3. I hope it gets fixed soon.
One thought on “Cannot change WP theme if Turbo mode is enabled”
FYI, this is not really a bug as it is more of a cache methodology issue. This is pretty standard for all cache based technologies that, as a rule of thumb, you should turn OFF your cache technology (i.e. JSP, PHP Gears API or whatever) and/or reset your theme/framework engine on/off until your cache get’s cleared.
Kill your cache directory is another good way of getting a “real” update.
While WordPress should probably have a “clear cache” button or something similar, it probably isn’t there since caching is generally a production/advancement enhancement (for higher traffic sites or those who just want an increase) and you generally do not want to interrupt your speed enhancement just to preview themes on. This may seem silly to some but for those with LARGE sites, caching still has a (large) startup cost to your server for initial page loads.
Comments are closed.