A number of WPSSO Core customers using JetPack have reported that shortlinks no longer work for Custom Post Types (CPTs). According to JetPack, this is a feature, and PHP code specifically for this JetPack feature must be added to your functions.php file — or an additional property added to the Custom Post Type definition. Unless you have made these PHP code changes, JetPack will break the WordPress
wp_get_shortlink() function for all Custom Post Types.
Because of this new JetPack feature, older versions of WPSSO Core (before version 3.48.7) may show a warning on Custom Post Type editing pages that the post shortlink is empty — which also prevents WPSSO Core from checking the current post webpage for duplicate meta tags. Additionally, the WordPress “Get Shortlink” button on post editing pages and the
link rel="shortlink" HTML tag in webpage headers will be missing.
WPSSO Core version 3.48.7 now checks for empty values returned by the
wp_get_shortlink() function and provides a correct shortlink URL. This not only addresses the new Jetpack feature, but also fixes incorrectly coded themes that disable the
link rel="shortlink" HTML tag by returning an empty shortlink value (a violation of the WordPress theme guidelines).
The upcoming WPSSO Core v3.48.0 release includes several changes to cache handling methods and filters.
If your site still uses the default WordPress transient cache in the database options table (most WordPress sites), you’ll find a new “Cache Status” metabox on the SSO > Plugin Dashboard and Features Status page.
If you’re using an external object cache, like APC, Memcache, Redis, Xcache, etc., this new metabox will not be displayed. Support for your chosen external object cache could be added at a later date, depending on user requests and the availability of an API to get (or count) all stored keys by prefix.
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 NextGEN Facebook plugin was forked in 2014 and replaced by the WPSSO Core plugin — they’re both Free and available on WordPress.org, have the same author and developer, the same solid core features and code-base, but WPSSO Core is distributed without the social sharing buttons and their related features. Social sharing buttons are distributed separately, as optional extensions for WPSSO Core. WPSSO Core also provides several other useful and optional extensions:
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).
The WPSSO Schema JSON-LD Markup (WPSSO JSON) v1.13.0-1 extension for WPSSO has been released (see the complete Changelog here) — this latest version adds several custom Recipe Instructions and Nutrition Information options to the Social Settings metabox, along with including some new integration modules for WP Recipe Maker and WP Ultimate Recipes.
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).