WordPress has grown to a point where some developers are having trouble keeping up with user demand and an ever-changing landscape. As a result, they’re selling their products to companies with more resources to devote to maintenance and support.<\/p>\n
We are also seeing changes concerning how commercial licensing works. One incident, in particular, has the community-at-large debating: what should happen when a WordPress theme or plugin license expires?<\/p>\n
Let’s take a look at what happened and examine the deeper issues at hand.<\/p>\n
A Popular Membership Plugin Locks Out Expired Licensees<\/h2>\n
MemberPress, a popular commercial WordPress membership plugin, have taken a tougher stand<\/a> with customers who have allowed their license to expire. After a “grace period”, website owners will no longer be able to access any of the plugin’s administration screens.<\/p>\n The plugin will continue to work on the front end of the site. However, making changes on the back end is not possible. Instead, administrators will see a deactivation notice<\/a> explaining the situation.<\/p>\n To be clear, this hasn’t been a common policy within the WordPress ecosystem. In my experience, an expired license means being cut off from support and software updates. This is a long-term risk for site owners due to potential security flaws or incompatibilities.<\/p>\n MemberPress’ actions have sped up the consequences of using an unlicensed plugin. Reaction within the WordPress community has been split<\/a>. Some are troubled by the tactic, while others think it’s fair game.<\/p>\n Whatever feelings this incident has conjured, it has certainly shaken up the status quo.<\/p>\n The act of locking users out of unlicensed software isn’t new. Desktop software has been doing this for years. Some popular apps, such as Photoshop, previously allowed unlimited access for whatever version you purchased \u2013 then switched to a subscription model. No subscription, no access.<\/p>\n It’s not a universal practice, however. And there’s an argument to be made that website software is a different use case than apps tied to a specific device \u2013 particularly when it’s being utilized on an open-source platform. According to some, it may even go against<\/a> the spirit of the \u201cWordPress way\u201d.<\/p>\n Those points aside, I have used and enjoyed MemberPress. It’s an effective way to build a membership website<\/a>. I’m not privy to the details of their decision. But as an observer, this action seems a bit heavy-handed.<\/p>\n I could see, for example, a modal window that pops up every time you try and access a plugin settings page (WordPress is great<\/a> for that, after all). Even an occasional email nag would be understandable.<\/p>\n The problem (as I see it) is that users are being treated like scofflaws. Yes, some people will intentionally not renew a license and expect to use the software forever (more on that later).<\/p>\n But there are other legitimate situations when a license renewal is simply missed. It could be that the license was in the original web designer’s name and they’re no longer in the picture. Or renewal reminders were sent to an email address that no longer exists. Frustrating for plugin developers, perhaps. But far from criminal.<\/p>\n It also sets a precedent for other theme and plugin authors. Think of a theme with an expired license that places a huge “UNLICENSED” banner across a website. Maybe it’s within their right to do so. But what kind of damage does that do to their relationship with customers? How likely is a renewal in such a case?<\/p>\n There’s a fine line between encouraging customers to continue supporting your product and (intentionally or not) antagonizing them.<\/p>\n While I can’t speak as to why MemberPress took this action, I can think of some valid reasons for doing so. There may be a subset of users out there who expect that, because they purchased a one-year license, should be able to have access and support indefinitely. That may be a drain on finite resources.<\/p>\n Appeasing these users isn’t sustainable. It’s a reminder that, if there’s a theme or plugin that is a key component of your website, you’ll need to keep your licenses in good standing. This helps to ensure that the product both survives and continues to improve. That’s in everyone’s best interest.<\/p>\n Is this a sign of things to come? Just as the reaction to the MemberPress policy was split, I would expect that future implementation of similar policies will be as well.<\/p>\n I’d like to believe that there’s room for a middle ground. Software developers should be able to convey the importance of license renewals. But they should also make their intentions crystal clear.<\/p>\n Users should know a developer’s policy before<\/em> they make a purchase. This won’t resolve everything (some are bound to forget or miss it completely). Still, as with most conflicts, effective communication can make a difference.<\/p>\n The post What Should Happen When a WordPress Theme or Plugin License Expires?<\/a> appeared first on Speckyboy Design Magazine<\/a>.<\/p>\n Source: Specky Boy<\/p>\n![\"An](\"https:\/\/i0.wp.com\/speckyboy.com\/wp-content\/uploads\/2022\/05\/wp-expired-licenses-01.jpg?resize=900%2C400&ssl=1\")
<\/p>\nWhy Did This Action Hit a Nerve?<\/h2>\n
![\"A](\"https:\/\/i0.wp.com\/speckyboy.com\/wp-content\/uploads\/2022\/05\/wp-expired-licenses-02.jpg?resize=900%2C400&ssl=1\")
<\/p>\nPondering the Future of WordPress Licensing<\/h2>\n