All posts filed under: Plugins

The perils for plugin businesses with no or minimal terms of use

WordPress is a fantastic content management system. In the some 18 years that I’ve been using it, I’ve seen it go from a glorified blogging engine to a fully fledged content management system. I’ve seen the development and growth of theme and plugin businesses, and I’ve witnessed and contributed to the often arcane debates about the GPL. Through this site, I’ve also tried to help WordPress theme and plugin businesses with the various legal issues that can crop up in the use of WordPress and the running of their businesses. I will soon be launching my own plugin business. The plugins that will be available for purchase all revolve around Gravity Forms (an awesome plugin that I’ve been using since 2010). If you’d like to be told when I launch, feel free to sign up here: In the past I whipped up an automated terms of use builder for theme and plugin businesses (you had to purchase the ‘business package’ of A Practical Guide to WordPress and the GPL to get access), and I’m using …

How to apply the GPL to your themes and plugins (and avoid getting in the shi*)

Introduction “I wish this stuff could be easier!” Have you ever found yourself saying or thinking this or otherwise cursing the ins and outs of applying the GPL to your themes or plugins? Have you ever been worried that, perhaps, you’re not doing what the GPL requires or that you’ve overlooked a WordPress.org requirement? From a wide range of stories and comments I’ve seen around the web, I think Jamie’s story is one that rings true for many. So, if you’ve answered yes to one of these questions, you’re far from being alone and this post is for you. “How do I apply and comply with the GPL correctly?” If you feel this way, it’s not surprising. Indeed, if you’re only just getting into open source or releasing your first theme or plugin, I’d say it’s to be expected. I say that because not only do you need to understand a legally-oriented copyright licence but, if you wish to make your products available on WordPress.org, you also need to get to grips with the WordPress.org theme and plugin guidelines. And …

“I’d rather see [an] attorney’s attention spent … on clarity and brevity”

WordPress, Wix and the GPL The Wix controversy, if I can call it that, has stirred up quite a bit of emotion in the WordPress and wider tech and open source communities. I’ve given my thoughts on what I see as the main issues in my previous post “Some thoughts on the Wix mobile app story (updated)”. In reading a wide range of comments on the various news and blog articles on this story, it strikes me that many people don’t understand the GPL, either due to its complexity at the margins (and I assure you that, at the margins, it can bamboozle lawyers too) or, in some cases, because they haven’t read it. Then, in reading further through various comments, one comment on the WP Tavern story stood out to me. Lisa League wrote: “Spending time, money, and attention on court diverts it to attorneys instead of that valuable time money, and attention spent on software. … … this is where I’d rather see attorney’s attention spent – on clarity and brevity where possible in …

Content scraper plugins, contract and copyright

The story I thought I’d introduce this post by telling a story. It’s a story about Jim, an everyday guy who has a website for which he wants more content. Jim already works hard on his site, adding new posts frequently, but he wants more content to drive more traffic to his site and to help monetise his site. He can’t do it all alone. Jim finds a bunch of sites with interesting and relevant content that he thinks would be perfect for his own site. These sites don’t generate web feeds of any flavour so Jim does a trawl of WordPress plugins and finds a commercially available plugin in a well-known plugins marketplace that does exactly what he wants. All he has to do is: install the plugin; create a post or page in his site and click a new icon in the editor which opens a pop-up window that asks for a URL and a CSS selector; get the URL of the page on another site that has the content he wants and …

Discouraging public redistribution of commercial themes and plugins – poll results

Background Back on 4 August of this year, I published a post called Theme and plugin shops – Discouraging public redistribution – User poll.  The poll that was included in the post sought people’s views on the reselling of commercial themes and plugins. It did this because people’s views on this issue are relevant to the inclusion of a contractual mechanism I’d proposed for theme/plugin shop terms of use. The contractual mechanism I’d proposed would seek to discourage purchasers of a commercial theme or plugin from making the theme or plugin available on a website for download by others (whether for free or a charge), even when the theme or plugin is 100% GPL-licensed. The proposed term would say that, if a customer decides to make your commercial theme or plugin available on a website for download by others, you may exercise a right to deactivate their access keys (if that’s how you’ve set things up) and to terminate their access to support and updates. I explained why, in my view, this sort of clause …

A Practical Guide to WordPress and the GPL – now available – 30% introductory discount

Finally… I’m pleased to be able to say that A Practical Guide to WordPress and the GPL is now out in the wild. You can find it right here. Outline Here’s a quick outline of the chapters: 1. Introduction: conception, birth and forking 2. Understanding the GPL licensing of WordPress 3. Common GPL-related questions 4. WordPress themes, the GPL and the conundrum of derivative works 5. The GPL and assumptions of automatic inheritance 6. Theme reviews, CC0, model releases and GPL-compatibility 7. Selling ThemeForest themes outside of ThemeForest 8. Reselling commercial plugins 9. The GPL and trademarks 10. Theme and plugin shop terms of use versus GPL freedoms Packages Three different packages, or editions, are on offer: 1. The business package If you’re into the business of developing WordPress themes or plugins (or both), you might want this package. You’ll get: the ebook (PDF) of A Practical Guide to WordPress and the GPL; a professionally narrated audio book, enabling you to listen to the book when you’re on the go (narrated by Steve Chase); and …

Theme and plugin shops – Discouraging public redistribution – User poll

Context Last week I sent an email to subscribers on my email list. I hadn’t proposed to publish the content of that email but, given some questions I’ve received in response, I thought it might help to publish it. I also thought it would be helpful and interesting to take a quick poll of people’s views on the reselling of commercial themes and plugins because people’s views on this issue are relevant to the inclusion of the contractual mechanism in theme/plugin shop terms of use that I discuss below. I’ll set out the email then take the poll. (Please retweet as the more that take this super quick poll the better.) So, the email This is what I said: “I’m in the process of finalising my 10 chapter ebook called A Practical Guide to WordPress and the GPL. The ebook will be offered in a range of packages, from just the ebook through to a package that will offer the ebook, an audio book and a terms of use builder for WordPress theme and plugin …

Theme and plugin shop terms of use versus GPL freedoms

Introduction For a while now I’ve wanted to address an issue that niggles away at me every time I see it. I touched on the subject slightly at the end of Readers ask: About reselling commercial plugins (updated) but I wanted to explore it a bit more in its own post. There are so many theme and plugin shops out there now that you probably couldn’t count them all with even 20 hands. Perhaps not surprisingly, this multiplicity of WordPress businesses has resulted in a wide range of terms of use and licensing statements in relation to the themes and plugins they sell. Of course, what these businesses say in their terms is constrained – or should be constrained – by the requirements of the GPL, at least in situations where they’ve created derivative works of WordPress or other GPL’d code or where they’ve otherwise chosen to apply the GPL to their themes or plugins. In this post, I’m going to focus on theme and plugin shops that have expressly applied – or purport to …

Click to accept processes: a closer look at Gravity Perks

Context As you might have gathered from some of my earlier posts, I’m a big fan of Gravity Forms, a fantastic plugin that just gets better and better with the passage of time. I’ve used Gravity Forms in the past to create ‘click to accept’ mechanisms but, at least as I’ve deployed them, they required inclusion of a link to terms of use which would then open up in a new window or tab (for anyone who bothered to read them). With this approach the terms themselves weren’t visible on the same page as the click to accept box. Legally this wasn’t a problem but perhaps it wasn’t the most user-friendly approach. In Legal checks when building a content-driven WordPress website I mentioned that you could go one step further by purchasing and installing the Gravity Perks plugin which includes a GP Terms of Service Perk. I noticed that this add-on for Gravity Forms helpfully adds a Terms of Service field to the available Advanced Fields and can produce something like this: At that point …

Readers ask: About reselling commercial plugins (updated)

The questions Following the posts on WordPress themes, the GPL and the conundrum of derivative works and A reader asks: Selling ThemeForest themes outside of ThemeForest, two people from countries far apart have asked me similar questions (albeit possibly from opposite perspectives) regarding the reselling of GPL’d plugins. The first person asked this (I’m paraphrasing): ‘If someone purchases a plugin (or theme) from a commercial plugin (or theme) provider, and then translates it, changes the code and puts it in a marketplace to sell, would that be permissible under the GPL? I’ve seen outfits doing this and I’m not sure how they can do it.’ The second person asked this: ‘As a plugin developer, how can I protect my plugins to prevent people from reselling them, bearing in mind that many plugins are largely PHP/HTML/javascript code with minimal CSS and graphical elements or, in any event, with CSS and graphical elements that might easily be replaced. In these circumstances, a ThemeForest-style split licence might not have much effect. In these circumstances, how can a plugin …