The SEO Framework

★︎ My account
  • Extensions
  • Documentation
  • Pricing
  1. Home
  2. Plugin Changelog
  3. 2.6.6 - Semantic Structures

2.6.6 – Semantic Structures

June 14, 2016 by Sybre Waaijer
Updated December 18, 2016

Changelog

Release date:

  • June 14th 2016

Summarized

  • Page builders are great for if you want to style your website, and when you want to do it fast.
  • So from this update the Divi Builder, Visual Composer, Beaver Builder, and the Page Builder by SiteOrigin are now fully supported.
  • Various bugs have also been fixed, to improve your experience. One particular bugfix is related to Polylang; this bugfix should improve performance and reduce other bugs from happening as well.
  • The Automated and Manual description output has been improved in several ways as well.
  • For developers, a class has been removed. All functions within have been moved to more suitable classes. This change will reduce server resource usage and increase overall performance.

SEO Tip of the Update – Know your Keywords:

  • To know how your website is found, sign up for Google Search Console. Over a couple of days (or weeks), elegant data has been accumulated about your website.
  • When you go to the Search Analytics within the Search Console, you’ll see a list of queries people have used to find your website.
  • The queries can be used as keywords, they are excellent starting points for new post titles and subjects. Go ahead, use them!

For developers – About the class removal:

  • Because the plugin makes use of a “Facade pattern“. And through class extending, all functions within the plugin are available at all times.
  • In trade for increased resource usage this does make the plugin very compatible, faster, and easier to work with.
  • This plugin serves one single responsibility: Outputting SEO data, and determining the reason why. Therefore, although it looks like a “God object“, it’s not.
  • Please keep in mind that all functions from any class are available through the “Facade object”. Because of this, the class removal shouldn’t cause issues for developers.
  • You can call this “Facade object” through a single cached function (rather than a global variable), this cached function is the_seo_framework().
  • If you wish to extend this plugin, feel free to ask me for any details or suggestions at the Support forums.

Detailed Log:

For everyone:

  • Added:
    • Page Builder detection, so no more incorrect descriptions can be created when a page builder. The following page builders are now supported, and when detected, the found content will be omitted from the description generation:
      • Divi Builder by Elegant Themes
      • Visual Composer by WPBakery
      • Page Builder by SiteOrigin
      • Beaver Builder by Fastline Media
  • Improved:
    • Automated Term SEO Descriptions from WordPress Core Term Descriptions no longer allows for line breaks and are instead replaced with spaces.
    • Automated Author SEO Descriptions from WordPress Core Author Biography no longer allows for line breaks and are instead replaced with spaces.
    • The Automated Description Excerpt now has one extra trimming parse for removing leading spaces.
    • When multiple spaces are found subsequently within the description, they’re now converted to a single space.
  • Updated:
    • Because of the page builder detection, all previous description transients have been invalidated and will be cleaned out from the database automatically within 7 days.
  • Fixed:
    • Incorrect descriptions were parsed in The SEO Bar on Taxonomies and Terms when a custom description is filled in.
    • On update, this plugin no longer flushes the WordPress Rewrite Engine to prevent missing rewrite data.
    • No more Custom Fields will be produced by this plugin on singular post types.
    • Polylang can no longer cause an incorrect query cache, this means that incorrect data is no longer being output on the front page.
  • Note:
    • From this update, in theory, when not flushing the rewrite data on plugin update, it’s possible that the sitemap will not be outputted correctly.
    • In practice, this won’t be the case; unless you’re updating the plugin with SEO Settings saved prior to The SEO Framework 2.2.9.

For developers:

  • Added:
    • The cache key base is now shown within the debugger title on the front-end and edit pages.
    • The cached query output is now shown within the debugger.
    • AutoDescription_Query::get_the_real_ID() now also works on Terms and Taxonomies within the term edit screens.
  • Improved:
    • The static functions related to plugin (de-)activation have been moved outside of their class, into (marked private) functions to reduce memory usage on.
    • Slightly reduced memory usage of AutoDescription_Load::call_function() by reusing variables.
    • Replaced seconds calculations with predefined WordPress constants.
    • AutoDescription_Generate_Url::get_paged_url() third parameter $post_id now also fetches the content for <!--nextpage--> accordingly, rather than what’s determined through the loop.
    • Removed the saved_flag singular post meta, as it’s redundant and caused a Custom Field to show up.
    • The expected/current meta output doesn’t add onto debug values.
    • The term data is now injected late at get_header or current_screen.
    • AutoDescription_Generate_image::get_image_from_post_thumbnail() now re-parses arguments when none are supplied.
  • Changed:
    • AutoDescription_Generate_Description::trim_excerpt() is now public.
    • AutoDescription_PostData::fetch_post_by_id() has gained an $output parameter, default ARRAY_A. All linked functions now fetch the post data as an object instead of an array.
    • AutoDescription_TermData::get_admin_term_id() has been moved to class AutoDescription_Query.
    • get_term_filter(), get_terms_filter(), taxonomy_seo_save() and term_meta_delete() have been moved to class AutoDescription_TermData from class AutoDescription_PageOptions.
    • inpost_seo_save() and save_custom_fields() have been moved to class AutoDescription_PostData from class AutoDescription_PageOptions.
  • Removed:
    • Public static function AutoDescription_Sitemaps::flush_rewrite_rules_activation, not deprecated as access was private.
    • Public static function AutoDescription_Sitemaps::flush_rewrite_rules_deactivation, not deprecated as access was private.
    • Class AutoDescription_PageOptions has been removed and unloaded to save memory.
    • Variable The_SEO_Framework_Load::debug_time, it was never used.
  • Deprecated:
    • AutoDescription_Load::the_seo_framework_version(). It’s no longer used within the plugin and serves no purpose.
  • Fixed:
    • Plausible PHP warning on terms and taxonomies when fetching data.
    • LD+Json transient state is now correctly reflected in the debug output when the output is an empty string.
    • AutoDescription_Query::is_feed()‘s first parameter no longer crashes site when supplying an array to determine state.
  • Filter Notes:
    • New:
      • (bool) the_seo_framework_detect_page_builder
      • (bool) the_seo_framework_do_shortcodes_in_description
      • (bool) the_seo_framework_do_shortcodes_in_title
  • Other:
    • Cleaned up code, quite a lot.
Filed Under: The SEO Framework Changelog

About Sybre Waaijer

Developer of The SEO Framework plugins.
Twitter  GitHub  WordPress

Looking for something?

Do more with extensions

Title Fix

View extension
Running an outdated theme? Use this.

Focus

View extension
Rank higher with a focus on keywords and subjects.

Get Extension Manager

Commercial

The SEO Framework
Trademark of CyberWire B.V.
Leidse Schouw 2
2408 AE Alphen a/d Rijn
The Netherlands
KvK: 83230076
BTW/VAT: NL862781322B01

Twitter  GitHub

Professional

Pricing
About
Support
Press

Rational

Blog
Privacy Policy
Terms and Conditions
Refund Policy

Practical

Documentation
TSF on WordPress
TSF on GitHub
TSFEM on here
TSFEM on GitHub
Feature Highlights

Using Analytics in 2025 › The SEO Framework