Hi @casper434,
My apologies for the late reply.
- There’s a bug with TSF 2.9.2: When your home page is a blog, some special pages have incorrect metadata. This will be fixed in 2.9.3.
- If you didn’t encounter that bug, it might be that the IDX plugin doesn’t correctly communicate with WordPress queries. Instead, it rather incorporates its own mechanism outside of the API. Therefore, TSF can’t fetch set titles. To prevent this bug, you also require TSF 2.9.3.
TSF 2.9.3 will be released this week, and it’s currently being tested on various websites.
For 1, in detail:
Various fixes across non-taxonomical archives, i.e. ones that you can’t edit, have noindex set by default, and have no ID assigned:
- These no longer share the same cache key as the home page.
- This fixes numerous object caching issues.
- These no longer use the home page Open Graph image.
- These no longer use the auto-generated description meant for the home page.
- These now listen to the archive option for
rel=next/prev
links, instead of the home page option.
For 2, in detail:
You can use an upcoming filter that disables The SEO Framework’s title output in specific scenarios.
It looks like this, and I suggest you’d try it when 2.9.3 comes out:
add_action( 'the_seo_framework_init', function() {
if ( 'my-post-type' === get_post_type() ) {
add_filter( 'the_seo_framework_overwrite_titles', '__return_false' );
}
} );
A free extension is planned that will make your life easier, rather than jumping to filters.
Another free extension is planned that might also help with your specific scenario.
That said, for both extensions, there’s no ETA.