WordCamp US 2022, WooCommerce 6.9, New Google Updates 🗞️ October 2022 WordPress News w/ CodeinWP

📆  This is the October 2022 edition of “This Month in WordPress with CodeinWP.” 

Hey, WordPress fans! We are back with you covering the latest WordPress news from the previous month.

Most notably, WordCamp US 2022 went off at the beginning of September, so we have some live streams and recaps to help you relive the event.

Beyond that, WooCommerce released a new version and shared plans for its custom orders table feature, Google slammed publishers with a bunch of search algorithm updates, we share a few cool new WordPress projects, and lots more.

Let’s get all of this month’s news:

📆  This is the October 2022 edition of “This Month in WordPress with CodeinWP.” 

Hey, WordPress fans! We are back with you covering the latest WordPress news from the previous month.

Most notably, WordCamp US 2022 went off at the beginning of September, so we have some live streams and recaps to help you relive the event.

Beyond that, WooCommerce released a new version and shared plans for its custom orders table feature, Google slammed publishers with a bunch of search algorithm updates, we share a few cool new WordPress projects, and lots more.

Let’s get all of this month’s news:

The biggest event from the past month was WordCamp US 2022, which happened on the weekend of September 9th in sunny San Diego, CA.

This is the earliest in the year that the event has happened in a while, which keeps with trends from the past few years.

WordCamp US 2018 happened in December, but subsequent events have shifted to November, then October, and now September.

If you want to catch up, the WordCamp Central YouTube channel has full live streams of both days and both event tracks:

Each video has timestamps to jump around to the different talks.

As usual, a lot of attendees also posted their own WordCamp US 2022 recaps. Here are some of the more detailed ones I found:

If you weren’t able to attend, you can live vicariously through other people’s screenshots and tweets.

WordCamp US

The biggest event from the past month was WordCamp US 2022, which happened on the weekend of September 9th in sunny San Diego, CA.

This is the earliest in the year that the event has happened in a while, which keeps with trends from the past few years.

WordCamp US 2018 happened in December, but subsequent events have shifted to November, then October, and now September.

If you want to catch up, the WordCamp Central YouTube channel has full live streams of both days and both event tracks:

Each video has timestamps to jump around to the different talks.

As usual, a lot of attendees also posted their own WordCamp US 2022 recaps. Here are some of the more detailed ones I found:

If you weren’t able to attend, you can live vicariously through other people’s screenshots and tweets.

WordCamp US

At the aforementioned WordCamp US 2022 event, Matt Mullenweg made another push for a concept known as canonical plugins. More specifically, Mullenweg wants WordPress Make teams to use canonical plugins to offer features to users.

So – what is a canonical plugin?

The basic idea is that it’s a more “official” type of plugin that comes from core contributors, rather than third-party developers.

These plugins would have a closer relationship to the core software than third-party plugins and would also have more inherent trust because they come directly from the community/core developers.

Developers could use these canonical plugins to add essential features that might not otherwise make it into Core.

It also gives those features a chance to grow and mature before possibly making the shift into Core.

An example of this would be the Gutenberg plugin before it was merged into the core in WordPress 5.0 (it also still exists as a place to test cutting-edge features for the block editor).

WP Tavern has a good post on the subject, that includes some of the pros and cons of this approach.

canonical WordPress plugins

At the aforementioned WordCamp US 2022 event, Matt Mullenweg made another push for a concept known as canonical plugins. More specifically, Mullenweg wants WordPress Make teams to use canonical plugins to offer features to users.

So – what is a canonical plugin?

The basic idea is that it’s a more “official” type of plugin that comes from core contributors, rather than third-party developers.

These plugins would have a closer relationship to the core software than third-party plugins and would also have more inherent trust because they come directly from the community/core developers.

Developers could use these canonical plugins to add essential features that might not otherwise make it into Core.

It also gives those features a chance to grow and mature before possibly making the shift into Core.

An example of this would be the Gutenberg plugin before it was merged into the core in WordPress 5.0 (it also still exists as a place to test cutting-edge features for the block editor).

WP Tavern has a good post on the subject, that includes some of the pros and cons of this approach.

canonical WordPress plugins

On September 14, the WooCommerce team released version 6.9 to the world, followed shortly thereafter with version 6.9.1 after discovering a bug that caused issues on some sites due to their PHP versions.

One of the biggest new features is that you’ll now get access to the Cart and Checkout blocks in the core WooCommerce software (whereas previously these blocks were relegated to the experimental WooCommerce Blocks plugin).

These core blocks are important to helping WooCommerce’s block-based approach keep up with visual builders like Elementor, given that Elementor has already had flexible cart and checkout widgets for several months now.

Beyond the new blocks, WooCommerce 6.9 comes with improved product filtering.

The filter will now update the URL without reloading the page. This makes it easy for shoppers to share and access direct links to filters.

Users can also set multiple selections for attribute filters when using dropdowns and the AND query type.

There are plenty of other changes, too, as WooCommerce 6.9 includes 90+ smaller fixes and tweaks.

Here are some relevant links if you want to learn more:

One thing that 6.9 did not include, though, is the custom database table for orders that we mentioned a few news roundups back.

This feature, which has been renamed to High-Performance Order Storage (HPOS), is currently targeted for release in WooCommerce 7.1, which is itself currently slated for release around November.

When it first launches, HPOS will be opt-in for stores. However, the eventual aim is that core is able to turn it on by default (I presume only for new stores). If things go well, this could happen in around a year’s time (August 2023).

Beyond the update to the core software, the WooCommerce team also released WooCommerce Blocks 8.6.0 later in September, which includes a new cross-sells block that should be making its way to the core WooCommerce software at some point.

WooCommerce 6.9

On September 14, the WooCommerce team released version 6.9 to the world, followed shortly thereafter with version 6.9.1 after discovering a bug that caused issues on some sites due to their PHP versions.

One of the biggest new features is that you’ll now get access to the Cart and Checkout blocks in the core WooCommerce software (whereas previously these blocks were relegated to the experimental WooCommerce Blocks plugin).

These core blocks are important to helping WooCommerce’s block-based approach keep up with visual builders like Elementor, given that Elementor has already had flexible cart and checkout widgets for several months now.

Beyond the new blocks, WooCommerce 6.9 comes with improved product filtering.

The filter will now update the URL without reloading the page. This makes it easy for shoppers to share and access direct links to filters.

Users can also set multiple selections for attribute filters when using dropdowns and the AND query type.

There are plenty of other changes, too, as WooCommerce 6.9 includes 90+ smaller fixes and tweaks.

Here are some relevant links if you want to learn more:

One thing that 6.9 did not include, though, is the custom database table for orders that we mentioned a few news roundups back.

This feature, which has been renamed to High-Performance Order Storage (HPOS), is currently targeted for release in WooCommerce 7.1, which is itself currently slated for release around November.

When it first launches, HPOS will be opt-in for stores. However, the eventual aim is that core is able to turn it on by default (I presume only for new stores). If things go well, this could happen in around a year’s time (August 2023).

Beyond the update to the core software, the WooCommerce team also released WooCommerce Blocks 8.6.0 later in September, which includes a new cross-sells block that should be making its way to the core WooCommerce software at some point.

WooCommerce 6.9

If you rely on Google to drive traffic to your WordPress site(s), you might be in for a bit of a ride as Google has just recently released three back-to-back-to-back Google search updates.

On August 25, Google released its “helpful content update,” which completed its rollout on September 9th. As the name suggests, the update aimed to target sites with “unhelpful” content, by giving them a sitewide penalty.

Just a few days after completing the rollout of the helpful content update, Google released another core update starting on September 12th and finishing on September 26th. For this second update, however, Google did not publicize any specific focus.

Finally, Google finished with another iteration of its product reviews update, starting on September 20th and also finishing on September 26th. See the full release log here.

It’s not unheard of for Google to release three updates in short succession like this. However, it does mean that your sites might experience some volatility.

Despite all of these changes, the Semrush Sensor, a chart from SEO tool Semrush that tracks SERP volatility, has remained fairly calm since August 25th, though there were some spikes around the second core update.

Overall, if you write quality content, have an organized content strategy, and implement general white hat SEO best practices, you shouldn’t have anything to fear from Google updates.

Still, there’s always that bit of trepidation whenever Google announces something…

Have your sites experienced any positive or negative shifts? Let us know in the comments!

new Google updates

If you rely on Google to drive traffic to your WordPress site(s), you might be in for a bit of a ride as Google has just recently released three back-to-back-to-back Google search updates.

On August 25, Google released its “helpful content update,” which completed its rollout on September 9th. As the name suggests, the update aimed to target sites with “unhelpful” content, by giving them a sitewide penalty.

Just a few days after completing the rollout of the helpful content update, Google released another core update starting on September 12th and finishing on September 26th. For this second update, however, Google did not publicize any specific focus.

Finally, Google finished with another iteration of its product reviews update, starting on September 20th and also finishing on September 26th. See the full release log here.

It’s not unheard of for Google to release three updates in short succession like this. However, it does mean that your sites might experience some volatility.

Despite all of these changes, the Semrush Sensor, a chart from SEO tool Semrush that tracks SERP volatility, has remained fairly calm since August 25th, though there were some spikes around the second core update.

Overall, if you write quality content, have an organized content strategy, and implement general white hat SEO best practices, you shouldn’t have anything to fear from Google updates.

Still, there’s always that bit of trepidation whenever Google announces something…

Have your sites experienced any positive or negative shifts? Let us know in the comments!

new Google updates

What does spending $477,924 to launch a new blog look like?

If you use WordPress to build content websites, Ionut Neagu posted a very detailed recap of what it’s like trying to launch a finance blog from scratch in 2020 and beyond.

He shares what’s worked, and what hasn’t worked, when it comes to growing FinMasters, our CodeinWP sister-site in the finance space.

You might not have half a million dollars to invest in starting a blog, but you’ll still come away with some good ideas on content strategy, experimentation, creating processes to help make your blog a success, and more.

You can read the full blog post at FinMasters.

WordPress that runs in your web browser? That’s cool!

Adam Zielinski, a WordPress core contributor, published a very cool demo of a new project that runs WordPress entirely in the web browser using WebAssembly.

While it’s still an early prototype and doesn’t support 100% of WordPress functionality yet, this could open up a lot of cool potential use cases such as the following:

  • Creating interactive demos of plugins, themes, patterns, and so on
  • Making WordPress code examples runeditable
  • Creating staging sites that run in your browser

If you’re interested in this project, you can learn more at the GitHub page or check out Adam’s blog post at WordPress.org.

What does spending $477,924 to launch a new blog look like?

If you use WordPress to build content websites, Ionut Neagu posted a very detailed recap of what it’s like trying to launch a finance blog from scratch in 2020 and beyond.

He shares what’s worked, and what hasn’t worked, when it comes to growing FinMasters, our CodeinWP sister-site in the finance space.

You might not have half a million dollars to invest in starting a blog, but you’ll still come away with some good ideas on content strategy, experimentation, creating processes to help make your blog a success, and more.

You can read the full blog post at FinMasters.

WordPress that runs in your web browser? That’s cool!

Adam Zielinski, a WordPress core contributor, published a very cool demo of a new project that runs WordPress entirely in the web browser using WebAssembly.

While it’s still an early prototype and doesn’t support 100% of WordPress functionality yet, this could open up a lot of cool potential use cases such as the following:

  • Creating interactive demos of plugins, themes, patterns, and so on
  • Making WordPress code examples runeditable
  • Creating staging sites that run in your browser

If you’re interested in this project, you can learn more at the GitHub page or check out Adam’s blog post at WordPress.org.

PublishPress acquires MetaSlider

Another month, another WordPress acquisition (though a bit smaller than usual, this time).

In September, PublishPress acquired the popular MetaSlider plugin (used on over 700,000 sites), along with the MetaSlider Lightbox plugin.

Steve Burge, the PublishPress founder, told WP Tavern that the PublishPress team plans to focus on improving the performance of MetaSlider and expanding its ability to work with dynamic content sources.

MetaSlider has bounced around a bit recently, moving from UpdraftPlus to Extendify in 2020 and now to PublishPress.

Hopefully it will have some longevity here – I think the focus on dynamic content is a good bet moving forward given that sliders as a static design element have sort of fallen out of favor.

A big vulnerability in the popular BackupBuddy plugin

BackupBuddy from iThemes is one of the most popular WordPress backup plugins.

In early September, Wordfence posted about a BackupBuddy vulnerability that allowed unauthenticated users to download files, including potentially sensitive files such as the wp-config.php file.

To make matters a little worse, Wordfence looked at its data to discover that malicious actors had been attempting to exploit the vulnerability since August 26.

That’s the bad news…

The good news is that the iThemes team has already patched the vulnerability since September 2nd in version 8.7.5 of the plugin.

If you are using BackupBuddy, make sure to update ASAP as this vulnerability affects BackupBuddy versions 8.5.8.0 to 8.7.4.1.

PublishPress acquires MetaSlider

Another month, another WordPress acquisition (though a bit smaller than usual, this time).

In September, PublishPress acquired the popular MetaSlider plugin (used on over 700,000 sites), along with the MetaSlider Lightbox plugin.

Steve Burge, the PublishPress founder, told WP Tavern that the PublishPress team plans to focus on improving the performance of MetaSlider and expanding its ability to work with dynamic content sources.

MetaSlider has bounced around a bit recently, moving from UpdraftPlus to Extendify in 2020 and now to PublishPress.

Hopefully it will have some longevity here – I think the focus on dynamic content is a good bet moving forward given that sliders as a static design element have sort of fallen out of favor.

A big vulnerability in the popular BackupBuddy plugin

BackupBuddy from iThemes is one of the most popular WordPress backup plugins.

In early September, Wordfence posted about a BackupBuddy vulnerability that allowed unauthenticated users to download files, including potentially sensitive files such as the wp-config.php file.

To make matters a little worse, Wordfence looked at its data to discover that malicious actors had been attempting to exploit the vulnerability since August 26.

That’s the bad news…

The good news is that the iThemes team has already patched the vulnerability since September 2nd in version 8.7.5 of the plugin.

If you are using BackupBuddy, make sure to update ASAP as this vulnerability affects BackupBuddy versions 8.5.8.0 to 8.7.4.1.