Dockside Press
On August 20th and August 21st, the official WordPress account on X went on the offensive against two different WordPress companies. These attacks, once again, do nothing beneficial for the community.
The first attack was against WP Engine, who posted on July 29th that they were partnering with BigCommerce (CMRC) in creating their own e-commerces solution. The attack was simply a graph showing that BigCommerce’s stocks have dropped since this announcement. However, the large drop occurred on August 6th, after Commerce.com announced that they missed Q2 2026 revenue goals. The merit of the decline being related solely to WP Engine is small. It is also highly unlikely that WP Engine’s announcement would’ve increased Q2 revenue goals enough in 8 days. We’ll have to see how Q3 does.
As a side note, it is interesting that WP Engine (owned by Silver Lake) would invest in BigCommerce rather than find a way to utilize EverCommerce.
The second attack was related to a compatibility issue with WP Rocket and WordPress 7.1. Now, before we go any further, WP Rocket was made aware of this issue on GitHub on July 6, long before the official WordPress 7.1 release. So it goes without saying that WP Rocket could’ve, and should’ve addressed this before the official release of WordPress 7.1.
That said, the comments made by WordPress on X are excruciating. The comments point out flaws of using plugins not on the official repository, the lack of awareness by the WP Rocket team, and even goes after a GitHub contributor who uses an allegedly copyrighted name and trademark.
The problem with both of these attacks aren’t necessarily that they are right, wrong, or in-between. It is simply the fact that the official WordPress account on X is attacking other companies in the WordPress ecosystem and continuing to cause doubt, confusion, and instability within the WordPress community.
Some of these could’ve been handled quietly or even more tactfully, instead of unprofessionally blatant attacks. If users within the WordPress community want to point these things out, that is one thing, but using official community resources should be highly discouraged.
