-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using a user edited/created page template creates a duplicate viewport meta #36528
Comments
Looks like it could be the same issue as reported here - https://core.trac.wordpress.org/ticket/53743 |
Yeah that looks like it's the same issue. |
This PR included the solution for the title tag: #36133 |
Yes, still an issue on 5.9 beta 3 with Gutenberg trunk. When Gutenberg is not active, the tags are not duplicated. |
Tested with Beta 4 as well, the issues is still there.
|
Bumping as this is still a present issue. |
This no longer seems to be an issue in the latest version of WordPress, Gutenberg and with TT3. |
Description
This is an odd one. If you assign a theme-provided custom page template to a page, the frontend output looks roughly like this.
If you then edit the template in WordPress (not in the theme files) and save, the frontend output now has a duplicate meta viewport tag.
You get the same output if you create a new page template from within the Block Editor.
The issue can be easily reproduced with the Twenty Twenty-Two theme, but has been reproduced in a number of other themes including emptytheme.
I am happy to explore further and work on a fix, but I am not sure where to start looking. If someone can point me to where the frontend output for templates "lives", I will take a look.
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
No response
Environment info
WordPress 5.8.2, Gutenberg 11.9
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: