📆 This is the September 2022 edition of “This Month in WordPress with CodeinWP.”
Hey, WordPress fans. We are back with another batch of WordPress news, covering everything notable that happened in the last 30 days in the world of WordPress.
In the largest bit of news last month, WordPress.org got a big redesign of its homepage and download page. Love it? Hate it? “Meh” it? Let us know in the comments below…
Beyond that, you might be surprised by just how big Cloudways was, as it just got acquired for not that far off half a billion dollars.
DesktopServer is also saying goodbye and shutting down for good, while we have a few other news pieces related to WordPress itself and the broader WordPress business space.
Let’s get to the news:
September 2022 WordPress News with CodeinWP
WordPress.org gets a new homepage and download page
In one of the biggest bits of news this month, WordPress.org finally got its new homepage and download page.
As we’ve documented over our news posts, WordPress.org has slowly been getting a facelift, starting with the header and now moving on to some of the core pages.
It doesn’t get much more “core” than the homepage and download page, as these are probably the two most important pages for people looking into self-hosting WordPress.
In terms of the design itself…well, I don’t love it, especially the copy that they’ve chosen to go with it. “Publish your passion” seems quite vague and like it misses out on the true benefit of using WordPress (WordPress.com seems to be able to capture the value of WordPress a lot better).
There are also some other quirks, such as the copy assuming that the visitor already has a solid understanding of how WordPress works and what blocks are.
What’s more interesting, however, is the behind-the-scenes of how these pages got updated.
It seemed like it took quite a bit of time, mostly because the team couldn’t get it done with the native block editor experience…which maybe isn’t the best look given how much the new design promotes the block editor.
Things got a bit testy when Matt Mullenweg essentially suggested it was a waste of time to create a block-based theme for the redesign when they could code it faster by implementing the design directly.
While I don’t disagree, that’s not exactly a ringing endorsement of the block editor when other WordPress users are supposed to do everything using block-based themes.
Jon Brown’s comment on the WP Tavern post about the release kind of sums up my own feelings:
To prove that the block editor could get the job done, Jamie Marsland spent 20 minutes recreating the homepage in the block editor. You can watch it in real-time in this YouTube video or check out the finished product on Twitter.
It’s not perfect and it would still require some cleaning up, but it is an interesting take on the saga.
What do you think of the new design? Let us know in the comments!
DigitalOcean acquires Cloudways for $350 million
This one isn’t WordPress-specific, but it is a massive acquisition that will touch a lot of WordPress users.
In August, DigitalOcean announced that it was acquiring Cloudways in a massive $350 million cash deal.
First: wow. I knew that Cloudways was doing well, but I didn’t know that it was doing $350 million in cash well.
Second, I, and a lot of other people, will be interested in seeing how this affects Cloudways’ offerings.
If you’re not familiar with Cloudways, it’s essentially a mix between a traditional managed hosting service and a server control panel.
Rather than offering its own infrastructure, Cloudways lets users choose their preferred setup from five different cloud hosting providers – DigitalOcean, Vultr, Linode, Google Cloud, and AWS. From there, Cloudways handles provisioning and maintaining the server and it works pretty much the same as traditional website hosting.
Now that DigitalOcean owns Cloudways, the big question is what happens to the integrations with those other cloud hosting providers:
- Will everything stay the same?
- Will DigitalOcean start promoting its own products even more? I say “even more” because DigitalOcean was always listed first on Cloudways’ pricing pages, which suggests some type of partnership.
- Will DigitalOcean move away from offering integrations with competing products?
Based on early statements, DigitalOcean seems to be suggesting that they’ll go with the “everything stay the same” approach:
However, it’s worth pointing out the “for now” part of that statement.
Overall, it will be interesting to see how this acquisition unfolds going forward.
If you’re worried and interested in some alternatives, I’d recommend looking at tools like RunCloud, SpinupWP, and GridPane. While they’re not exactly the same as Cloudways because they don’t bundle in the cloud hosting, they do use the approach at a basic level.
DesktopServer, a local WordPress development tool, is shutting down for good
In a sad bit of news, ServerPress announced that it would be shutting down the DesktopServer local WordPress development tool after 12 years in business (along with the ServerPress business in general).
To my knowledge, DesktopServer was one of the first WordPress-specific local development tools and it offered a number of convenient features for WordPress users.
The DesktopServer team had been working on a new version (5.0), but stopped working on it after coming to the conclusion that it didn’t have much chance of achieving a high market share.
To be honest, this doesn’t really surprise me. Competition in this space has really heated up, most notably from managed WordPress hosts releasing free local development tools as a value-add/attraction for their hosting customers.
For example, Flywheel (and subsequently WP Engine) started this trend with Local WP. Then, Kinsta also got into the mix with DevKinsta.
Given that both of those tools have functional and unlimited free versions, it’s hard to justify the cost for DesktopServer, even if it is/was a solid tool.
Not to mention, there are also lots of new local development options that aren’t specific to WordPress, but still work well for WordPress sites.
I think the ServerPress team is handling this in a really fair way, though. ServerPress will continue supporting people with a license until their subscription expires, including assisting them with migrating to another tool.
There is a chance that ServerPress either sells or open-sources the DesktopServer code, but there’s no official news on that yet.
To see some other options, you can read our full collection of the best WordPress local development tools.
WP-Optimize alleged to artificially boost its optimization scores
If you’ve ever dug into WordPress performance optimization, you’ve probably noticed a really annoying trend:
A lot of users, especially on the more casual end of things, care more about their sites’ “optimization scores” than they do about their sites’ actual performance.
Sure, their site might load in under one second for all visitors, but they only got a 79 in their speed test tool, so clearly something is wrong.
Perhaps it’s no surprise, then, that some WordPress performance plugins would go out of their way to boost performance scores in any way possible.
This leads me to this tweet from Gijo Varghese, who makes the popular FlyingPress optimization plugin, as well as a number of free optimization tools.
WP-Optimize is a comprehensive WordPress performance plugin that was acquired by the same team behind UpdraftPlus.
If true, this would harken back to the Volkswagen emissions scandal, where Volkswagen was artificially lowering emissions but only when being tested. In the real world, emissions were up to 40X higher.
In a response to inquiries from WP Tavern, David Anderson of UpdraftPlus said that the code was added as part of including code from a fork of the Fast Velocity Minify plugin and that the code hadn’t been touched since initially merging it into the WP-Optimize plugin.
Overall, I’ve been a happy user of UpdraftPlus for a long time, so I’m inclined to give them the benefit of the doubt that there wasn’t anything intentionally sinister going on. Still, it shouldn’t have happened.
Either way, this is a good reminder that, when it comes to WordPress performance, you should always focus on the actual experiences of your human visitors, rather than nebulous optimization “scores.”
You may also be interested in:
- #WCEU Online, Google and GitHub Free Services, Zoom Data Breach 🗞️ May 2020 WordPress News w/ CodeinWP
- ManageWP.org Closed, Astra News, #WCEU 2021 Online, Unsplash Plugin 🗞️ August 2020 WordPress News w/ CodeinWP
- No New Default Theme? More Pricing Changes, Possible “FSE” Name Change 🗞️ August 2022 WordPress News w/ CodeinWP
Newsletter Glue ditches WordPress.org to go all premium
A lot of plugin developers like the WordPress.org plugin directory because it gives them access to a large audience.
However, there are also some downsides, most notably some…entitled users, so to speak, who want high-quality support from a free extension.
Still, most developers either bypass the directory from the beginning (e.g., Gravity Forms) or put up with the demands of supporting those free users in return for the exposure that it brings them.
That’s why I thought it was interesting that Newsletter Glue made the decision to officially shut down its existing free WordPress.org plugin to shift to an all-premium approach (after a few months of forewarning – they didn’t do it out of the blue).
The WordPress.org page is officially disabled as of August 15.
In an interview with WP Tavern, Leslie Sim of Newsletter Glue said that they just hadn’t set up the free-to-premium experience in an optimal way.
For example, users had to delete the free version of the plugin and install a separate premium plugin, which meant that Newsletter Glue’s “active installs” count at WordPress.org would stay unrealistically low (as the “active install” count would actually go down if someone upgraded to premium).
If you’re planning to release your own plugin or theme, this is a good reminder that you’ll want to think about these types of implementations before you go live.
WebP by default is on hold (again)
Will they or won’t they? That’s been the question about default WebP usage in the WordPress core.
By “default,” I mean automatically generating WebP versions of newly uploaded JPEG images (which would essentially double the number of image files on the server).
Even though much of the main work had already been merged into the upcoming WordPress 6.1 release, it appears that it is now “on hold” after objections from a number of WordPress lead developers.
Common complaints about the implementation are as follows:
- It will double the number of image files on the server.
- It dramatically increases the processing required for uploading images, as the server would now need to additionally convert them to WebP. This could also cause image uploads to fail more often.
Overall, I tend to agree that this just doesn’t make sense as a core feature, at least in its current implementation.
If users actually want to use WebP images, they have tons of options, including both converting the images themselves or using a plugin like Optimole that dynamically optimizes images in real time.
It also seems like Google-sponsored developers are the ones driving the change, which could be a bit of a conflict of interest given that Google also developed the WebP format.
Overall, the push for WebP by default is definitely not dead, but it still remains to be seen when and how the implementation will arrive.
That sums up our September 2022 WordPress news roundup. Anything we missed?
Don’t forget to join our crash course on speeding up your WordPress site. Learn more below:
Layout and presentation by Karol K.