Why CodeConfig Left WordPress.org: Our Plugin Review Story

CodeConfig started as a WordPress plugin development company. We built free and freemium plugins, shipped them through the official WordPress.org plugin directory, and spent years supporting the people who used them. Today, none of our plugins are hosted there. We now run our own website, offer WordPress services, and distribute our plugins directly, including our two newest releases, WP Media Player and WP Social Media Gallery.

In this post, we want to explain, openly and honestly, why CodeConfig Left WordPress. This is our experience and our opinion. It is not meant to attack anyone, but we think the WordPress community deserves to hear what plugin developers go through behind the scenes.

When CodeConfig Joined WordPress.org

CodeConfig joined the WordPress.org community in 2023. Our mission was simple: make WordPress more powerful and keep great tools free to use. With that goal in mind, we built free and freemium plugins, answered support requests, fixed bugs, and put a lot of time into keeping our releases up to date.

The plugins we published included File Manager for Dropbox, Integration for Google Drive, Dusky Dark Mode, and an accessibility plugin. For a small team, the WordPress.org directory was the best way to reach users, build trust, and grow a genuine open-source reputation.

What We Contributed

We did not treat the directory as just a distribution channel. We handled support threads, shipped regular updates, and tried to follow every guideline we were given. Many WordPress developers do the same. Hosting a plugin on WordPress.org is a real commitment of time, and for a small company it is a serious investment.

How the Problems Started

Over time, our plugins were flagged by the Plugin Review Team repeatedly. Some of the reasons given were ones we could not find written in the published plugin guidelines. We fixed what we were asked to fix each time, but the flags kept coming. Eventually, we were told that our plugins would no longer be hosted in the directory.

We accepted the decision. We did not argue or try to work around it. But the way it happened left us with a lot of questions, and those questions are the reason for this post.

The Inconsistency We Noticed

While we were being asked to correct our listings, we looked at how the same rules were applied elsewhere in the directory, and we saw what looked like uneven enforcement.

For example, we were told not to use words such as “Best” or “#1” in our plugin descriptions, and not to use “WP” or “WordPress” in plugin names. We followed those instructions. Yet we noticed other plugins, including some from very large companies, that appeared to use similar wording or naming. We also reported a plugin whose name used “WP” while its own branding pointed to a different product name, and as far as we could see, nothing changed.

We cannot know the internal reasons for any of this. Reviewers are volunteers, the queue is huge, and some listings may simply have been approved years ago under older standards. But from a developer’s point of view, the pattern was hard to ignore: smaller teams seemed to get strict, immediate enforcement, while larger brands seemed to get more flexibility. Whether that is true or only how it looked from our side, it damaged our trust in the process.

The Mistakes We Own

We want to be fair. CodeConfig made mistakes too. Some of the issues raised about our plugins were valid, and we said so at the time. We committed to fixing them and not repeating them. We are a human team, and human teams make errors.

What we asked for was proportionality. A first-time guideline mistake, fixed quickly and sincerely, should not lead to the same outcome as repeated deliberate violations. Developers who are willing to learn should be given a clear way to do so.

What We Believe the Review Process Needs

This is not only about our plugins. It is about how a system that thousands of developers rely on can work better for everyone. Here are the changes we would like to see:

• Automated pre-checks. Common issues such as restricted words in names and descriptions, missing escaping, or readme problems could be caught by an automated scanner before an update is accepted, rather than after a human review weeks later.
• Every rule written down. If something can get a plugin flagged or removed, it should appear in the published guidelines.
• Consistent enforcement. The same rule should apply to a solo developer and a company with a hundred employees, and the process for reporting violations should lead to visible, timely outcomes.
• Faster, clearer communication. Developers should know what the problem is, what to change, and how long a review will take.
• Support for the review team. A volunteer-driven team handling tens of thousands of plugins needs better tooling and more hands.

Why CodeConfig Left WordPress

When you combine unpredictable flags, rules that were not always clear, and a feeling of uneven enforcement, the directory stops being a safe place to build a business around. We also know we are not alone. Many independent plugin developers have talked about burnout, long review waits, and the difficulty of keeping a free plugin sustainable. Some have already stepped away from WordPress.org or from plugin development altogether.

For us, the decision was practical. We would rather control our own release process, support channel, and update system than depend on a platform where our work can disappear with little warning.

What Comes Next for CodeConfig

Leaving WordPress.org does not mean leaving WordPress. CodeConfig is still a WordPress company. We provide WordPress services, build custom solutions, and distribute our plugins from our own website. We have just launched two new plugins:

• WP Media Player, a flexible way to present audio and video on your WordPress site.
• WP Social Media Gallery, which helps you display social media content in a clean gallery layout.

We remain grateful to the WordPress community and to the many reviewers who volunteer their time. We hope this post starts a constructive conversation about how plugin developers and the review team can work together better. You can explore everything we offer at codeconfig.dev.