Thank you for trusting us by upgrading to TSF 4.0.0 earlier! We’ve received many warm and welcoming responses, and we’re very grateful.

Even though we churned 40% of the code, we only confirmed two bugs in that update. This minor update addresses those bugs.

Our users reported some admin scripting issues when updating from v3.2.4 to v4.0. These issues are out of our reach, and we provided several solutions in this post.

Haven’t caught up with the v4.0 major release yet? Check out the 4.0.0 changelog, and read our foreword on v4.0.

Detailed log

> View code changes.
> View closed issues.

For everyone

• Fixed:
  • Page-as-archive (confirmed: WooCommerce shop pages) pages no longer take SEO post-meta from the last post listed.
    • This wasn’t an issue with the blog-as-page page, because the code trickles down differently there.

For developers

• Changed:
  • the_seo_framework()->get_post_meta_item() will now fall back using the_seo_framework()->get_the_real_ID() when an empty ID is supplied.
  • the_seo_framework()->fetch_excerpt() will no longer trust WordPress to get the right post. Instead, it fetches the real post ID for the query.
  • the_seo_framework()->get_current_term_meta() now uses the filterable the_seo_framework()->get_the_real_ID() function.
  • the_seo_framework()->get_excerpt_by_id() second parameter $id now defaults to int 0, instead of an empty string. This affects nothing.
• Fixed:
  • the_seo_framework_sitemap_additional_urls filter now works again as intended. Note that our API example uses deprecated functions. We’ll update the API documentation soon™.