WPSSO Schema JSON-LD Markup (WPSSO JSON) version 1.11.1-1 has been released and features improved markup for the Schema item types Blog, CollectionPage, ProfilePage, and SearchResultsPage. Each of these “archive” page Schema types now include a “hasPart” property to list posts in the current view (WordPress blog home page, date / category / tag archive pages etc, and search results).
NGFB version 8.37.2-1 and WPSSO version 3.37.2-1 have also been released. The “Item Type for Home Page” option has been replaced by two new options — “Item Type for Blog Home Page” and “Item Type for Static Home Page” — allowing you to select different Schema types for each. The WordPress blog home page defaults to https://schema.org/Blog, with posts listed in the JSON-LD “hasPart” property (WPSSO JSON extension required), where-as the static home page defaults to https://schema.org/WebSite.
WordPress Social Sharing Optimization (WPSSO) version 3.37.0-2 has been released, along with updates to all its extensions. This latest WPSSO version includes several new options to fine-tune WPSSO’s internal caching features. The previous “Object Cache Expiry” option has been replaced with 7 new options:
- Head Markup Array Cache Expiry (default 3 days).
- Shortened URL Cache Expiry (default 1 week).
- List Column Content Cache Expiry (default 1 week).
- Filtered Content Text Cache Expiry (default 1 hour).
- Get Image (URL) Size Cache Expiry (default 1 day).
- Article Topics Array Cache Expiry (4 weeks).
- Schema Types Array Cache Expiry (4 weeks).
The NextGEN Facebook (NGFB) and WPSSO plugins are updated every 1-2 weeks to enhance performance, improve existing features and add new functionality — all plugins and extensions have been updated at least once this past month. Don’t forget to install the latest NGFB and WPSSO updates from your WordPress dashboard. ;-)
If you’re using the WPSSO Schema JSON-LD Markup (WPSSO JSON) extension (and if not, you really should), you may have noticed that Google’s Schema validation tools can pickup additional incomplete / inaccurate Schema markup from your theme templates. WPSSO JSON defines its JSON-LD markup as the “main entity” for the webpage — so Google will prefer this markup over any other found in the webpage — but you may still want to cleanup that incomplete / inaccurate Schema Microdata from your theme templates. The new WPSSO Strip Schema Microdata (WPSSO SSM) extension is a Free plugin that removes Schema Microdata markup from the webpage body section automatically, leaving the Schema JSON-LD markup as the only Schema markup in the webpage.
Wondering about the post meta your theme and/or plugins might be creating?
Want to find the name of a specific post meta key?
Need some help debugging your post meta?
The JSM’s Show Post Meta plugin displays all post meta (aka custom fields) keys and their unserialized values in a metabox at the bottom of post editing pages.
There are no plugin settings — simply install and activate the plugin.
WPSSO Schema JSON-LD Markup (WPSSO JSON) version 1.10.0-1 has been released, and includes several improvements for Pinterest and the Schema Recipe markup.
Although previous versions of WPSSO JSON included basic support for the Schema Recipe markup, finding an elegant way to manage ingredients — without duplicating existing theme and/or 3rd party ingredient management — was still on the To-Do list. Thanks to the helpful suggestions of a customer with a recipe website, I was able to include recipe integration features in this version.
WordPress Social Sharing Optimization (WPSSO) version 3.33.1-1 has been released, along with updates for the WPSSO JSON, WPSSO ORG, and WPSSO PLM extensions.
One of the big features for this new release is the added support for the Schema http://schema.org/Event type and its sub-types (DanceEvent, MusicEvent, etc.), along with integration of The Events Calendar plugin. The Events Calendar plugin already includes basic JSON-LD support, but the WPSSO Organization Markup (WPSSO ORG) and WPSSO Place / Location and Local Business Meta (WPSSO PLM) extensions allow you to include much more detail about the organizer (as an actual Organization instead of a Person), select a performer for the event, along with WPSSO’s standard support for images, videos, etc. The combination of WPSSO Pro and all three Pro extensions can provide extensive Schema markup about your event — see the following Schema JSON-LD markup for an example.
If you use a caching plugin, you may have an option to include custom PHP code when flushing the cache manually — for example, Comet Cache has an “Evaluate Custom PHP Code when Clearing the Cache?” option where you can enter additional PHP code to execute when clearing the cache manually. Adding the following code will also clear the WPSSO object cache when clearing the webpage cache:
| || |
if ( function_exists( 'wpsso_clear_all_cache' ) )
echo 'Cleared '.wpsso_clear_all_cache().
' files and objects from the WPSSO cache.<br/>';
WordPress Social Sharing Optimization (WPSSO) version 3.31.0-1 has been released, and includes several interesting changes — The display of Free / Pro version features in the settings pages sidebar has been improved by adding icons and grouping similar features. And the big change for this version is the support of post / page co-authors and guest authors using the Co-Authors Plus plugin. WPSSO Pro will extend the list of Contact Info under the Guest Author profile page, and include co-authors and guest authors (name, description / bio, image, and all contact URLs) in post / page meta tags. The WPSSO Schema JSON-LD Markup extension has also been updated to add co-authors and guest authors to all Schema types that include author information (Article, NewsArticle, TechArticle, BlogPosting, WebPage, etc.).
If you need to create an array of store hours (for example), the following function can generate an associative array of values quickly, with the hours formatted and stepped (every hour, 30 mins, etc.) as you wish.
I’ve seen similar functions using DateTime(), but we’re already working with timestamps, so there’s really no need.