We need to be careful with freemium plugins because that may exclude WP plugins that support CP. Shield Security and Beaver Builder are 2 examples. Both are listed in the directory.
1 Like
So, I guess it’s too late to rule out freemium then ![]()
The last time I remember discussing this was around here: Policy for non-GPL plugins - #7 by james
I’m concerned that the core does not do the update, so it has to be built into the plugin. The WP guidelines prohibit plugins from transmitting code:
Plugins may not send executable code via third-party systems.
This seems like a good guideline to have, yet we can’t.
Maybe we can make it conditional and limit it to updating system? And note it’s temporary.