Describe the bug
In some occasions - I have unfortunately no way to identify these cases, as they seem very, very random - it appears that the og:image and description are not from the entry itself, but the default one from the site it originates from.
We believe this behaviour started when we upgraded to Craft 5.
To reproduce
I have unfortunately no way to reproduce yet. Initially I thought it perhaps had to be related with scheduled content (e.g. content in the future) but that also seems not to be the case.
Expected behaviour
SEO from article is being shown.
Versions
- Plugin version: 5.1.18
- Craft version: 5.8.18
Multisites enabled
Additional information
This site is running in a high-availability cluster, there are running several instances of Craft with Redis being the session backend. There is only 1 database instance.
What I am looking for is help to debug this issue. For now, what the content creators do, is to invalidate the SEOMatic metadata cache via the system utility and they uncache the page via Blitz.
The problem is 100% related in the SEOMatic metadata cache and not Blitz, as the problem remains when the page is being uncached by Blitz.
Describe the bug
In some occasions - I have unfortunately no way to identify these cases, as they seem very, very random - it appears that the og:image and description are not from the entry itself, but the default one from the site it originates from.
We believe this behaviour started when we upgraded to Craft 5.
To reproduce
I have unfortunately no way to reproduce yet. Initially I thought it perhaps had to be related with scheduled content (e.g. content in the future) but that also seems not to be the case.
Expected behaviour
SEO from article is being shown.
Versions
Multisites enabled
Additional information
This site is running in a high-availability cluster, there are running several instances of Craft with Redis being the session backend. There is only 1 database instance.
What I am looking for is help to debug this issue. For now, what the content creators do, is to invalidate the SEOMatic metadata cache via the system utility and they uncache the page via Blitz.
The problem is 100% related in the SEOMatic metadata cache and not Blitz, as the problem remains when the page is being uncached by Blitz.