As my recent post on Make WordPress Plugins explains, there’s a serious problem in many themes and plugins using the content filter, and although this problem well known, it has largely been ignored by the WordPress community. :-/
I’d like your feedback on the new Block Filter Output (BFO) feature that will be enabled in WPSSO version 3.47.0 (currently in pre-release) — the Block Filter Output (BFO) feature attempts to make the content filter usable by monitoring the content filter for webpage output, and fixing incorrectly coded filter hooks (that send text to the webpage instead of returning it, as all filter hooks must). WPSSO version 3.47.0 will also enable the “Use WordPress Content Filters” option by default, and use the BFO feature to report any content filter issues.
If you are a Pro version user, you can try the latest pre-release / release candidate version by selecting the “Release Candidate and Up” version filter for WPSSO under the SSO > Update Manager settings page. Let me know if WPSSO reports any issues with your content filters — hopefully it won’t, but if it does, you’ll have the necessary information to contact the theme or plugin author and have them fix their code. ;-)
The “Social Settings” metabox, shown at the bottom of every post / page, term, and user editing page, has been renamed to “Social and Search Optimization” in the latest version of NextGEN Facebook (aka NGFB) and WPSSO (v8.46.0 and v3.46.0 respectively).
The “NGFB” top menu item has also been renamed to “NGFB SSO” and a “Social and Search Optimization” tagline has been added to the top of every settings page (50% transparent). The top menu item for WPSSO has not changed, and is still named “SSO”. :-)
WPSSO v3.40.3-1 plugin has been released (see the complete Changelog here) — this new version adds a custom “Product Condition” option in the Social Settings metabox, along with updating the minimum & recommended versions for WordPress and PHP.
The new “Product Condition” option will be visible only if the Open Graph
og:type meta tag value is a “product” — which is the default value for all product pages from Easy Digital Downloads, MarketPress – WordPress eCommerce, WooCommerce, WP eCommerce, and most other e-commerce plugins (developers can also hook the ‘wpsso_og_type’ filter to change the default value – see the complete list of filters here).
WPSSO v3.40.0-1 has been released (see the complete Changelog here) — this new version adds custom Product Availability, Price and Currency options to the Social Settings metabox.
These options will be visible only if the Open Graph
og:type meta tag value is a “product” — which is the default value for all product pages from Easy Digital Downloads, MarketPress – WordPress eCommerce, WooCommerce, WP eCommerce, and most other e-commerce plugins that use a “product” custom post type (developers can also hook the ‘wpsso_og_type’ filter to change the default value – see the complete list of filters here).
Are you using Yoast SEO in combination with WPSSO?
Have you used Yoast SEO in the past, and would like to read / import its social meta as default values for the WPSSO Social Settings metabox?
WPSSO version 3.38.1-1 (released earlier today) includes additional support for Yoast SEO — When the “Use Yoast SEO Social Meta” option is enabled under the SSO Advanced > Social / Custom Meta tab, WPSSO will read / import Yoast SEO social meta for Posts, Terms, and Users — the Yoast SEO plugin does not have to be active or even installed to use this feature.
An active Yoast SEO plugin does offer a few more integration features though, including the expansion of Yoast SEO variables and custom canonical URLs, but is not required to read / import Yoast SEO custom meta for Posts, Terms, and Users.
The NextGEN Facebook (NGFB) and WPSSO plugins offer a “Meta Property Containers” option that you can enable / disable under their General Settings > Specific Websites and Publishers > Google / Schema tab. There are several ways to include Schema markup in webpages (see an Introduction to Structured Data from Google for examples):
- JSON-LD machine-readable scripts for Google (see WPSSO JSON extension).
- Microdata and RDFa markup of HTML tag attributes in theme templates (not recommended).
- HTML meta tags in the webpage head section.
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).
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.
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/>';