There has recently been a discussion on the WP-Forums mailing list concerning the following sticky thread. In a nutshell, there are two questions being considered. The first is whether decoding should be allowed on the forums. The second is whether this type of behaviour on the forum promotes the use of so called pirated themes. I say so called due to the fact that if the theme is licensed under the GPL, no pirating actually occurs.
Unfortunately, there are more bad places to download themes than good. Case in point, take a look at this screenshot from a Google search I performed looking for ‘Free WordPress Themes‘. The first two results are filled with base64 encrypted themes.
Poor SEO, or too many sites using themes with public facing links with encrypted code? Whatever the case may be, it’s evident that many users within the community are getting a hold of these themes and using them on their site, possibly not even knowing about the encrypted code within the footer.php or other files within the theme. In my opinion, I think that support of any kind for commercial themes should not be allowed on the WordPress.org support forum. Not only does it not make sense, but it’s a common courtesy to those companies that provide support as part of their value. While browsing through the Welcome Message that all new forum members should read upon signing up, I didn’t see any mention of commercial theme support. This would also make it very easy to just lock or delete threads concerning obfuscated code within commercial themes.
As for free themes that have been downloaded from the official theme repository and redistributed with the encrypted code or free themes in general, I’m not sure if decrypting those themes should continue on the forum or not. On one hand, it’s an opportunity to educate that user and explain why that code within a theme is bad news while on the other hand, it’s a never ending problem with no hard solution. I think education here is our best bet to fight against this with a detailed post on the WordPress.org blog but it’s not as if that will solve the problem, it will only make folks more aware.
There is no law saying you can’t place obfuscated code within a WordPress theme but it’s considered very bad mojo within the WordPress community. Obviously, these sorts of themes are not allowed within the theme repository but outside of the WordPress.org domain, it’s the wild wild west. It’s reached the point now where if a developer is releasing free themes, their best bet for trustworthy exposure is to have the theme on the WordPress theme repository. I suppose it’s a trade off. You can get a theme from the repository which doesn’t have the best variety and selection and know that it won’t have encrypted code or any other junk in it, or you can take your chances by finding a theme somewhere out on the net.
I’m interested in hearing what you folks have to say regarding the issue of themes, obfuscated code, and the WordPress support forum.
I started the discussion on the forum mailing list because I found a copy of a repository theme that had base64 in it when I was helping on this topic: http://wordpress.org/support/topic/414732?replies=8 I did a quick Google search for the theme he was having a problem with and downloaded it. I soon realized that the bad site had only switched 2 letters in the theme name and added some spam links in functions.php
This got me going through the decode sticky post and starting finding pirate themes from Woo, Studio Press, and Thesis which is not GPL.
I agree that we shouldn’t be offering support for premium themes in the forums but we have an obligation to protect WordPress users. At the same time as Jane Wells stated, we should also not be promoting the use of pirated themes.
Some of the pirate themes in question are not GPL and just as WordPress is firm on the GPL stance it should also respect other licenses by not helping users get around those licenses.
My stance is that we should not be decoding themes for users but we have an obligation to warn them of possible harm and should be educating them on the ethics and dangers involved.