7 Comments


  1. I am removing whole right hand side sidebar php file and instead hard-code all links in the div. Secondly I remove heaps of stuff from head php file manually disabling most line in function file. It’s faster. My one/single file runs Pages and Posts, it’s a longer theme file (ex file of standard wp theme that used to be in the wp pack) but it’s not too bad I update it with each new wp release.


  2. So far most of those features didn’t need a Plugin to be deactivated or controlled (revisions, admin bar, etc). As long as this keeps to be the case I’ll be ok but I think the core Plugin idea might has to be revisited and move some of those things out of WP core.


  3. I agree with Nicolas, so far I’ve added the required one line of code to limit post revisions in my config file and added a few lines tomy functions file do a few bits and bobs. But otherwise, the cleanr gallery plugin is the only plugin I use to fix what WordPress as done poorly (and I’m sure it won’t be needed for much longer).


  4. Same as Christine and Nicolas – Most of the new stuff is stuff I’ve wanted, or used plugins to punch around. While I did write a disabler plugin, I don’t actually use it myself. It was more an experiment in coding.


  5. Speed of delivery needs work. The more functions the more overhead. A better way to switch off functions in the deployment would be good so that it doesn’t even have to check a boolean switch.

    I would like to use caching but I rely on the Fraxion Payments plugin to sell my content. That means the page and post content has to be dynamic, so caching is right out.


  6. @Danny Freebie caching of whole pages is right out, but you can still manually build caching into your theme. Things like the current list of posts on the front page doesn’t change. The tag clouds can be cached.

    Caching doesn’t have to be an all or nothing thing. It just means you have to do some work to put it in place.

Comments are closed.