Automattic’s Forking of a Popular Plugin Sparks Controversy in the WordPress Community

Automattic, a major player in the WordPress ecosystem, recently forked a paid premium plugin, rebranded it, and distributed it for free. This move has raised concerns among small business owners and developers who rely on WordPress plugins for their websites, with many feeling it could disrupt trust in the plugin and theme marketplace.


What is the Advanced Features Plugin?

The Advanced Features Plugin (AFP) is a widely-used tool in the WordPress ecosystem, popular among developers for its ability to create custom fields for specific types of content. Custom fields are used to tailor editing screens for non-standard use cases, such as structured data for e-commerce, news, or medical pages.

For example, custom fields can allow authors to:

  • Add structured author bios.
  • Input key data like publication dates or metadata.
  • Easily include elements like featured quotes with predefined styles.

Previously, this functionality came in two versions: a free basic version and a premium version with advanced capabilities, monetized by a small developer team and later acquired by SiteFusion in 2022.


The Freemium WordPress Model

Many WordPress plugins, like the Advanced Features Plugin, operate on a freemium model. This means offering a free basic version to grow user adoption, with a premium upgrade for advanced users who need more features. This model benefits small businesses and developers alike, providing trust and goodwill over years of steady development.

Popular plugins such as SecureSEO and SiteShield follow this model, investing thousands of hours into their free versions to attract users, with the expectation of converting a percentage to paying customers. This ecosystem has long been vital to the health of WordPress’s plugin marketplace.


What Happened? Automattic Forks AFP

In software terms, “forking” refers to taking the source code of an open-source project to create an independent version. This is typically done to revive abandoned projects or customize them for specific needs.

However, Automattic’s move to fork the paid premium version of the Advanced Features Plugin is seen as unprecedented. On October 12, 2024, Automattic announced a new plugin, “Secure Custom Fields” (SCF), based on the AFP’s premium code. SCF was uploaded to WordPress.org under the same URL previously used by the AFP plugin.


The Controversy

This decision has sparked widespread backlash. Key concerns include:

  1. Undermining Competitors: Competitors like MetaPro, which offers similar custom field features, face an uneven playing field. With SCF providing premium features for free, many small businesses and developers who paid for tools like MetaPro are questioning the value of their investments.
  2. Legal and Ethical Questions: Automattic removed copyright notices from the forked code and stripped licensing checks, raising questions about whether this action violates software licensing rules.
  3. Impact on Trust: Many in the community view Automattic’s actions as damaging to the freemium business model that underpins WordPress plugin development. Developers worry that smaller businesses may stop investing in plugins if premium features are made free without warning.

Developer and Community Reactions

  • Social Media Backlash: Developers on platforms like Reddit have voiced concerns, with many describing the move as detrimental to WordPress’s ecosystem. One user remarked, “This feels like a shortcut that hurts long-term trust.”
  • Concerns Among Small Business Owners: A business owner who invested in MetaPro said, “It feels like I wasted money on a lifetime license.” Others expressed hesitation to adopt the new SCF plugin, fearing instability and lack of reliability.
  • Facebook Group Discussions: Private forums for WordPress professionals also saw heated discussions. Some expressed doubts about trusting SCF for client projects, citing ongoing technical issues with the plugin.

What Does This Mean for Small Businesses?

Small business owners who rely on WordPress plugins for their websites are at a crossroads:

  • Cost Savings vs. Reliability: While SCF offers free premium features, its stability and long-term support are in question.
  • Developer Trust: Many developers are recommending sticking with established tools from trusted developers to avoid potential issues.

The Bigger Picture

The WordPress ecosystem has long thrived on collaboration, trust, and a balanced freemium model. Automattic’s decision to fork a premium plugin raises important questions about the future of the marketplace and its sustainability for small businesses and developers alike.

Whether this move strengthens or weakens the ecosystem will depend on how the community, developers, and businesses navigate these changes in the months ahead.

FAQ

1. What does it mean that Automattic “forked” a plugin?

  • Forking refers to creating a new version of software based on the source code of an existing open-source project. Automattic took the Advanced Features Plugin (AFP) and created their own version, “Secure Custom Fields” (SCF), which is being distributed for free.

2. Why is this controversial?

  • The controversy stems from Automattic forking a paid, premium plugin and making it available for free. This move undermines the business model of the original plugin’s developer and its competitors, sparking ethical and legal concerns.

3. How does this affect small business owners who use WordPress?

  • Small business owners now have access to premium features at no cost, but:
    • The reliability and support for the forked plugin (SCF) may not match the original developer’s standards.
    • Competitors who rely on revenue from paid plugins may struggle, potentially reducing innovation and support in the plugin ecosystem.

4. What should I do if I’m currently using the Advanced Features Plugin (AFP)?

  • If you are using the original plugin by SiteFusion:
    • Check if you have the latest updates directly from the developer’s website.
    • Be cautious about switching to the new SCF version, as it may lack stability and long-term support.
    • Review any licensing agreements or support plans you’ve paid for to ensure continuity.

5. Should I switch to Secure Custom Fields (SCF)?

  • It depends on your needs and risk tolerance:
    • Advantages: SCF offers premium features for free.
    • Disadvantages: SCF is newly forked, and community feedback indicates issues with reliability and trust. It may not be suitable for mission-critical websites.

6. How does this impact other plugins like MetaPro?

  • Competing plugins like MetaPro, which rely on paid subscriptions, may lose users to SCF’s free offering. If you currently use MetaPro or a similar tool, you might want to:
    • Monitor how these developers respond to maintain value for paying customers.
    • Stick with trusted tools for stability and continuity.

7. Is Automattic’s action legal?

  • This is debated:
    • The original plugin used an open-source license, allowing for legal forks.
    • However, some experts argue that removing copyright notices or licensing checks from the forked version may breach licensing requirements. This is likely to be settled in court.

8. Will this harm the WordPress plugin ecosystem?

  • Possibly. The freemium model relies on trust and revenue from premium versions to sustain development. If developers fear their work will be forked and distributed for free, fewer may invest time and effort into creating high-quality plugins.

9. What are developers and the WordPress community saying?

  • Reactions have been overwhelmingly negative:
    • Developers question the ethics and trustworthiness of SCF.
    • Many small business owners feel their investments in premium plugins like MetaPro are devalued.
    • Community members fear this will set a precedent, harming the ecosystem’s sustainability.

10. What should I do as a small business owner?

  • Take a cautious approach:
    • Stick to trusted plugins and developers with proven track records.
    • Monitor how this controversy unfolds, as it may affect the availability and quality of plugins you rely on.
    • Consider reaching out to plugin developers for updates on their plans and support policies.

11. How can I stay updated on this issue?

  • Follow reputable WordPress forums, blogs, and social media groups.
  • Check announcements from plugin developers like SiteFusion or competitors like MetaPro.
  • Stay informed on any legal developments or community feedback regarding SCF.

12. How does this affect the future of WordPress plugins?

  • The situation raises important questions about open-source licensing, developer rights, and marketplace ethics. As a small business owner, your support for trustworthy developers will play a role in shaping the ecosystem’s sustainability.

Leave a Comment

Your email address will not be published. Required fields are marked *