You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While this is an issue on my project, I have also verified that it is occurring on another project using this framework.
When passing useYoastHtml into the Headless app component, the page metadata within the document head seems to be correct, but when navigating around the site via internal links, many of the fields don't update. The title component updates, but from what I can see, other fields don't.
Steps to Reproduce
Navigate to a page on a site using the useYoastHTML option and open the document head in the Elements tab of your browser dev tools.
Click an internal link on the page.
Notice that the title updates but nothing else in the head.
Completely refresh the page and see that the head does have the expected content.
Screenshots, screen recording, code snippet
No response
Environment information
No response
WordPress information
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
I can replicate on your project but on the default project 🤔 .
This issue has been haunting us for a while.... In the past I was able to replicate this issue only when GTM was being added to the page but it doesn't seem to be the case now.
What I think it's happening though is that the page ends up with both the previous values and the new ones, so we need to find a way to clear up the old meta tags.
Describe the bug
While this is an issue on my project, I have also verified that it is occurring on another project using this framework.
When passing
useYoastHtml
into the Headless app component, the page metadata within the documenthead
seems to be correct, but when navigating around the site via internal links, many of the fields don't update. Thetitle
component updates, but from what I can see, other fields don't.Steps to Reproduce
Screenshots, screen recording, code snippet
No response
Environment information
No response
WordPress information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: