Get your themes from WordPress

It looks like WordPress has decided to revamp their theme directory and turn it into a fully fledged source repository. This is a step in the right direction and a possible route to order in the previous anarchy that represented the theme market prior to this move. There are a number of requirements for a theme to be accepted:

  • A single zip file, with all of the files themes file included.
  • There must be a style.css file containing:
    • Name (which must be unique to the directory)
    • Tags
    • Version (in the format of x.x or x.x.x and must be unique to the theme)
    • Align classes: .alignright, .alignleft, .aligncenter (see http://codex.wordpress.org/CSS for more details)
  • The screenshot file name must be screenshot.png, and be a real screenshot of the theme, not a splash screen.
  • Licensing must be GPL compatible.
  • No hidden, paid or sponsored links in the theme. Links back to the author’s site are fine.
  • Support Gravatars
  • Show post categories and tags
  • The theme must be your own original work.
  • Adult/mature themes are not allowed.

So, where does this leave WordPress. Well, for a start they are now in a position to guarantee quality in the themes they represent. In the past themes were riddled with bugs, unimplemented features, encrypted sections and sponsored links, all of which reduced the confidence of people trying to use them. All these reflected badly on the underlying product and now WordPress has a way to control all this. Another change we are bound to see is the ability for WordPress to automatically notify a user when a new version of a theme is available, in the same way it currently does this with plugins.

With a change like this, there are bound to be people who are unhappy with the decision. A number of people run directories of templates, these are bound to fade away now that there’s a quality offering and WordPress can direct people in that direction. Theme designers who earn a fee for maliciously hiding sponsored links in themes will also suffer. I still think there’s a market for premium themes that have a cost attached to them, if they offer additional functionality and support that the free theme directory doesn’t offer, but that would be an honest transaction rather than persuading users they have a “free theme” that has dangerous bits attached to it.

The other interesting fact is that WordPress is not only pushing to increase the quality of their product, but also tying it it’s other assets (like Gravatar) and encouraging people to use them. It’s advice that any IT Service organisation should take on board and use their position to maximise their utility and return. That’s what strategic planning is all about.

Should be interesting, check out the theme directory

WordPress Error: You do not have sufficient permissions to access this page

If you upgrade WordPress and get:

WordPress Error: You do not have sufficient permissions to access this page

you might have had a problem whereby WordPress thinks you’ve completed the upgrade but in fact some things have been left unfinished.

If this is the case, you can find a fix here. You’ll need to download a fix and run it on your server but I’ve had great success with it fixing this problem.

Call to undefined function: wp()

I came across a frustrating bug today that has a pretty simple solution. I had an installation of WordPress that had been created by Fantastico. I needed to modify wp-config.php, but once I saved it back to the server WordPress just refused to start. It returned the following error:

Call to undefined function: wp() in wp-blog-header.php

Anyway, I tried a number of different things to resolve the issue and almost ended up tearing my hair out, but in the end I managed to resolve it. Turns out that the line endings in the wp-config.php file created by Fanstastico aren’t standard CR/LFs. When I opened the file up in Notepad2, my text editor of choice, they appeared to me “Mac-type” line terminations. Setting these to normal CR/LFs and deleting any extra lines at the end of the file resolved the issue.

WordPress 2.6 Beta 3

I’ve just upgraded this blog to WordPress 2.6 Beta 3 to have a look at what it’s like. Everything seems to be working fine at the moment (and I’m loving the Word Count while I’m writing this post). Here are the changes from Beta 2:

  • Image captions
  • Yet more inline documentation
  • “Add Media” buttons for the RTE full-screen mode
  • Theme Preview fixes
  • Gallery sorting fixes
  • I18N fixes

See the full list of changes since Beta 2.

Get Beta 3.

Liberated Theme: Funny Dogs Liberated

Funny Dogs Liberated

Here’s another liberated theme for you. As I’ve said in a previous post, one of the projects I’ll be undertaking on this blog is clearing up themes with encrypted sections. The WordPress mantra is that WordPress, it’s plugins and themes should be available for the public to use, without being crippled or impaired. However, a number of “free” themes not only have links put in the footer without the user’s consent, they are also encrypted in such a way that they really impact a site’s performance. For example, today’s liberated theme had a footer file that was over 250k in size. Your server needs to load this in, decrypt it then display it. And that needs to happen on every page load. You really don’t want stuff like that running on your server.

So, here’s today’s liberated theme: Funny Dogs Liberated