Sybre Waaijer
Sybre Waaijer
Hi @birdbrainsolutions Thanks for your interest in supporting us! Could you forward your ideas to https://tsf.fyi/contact? I'll be sure that Pierre received it. Thanks!
Candidate for 3.1.0. But, I don't want to rush this as it's a vital component and it needs to be done perfectly.
Maybe later, it's not pressing.
In TSF 4.0, we revised how post-metadata is handled, with this issue in mind. See the [post-data.class.php](https://github.com/sybrew/the-seo-framework/blob/master/inc/classes/post-data.class.php) file.
When we move to this method of storing data, plugins like "Better Search and Replace", and possibly "WP-Optimize", will annihilate the metadata as they pass over it. [Here's one recent...
This filter cannot apply to images taken from the content, for which we now use a regular expression. To workaround that issue, we'd have to perform multiple database requests every...
> To workaround that issue, we'd have to perform multiple database requests every time someone visits a post to obtain the IDs, which isn't ideal. We could store the attachment...
The parser already strips duplicated image URLs. We can safely forego this implementation until the blocker is resolved (#185).
Since WordPress 5.2, the following filter is available: `post_column_taxonomy_links` It should allow us to implement this enhancement.
Unfortunately, the `post_column_taxonomy_links` filter doesn't allow us to augment the output. Since the filter doesn't pass the post object, we have no way to (reliably) retrieve the current post object's...