“Paid plugin demo” advertised as a “free plugin”

Suki
(@sukinoz)

9 months ago

Lately, I’ve noticed a lot of plugins advertised as free plugins in the WordPress plugins repository (some with a pro version, others without), BUT in reality, the plugin is limited to a certain number of page views per month on the website where it is installed.

Once that limit is exceeded, the plugin is deactivated and stops working until the following month, unless… YOU PAY!

In other words, you can no longer continue using it without paying, even though it is in the WordPress repository…

That’s not a free version, it’s a demo! What do you think?

Does this meet the requirements of the WordPress plugin repository or is it a scam?

Thank you

Viewing 7 replies - 1 through 7 (of 7 total)

Moderator Steven Stern (sterndata)
(@sterndata)

Volunteer Forum Moderator

9 months ago

If the plugin is a means of connecting to an SAAS (software as a service) provider, then the charge is for the service, not the plugin, and that’s allowed.

https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#5-trialware-is-not-permitted

https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#6-software-as-a-service-is-permitted

Moderator Jan Dembowski
(@jdembowski)

Forum Moderator and Brute Squad

9 months ago

BUT in reality, the plugin is limited to a certain number of page views per month on the website where it is installed.

If the plugin code, and that’s important, is what is limiting the page views, that is not allowed.

https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#5-trialware-is-not-permitted

If the plugin code is an interface to a service and that service is the utility to limit page views then that is 100% allowed, permitted, blessed and sacrosanct.

*Drinks coffee, so good.*

The prohibition for trialware or limited ends at the code level. It the limits are done “in the cloud” then that is outside of the scope of the plugin guidelines.
Thread Starter Suki
(@sukinoz)

9 months ago
Thanks for responding, but as a user, I don’t understand the difference…

Let’s look at a real example (but there are several like this):
1. I find a plugin in the repository for managing cookie notices that says “Features of the free version: a) Displays the ‘accept or reject cookies’ notice. b) You can automatically scan cookies. c) Keeps a record of user consent. d)…“.
2. I think: Great!”, and I download the free version of the plugin and install and activate it.
3. Once installed, it tells you that in order to use features 2 and 3…, you need to register on their website. (I think: “Well, never mind.”)
4. When you go to register, it tells you: The free plan only works until the website reaches 5,000 page views. Once you reach that number of visits, the plugin stops working (it doesn’t even show the “accept or reject cookies” notice).
So, If your website has more than 5,000 pageviews per month, you either pay or the plugin is useless! I don’t know if it’s legal or not, but it’s certainly an unpleasant surprise… Also, keep in mind that displaying that notice is required by law, so if it doesn’t work, you’re breaking the law.

In summary, my questions are:
1) on the one hand, whether it is “legal” to do that in the WordPress repository,
2) and on the other hand, whether it is “ethical” not to warn the user before downloading and installing the plugin.

Thank you

PS. I have read in the “5. Trialware is not permitted.: … Functionality may not be disabled after a trial period or quota is met”
- This reply was modified 9 months ago by Suki.
Moderator Support Moderator
(@moderator)

9 months ago

We are forum moderators and do not make judgements on what is “legal” for plugins. If you have a serious concern, email “plugins@wordpress.org”.

Moderator Jan Dembowski
(@jdembowski)

Forum Moderator and Brute Squad

9 months ago

on the one hand, whether it is “legal” to do that in the WordPress repository,

Yes, totally as long as the limitation is on the service and not the code hosted here. That’s what the plugin guidelines is about and anyone hosting a plugin here must agree to those terms.

Legal is meaningless in this conversation. As a user of opensource software, you have no rights at all except what the plugin license grants you set by the author. Here, all plugins need to be GPL or GPL compatible.

If a developer is limiting the plugin in code, that’s not allowed (notice I am not saying “legal”) but if the plugin is an interface to a service, that is 100% allowed provided that the limits are on the service and not the plugin.

No one owes anyone free service. The code is free, services in “the cloud” do not need to be.

and on the other hand, whether it is “ethical” not to warn the user before downloading and installing the plugin.

I’m afraid I am pretty sure there is no answer that will satisfy you. If you did not download the code, how would you really now? Yes, the plugin page often needs to explain but the plugin page is a description of the plugin’s capabilities and functions.

A plugins page is not some binding document.

When you go to register, it tells you: The free plan only works until the website reaches 5,000 page views. Once you reach that number of visits, the plugin stops working (it doesn’t even show the “accept or reject cookies” notice).

With the provision I wrote, that is completely allowed and always will be.

PS. I have read in the “5. Trialware is not permitted.: … Functionality may not be disabled after a trial period or quota is met”

Then you misread it. Where the limitation is the important part.

You don’t have to agree to the terms of the plugin you download. Downloading it was your choice and you can always remove the plugin if you dislike it.

Thread Starter Suki
(@sukinoz)

8 months, 4 weeks ago

Wow, maybe it’s just me, but I get the feeling that the question bothered you. I’m sorry.

It wasn’t my intention to make you judges, I just wanted to hear the opinion of WordPress experts on an official WordPress forum. That’s all.

Don’t worry, I’ll try not to bother you again.

Thanks anyway.

Kevin McClellan
(@crazywpgeek)

8 months, 2 weeks ago

@sukinoz I agree that free plugins that limit a big amount of features like what you pointed out are probably not being clear enough about those limitations in the plugin description if you are surprised to learn about this after signing up/registering for the free features.

I have run into some situations like that as well over the years which is why I tend to stay away from plugins like that. If they require a registration to use something that is free, and it’s not a app you use separately, then to me that is a red flag as it seems they just want your info to spam you about getting the premium version (this happened to me once).

I use a lot of free plugins. I understand the plugin author’s need to have funds in order to continue developing, and I do support this as I have purchased many premium versions of plugins.

Some of the things that plugin authors do with the free versions is borderline spammy in some ways, but this doesn’t happen to a majority of plugins out there.

Just as a suggestion, I would recommend discussing your concerns directly with the plugin authors if possible, by posting in their support forum from the plugins page on WordPress, as they’ll be able to address those concerns in a better way than we can here.

It’s very rare (almost unheard of) that a plugin submitted to the plugins directory is allowed to come through if it violates any rules – but that can happen after the fact as well if the plugin is changed later that adds some blockages that would have violated the rules. If that seems to be the case then reaching out directly to the plugins team via the email address shared in a previous response to this thread would be the best way to get someone to look into that specific plugin.

I don’t think anyone here in this thread was bothered by your questions as they are valid concerns and that you were just asking this out of curiosity and not to complain about it. It’s hard to read tone via a forum response – and a lot of us here in the forums can be a little direct and to the point which can sometimes sound like they were annoyed.

I hope my thoughts on this were somewhat helpful, and again, I do agree that sometimes these plugin authors need to really think about how they are offering their features. I don’t have anything against plugin authors at all as their contributions to WordPress are important.