WordPress.org's latest move involves taking control of a WP Engine plugin
1–10 of 222 posts
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#2Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#3Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#4Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#5They either have some of the best or worst legal counsel; or they just ignore the legal counsel.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#6Where is the CVE? What risk is there continuing to use the original plugin? No details at all. This results in fear: we don't know if the original is safe to use.
> Going forward, Secure Custom Fields is now a non-commercial plugin
Does this imply that Wordpress is potentially going after a revenue stream from WPEngine?
If the plugin had Pro options* then are those closed source and so not available to Wordpress in their fork of the codebase? It's not clear.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#7To be honest, none of this makes WordPress look good... It just seems like a douche move.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#8Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#9> It’s not clear what security problem Mullenweg is referring to in the post. Where is the CVE? What risk is there continuing to use the original plugin? No details at all. This results in fear: we don't know if the original is safe to use. > Going forward, Secure Custom Fields is now a non-commercial plugin Does this imply that Wordpress is potentially going after a revenue stream from WPEngine? If the plugin had Pr…