I recently wrote a plugin to provide missing GTIN, GTIN-8, GTIN-12 (UPC), GTIN-13 (EAN), GTIN-14, ISBN, MPN, Depth, and Volume values for WooCommerce Products and Variations. As part of that plugin, I extended the WordPress search feature to search metadata from WooCommerce products (and their variations). The standard way to extend the WordPress search feature is to hook the “pre_get_posts” action and modify the WP_Query to include additional posts / products in search results. There are some serious drawbacks to doing this – with or without WooCommerce – but especially with WooCommerce.
On March 17th 2020, in response to COVID-19 self-isolation trends, Google published new Schema Event properties for virtual, postponed, and cancelled events.
The latest Premium version of WPSSO Schema JSON-LD Markup provides several customization options for these new Schema Event properties in the Document SSO metabox.
This past month, the Free / Standard versions of WPSSO Core and its WPSSO Schema JSON-LD Markup add-on have also received several new features — most notably, almost all customization options in the Document SSO metabox are now available in the Free / Standard version of WPSSO Core (except those options that require an integration feature in the Premium version to implement, like the video service APIs), and the Free / Standard version of WPSSO Schema JSON-LD Markup now includes all 495 supported Schema types!
Pop quiz! Did you know?
1) WordPress creates thumbnails automatically?
WordPress uses the larger / full-size image you upload to create smaller thumbnail images (see your WordPress Settings > Media page for the complete list of sizes).
For example, a photo gallery page will show small thumbnails of the larger / full-size images you uploaded. Themes will often include the featured image you selected in a predefined image size and location in the webpage.
2) All images must be sharpened after resizing?
This is such a standard process that Photoshop, for example, automatically applies a default amount of sharpening when resizing any image — you must specifically uncheck an option in Photoshop to avoid sharpenning an image during the resize process!
3) WordPress does not sharpen resized images?
Does your website use parent pages and/or categories? Unless you have a very simple site, you’ve probably organized your WordPress pages and categories as parents with child pages / categories.
And have you defined a featured image for a parent page and wished its children used the same featured image automatically?
How about social and search optimization images? If you’re using the WPSSO Core plugin — and have selected a custom image for Facebook, Google, Twitter, and/or Pinterest — would you like the children of that page and/or category to inherit those custom images automatically?
Did you know that WordPress creates thumbnails from images you upload?
You may have already known this — not everyone does, but most WordPress users are aware of this (or at least should be).
Did you also know that all resized images must be sharpened?
This is common knowledge for photography and website design professionals, but probably not for the majority of WordPress users.
And did you also know that WordPress does not sharpen resized images?
I bet that you didn’t know that one… not many people do. ;-)
WordPress creates several different thumbnail / resized images by default (see WordPress Settings > Media page for details) and potentially several more, depending on your theme and plugin settings. It’s not uncommon, for example, for WordPress to create a half-dozen (or more) images from the original image you upload. And in all cases, WordPress does not sharpen or make any adjustments to the resized image it creates!
On April 26th – just two weeks ago – WPSSO Core v4.0.0 was released, which included support for the new Gutenberg editor. Since then, WPSSO Core v4.1.0, v4.2.0, and v4.3.0 were also released (the last one just today), along with WPSSO JSON v1.25.0 and v1.26.0.
In case you missed all the update notices and posts about those versions, the following is a quick summary of the big changes and improvements in both WPSSO Core and its JSON-LD add-on. And at the end of this post, you can also find a summary of our release schedule philosophy, and why we chose to release four big improvements, in four different versions, in just two weeks. ;-)
The release of WordPress 5 and the new Gutenberg editor are just around the corner, and Gutenberg developers still have not tackled a serious design issue with the current Gutenberg notification system — notices in Gutenberg are being displayed over the content area, forcing users to dismiss notifications to gain access to their content — and in some cases, where several non-dismissible notices are displayed, users may not have access to the content area at all.
The notification system in the current version of WordPress is nothing fancy — and can feel a bit intrusive when several notices are displayed at once — but it’s a lot more flexible and functional than the proposed Gutenberg notification system. :-) As an example, here are some typical SSO (Social and Search Optimization) notifications when editing a test post in the current version of WordPress, in the Gutenberg editor, and with the upcoming release of WPSSO Core v4.2.0 that moves SSO notices into the admin toolbar.
The new Gutenberg editor for WordPress v5 may not be ready yet — and I can certainly attest to that, lol — but it’s coming soon, and WPSSO Core is ready for Gutenberg!
This latest version of WPSSO Core (scheduled for release this week) includes several key changes aimed specifically at integrating WPSSO Core with the new Gutenberg editor. The Document SSO (Social and Search Optimization) metabox is now refreshed when the Gutenberg post is saved, and any SSO notices are displayed using the new Gutenberg notification system. The notices themselves have also been improved by including more information about the dismiss button — either simply hiding the notice (Gutenberg default), temporarily dismissing it for 1 hour, 3 months, etc, or dismissing it permanently.
Have you tried the Gutenberg editor yet?
WordPress v5 is coming soon, and if you haven’t tried the new Gutenberg editor in a staging environment (contact your hosting provider for details), then you could be in for a major surprise! Many plugins will not be compatible with Gutenberg, and for those few and rare plugin authors that are still actively maintaining their plugins, updates to support the Gutenberg editor may take some time. Save yourself the headache – install the Gutenberg editor in a staging environment now, and make sure all your plugins are compatible. ;-)
WPSSO Core v4.0.0 beta is available now.
If you’re a WPSSO Core Pro user — and have a staging environment — you can select the “Beta and Up” version filter for WPSSO Core in the SSO > Update Manager settings page, to install and test the latest beta version. You can also re-select the “Stable / Production” version filter at any time to re-install the last stable / production version.