In TSF v4.0.5, we brought advanced query protection, oEmbed control for improved Discord sharing, Baidu Search Resource Platform code support, and syntax detection for titles and descriptions.
Social sharing images are now taken from your content intelligently, feeds can now optionally be indexed, and we also improved support for Easy Digital Downloads and Polylang.
In WordPress, we found various query endpoints that can be malformed to create broken pages. Backlinks to these pages can harm your site’s ranking. In this update, we added advanced query protection, which you can enable via the robots meta settings.
The “Connected Social Pages” input fields will now disappear when you empty them. They have never proven to work, and Google has deprecated them. We also removed the transient caching for JSON-LD scripts, as it wasn’t helping anyone.
On the other hand, we added a new feed indexing option, Discord sharing options (oEmbed, theme color), and the aforementioned advanced query protection option. Support for EDD and Polylang has been expanded, and we reintroduced the hyphen option for titles (which is the new default).
In this update, we also bring a few other quality-of-life changes, as well. We added a dozen new filters, touched up the interface, streamlined the query handler, and fixed known corner-case issues and bugs.
With our new extension, Cord, you can start gathering useful data from your visitors with Google Analytics. From this information, you can start tailoring your content to the right audience. Cord also brings Facebook pixel, so you can make sure your ads are shown to the right people, drive more sales, and measure the results of your ads.
In this release, we bring you a new extension, called Cord. We also refactored the settings’ form generator, making it easier to work with.
WordPress 5.3 has a bug where the timezone set in PHP is taken into account when creating permalinks. Since this bug can cause canonical URLs with dates to point to a nonexistent page, we’re sending out this patch where TSF sets the timezone to flat UTC for its front-end generation.
The proper fix in WordPress 5.3.1 is due in about three weeks from now, after which we’ll consider reverting these changes.