Moving Forward: The Closure of DLX Plugins (and why I’m Open-Sourcing the Code)

Effective October 1, 2026, DLX Plugins will close its shop, ending its commercial operations. As this chapter ends, I am taking steps to ensure users are fully supported and that the software can live on.

Why is DLX Plugins closing?

Building WordPress plugins has been the joy of my life, and I hope it can continue in a different form. The ecosystem around plugins like mine has shifted considerably over the years, and many of my extensions have seen declines in their install bases and sales. As an indie developer, running a standalone plugin shop is very expensive to maintain, and I’ve been operating in the red for some time now. To better align my resources, I’ve made the strategic decision to close DLX Plugins (the brand and its plugins) entirely while focusing on full-time employment, consulting, and enterprise WordPress engineering solutions.

What this Means for the “Pro” or Premium Plugins

I don’t want the code to go to waste, nor leave any customers stranded, especially the lifetime ones. Therefore, I am completely open-sourcing most of the DLX Plugins code on GitHub. For each open-source plugin, a version stripped of any license-key restrictions will be released before the October 1st sunset date. Anyone with an active license will be able to update to this code. The nulled code will be publicly available on GitHub after the sunset date under the GPL license for anyone to use, fork, or modify.

What happens to Lifetime License Customers?

DLX Plugins, as a plugin development shop, is ending, and so are its plugins. I don’t want to leave lifetime users hanging with a plugin they can’t use, or that pings a site that doesn’t exist for updates. The plugin code will be open-sourced and nullified, with a final version that strips out any license code provided to all lifetime holders before the sunset date of October 1, 2026.

By open-sourcing the code, each lifetime user is set up for the future with an archive they can copy, fork, and modify as needed. I will personally email (and thank) each lifetime license holder during the sunsetting period to answer any questions and concerns. Due to business financial constraints, I’m unable to issue refunds to any lifetime license holders.

What Happens to Active Subscribers?

To prevent accidental renewals, active plugin subscribers with licenses have already:

  • Had their subscriptions canceled at the gateway (e.g., Stripe, PayPal).
  • Have had their subscriptions canceled here at DLX Plugins.

I will work with customers who have recently purchased or renewed a product individually. I’m unable to issue refunds for any previous charges (including charges from previous years) due to financial constraints.

Nulled code will be delivered to customers with active licenses before the sunset date.

What is Happening to the Pro (Paid) Plugins?

Most of the paid plugins are being open-sourced (where it makes sense) and nullified (stripped of their licensing mechanisms).

Here are each of the premium plugins and their current status. I will update this table until the sunset date.

PluginActive InstallsGitHub RepoLicense-free Available?
Archive Pages Pro2View GitHubYes, 1.0.2 released September 7, 2026
Comment Edit Pro20TBDNot yet
GB Extras21View GitHubYes, 3.0 released August 3, 2026
HeyTodos0Not Open-Sourcing (requires auth plugin)N/A
QuotesDLX4TBDNot Yet
Tazker0TBDNot Yet

What is happening to the Free (.org) Plugins?

I will try to find new owners and homes for each plugin, or return them to their previous owners. Each plugin will be placed in perpetual maintenance mode (with a brief notice, an “adopt me” tag, and a pinned forum post) until a good owner or maintainer is found. Any hosted documentation will be moved to GitHub before the October 1st sunset date.

Here is the current status. I will update this table until the sunset date.

Last updated: July 13th, 2026

PluginInstallsLooking for a new owner?GitHub RepoStatus
Ajaxify Comments3,000YesGitHubAdopted by David Stone.Opens in a new window
AlertsDLX80YesGitHubUp for adoption.
Comment Edit Core2,000YesGitHubAdopted by David Stone.Opens in a new window
Custom Query Blocks700No, deprecateGitHubTo be removed from .org on Oct 1st.
Highlight and Share800YesGitHubAdopted by BerryPressOpens in a new window
Pattern Wrangler400YesGitHubAdopted (Details soon)
Reorder Posts10,000YesGitHubPotentially for sale or adoption to reputable owner
Reorder by Term1,000YesGitHubPotentially for sale or adoption to reputable owner
Reorder Terms1,000YesGitHubPotentially for sale or adoption to reputable owner
Slash Edit500YesGitHubAdopted by BerryPressOpens in a new window
Sortacular10No, deprecateGitHubTo be removed by October 1st.
WP Plugin Info Card500No (but original owner is looking for new developer/contributor)GitHubUp for Adoption

What Happens to the Site?

After October 1, 2026, DLXPlugins.com will cease to exist, including all its content. If you have a favorite resource or tutorial on the site, please archive it before the sunset date. This site, with very few exceptions, will remain as-is (warts and all) for archival purposes until the sunset date.

For transparency and archiving, a copy of this post and its public comments will be reposted on MediaRon.com, the parent company of DLX Plugins, after the sunset date.

Any Questions or Comments?

From the bottom of my heart, thank you so much for reading. If you’re a customer, I truly hope you understand why I’m doing this.

I’ve left the comment section open. Please keep the discussion open and civil.

You can also: