![Popular open source software is more secure than unpopular open source software, because insecure software becomes unpopular fast. [That doesn't happen for proprietary software.]](../sites/all/themes/drupal4hu/images/bg-center/bg-center_4.png)
And because of that we need Drupal specific theme sites like http://www.topnotchthemes.com and not generic template sites like Template Monster selling you an oversimplified template that's so simplified it's unusable.
Edit: oScommerce users have already been burned. Beware!
Commenting on this Story is closed.
Yeah, TM is OK to make a purchase and have the files, but sometimes installations are terrible and the xHTML is not good. Outside of the purchase, the customer support sucks. But, I think it is a good thing for Drupal, bringing new CMS users to Drupal. As Drupal gets more theme developer friendly more and more people will theme for Drupal. Themers visit TM just to compare. That is what I am hoping for, those themers will jump into Drupal and embrace the future!
Cheers,
Elvis
Lets first see if they sell/license the themes conform Drupals GPL license. If not than Bert will most likely shut them down :)
Be sure to read the FAQ section of the site. All template code (.tpl.php and template.php) is licensed under GPL, as it has to be. However, the CSS and images are NOT GPL. Making it so you could potentially redistribute the markup, but that's not the point. They're selling design, which doesn't have to be under the GPL.
You might read Dries' article on Drupal's use of GPL 2 (but not 3) in his post "Long live the web services loophole. Although themes aren't a web-service, the premise is the same. CSS and Images can't execute the GPL'd code of Drupal, and so therefor they're not "infected" with the license.
Please bear in mind that the "web services loophole" is most definitely _not_ addressed in the released version of GPLv3, so disagreeing with Affero GPL style copyleft is not a reason to not use GPLv3.
There was discussion very early on in the GPLv3 draft process of possibly making "software as a service" a trigger for copyleft, but it was decided that it wasn't clear that providing a service that depended on a piece of software was the same as distributing (or "conveying" in GPLv3-speak) a copy of the software, and that the freedom to make private modifications to your own software was more important than any potential restrictions on the users' freedom in these cases. So the Affero GPL (which closes the "loophole") remains a separate license, but there are clauses in both GPLv3 and AGPLv3 to allow projects covered by either license to share code.
Most criticisms of GPLv3 you'll find date back to the draft process, and don't apply to the released license; the changes are actually pretty conservative (as far as everyone except TiVo, Microsoft, and Novell are concerned).
Personally I think Drupal should move to GPLv3 ASAP, to avoid the problem of "TiVoization", or the threat of a Microsoft-Novell-style patent covenant between a patent holder and one or more - but not all - Drupal distributors.
I say that TM themes will lack the detail a proper theme requires.