Here’s a great answer from another forum thread:
[The] PHP code loaded and interpreted together with WordPress PHP core code should be under GPL. This means – all plugins and themes PHP code should be GPLv2, assets can have another license
GPL refers only to code, and not an interaction. So apps that operate independently to WordPress, do not include WordPress code, and simply use APIs to interact with WordPress would not be derivative works.
@kaitohm I appreciate the input!
So then theoretically, somebody could set up their own repository of every WordPress theme and plugin (both free and paid), and then host that for an infinite number of people to use?
-
This reply was modified 1 year, 6 months ago by
oguruma.
Yes, theoretically, anyone may do that. Each of those plugins and themes should inherit GPL, though.
@kaitohm That’s not originally why I asked, but I do suspect I’d find that useful. Clients often reach out to me because their site uses some kind of paid plugin (Elementor Pro, ACF Pro, etc.) and they can’t update it because they failed to renew their paid membership/support plan for that plugin. It seems like it might be convenient (and possibly cost-effective for those involved) to make a repo that hosts the most recent version(s) of those plugins and then a simple plugin to override the plugins’ default update repo to the “forked” repo.
@oguruma GPL only relates to code. So what you are describing wouldn’t be prohibited by GPL.
However, there are other ethical considerations. Pro plugin creators need to be paid for their services including providing plugin updates, support, documentation, bug fixes etc. When someone signs up to a Pro plugin’s plan, they are supporting the people behind the plugin to continue providing their services. While the suggested “forked” repo may reduce the financial commitment on the user, it doesn’t support the creator, and would affect the services they are able to provide.
