Liquid Web WordPress Plugin Rebrand Triggers Backlash

Search Engine Journal reports that Liquid Web’s consolidation of its WordPress plugin portfolio has sparked significant backlash from users caught off guard by disappearing brands and broken access flows. The chaos stems from both the product restructuring itself and years of overlapping branding between Liquid Web and Nexcess.

What’s actually new

Liquid Web has collapsed its WordPress software portfolio — previously scattered across the StellarWP umbrella with standalone sites for each plugin — into four core products: Kadence, LearnDash, The Events Calendar, and Give. SolidWP, Iconic, Restrict Content Pro, and MemberDash are no longer sold standalone; their features have been folded into Kadence or LearnDash. The StellarWP brand appears to have been retired without advance notice. Meanwhile, the corporate branding is its own puzzle: Nexcess relaunched in April 2026 as a “Specialty Cloud” brand, while the plugins are described under “Liquid Web by Nexcess,” and both brands claim the same products as part of their ecosystem. A Nexcess strategic product leader confirmed that lifetime deal holders retain everything they purchased and that all existing customers are grandfathered in on current plans and pricing, though login issues and missing invoices plagued the initial rollout.

What it means for your config

This isn’t a code-level breaking change to how these plugins work inside WordPress — it’s an organizational and licensing restructuring. But if your WordPress stack relies on plugins like SolidWP, Iconic, Restrict Content Pro, or MemberDash, the practical concern is real: standalone product pages and download links have been disrupted, and license key management may temporarily break during the migration. If you manage deployments via Composer with wpackagist or private Satispress/SatisGo repositories that reference specific plugin slugs or download endpoints, those URLs may have changed or may change further as the dust settles. The announcement doesn’t detail whether plugin slugs in the WordPress.org repository are affected, or whether API endpoints for license activation have moved. If you pin plugin versions in your composer.json or manage updates through a CI pipeline, it’s worth verifying that your update sources still resolve correctly. For teams using configuration management tools to enforce specific plugin sets across environments, the brand consolidation means some plugins you track individually may now be bundled differently — check whether the features you depend on landed in Kadence or LearnDash, and adjust your stack documentation accordingly.

Recommended next step

If you’re running any of the affected plugins — especially the ones folded into other products — log into your Liquid Web/Nexcess account now and verify that your license keys still activate and that you can download the plugin versions you need. Don’t wait for auto-updates to surface a problem in production. For lifetime deal holders, confirm your grandfathered access explicitly through a support ticket if the dashboard doesn’t reflect it yet. And if your deployment tooling references any StellarWP-era URLs, test those paths before your next deploy.

---

Read the full announcement on Search Engine Journal → Liquid Web WordPress Plugin Rebrand Triggers Backlash