Replies: 1 comment 5 replies
-
|
Hi, the meta tags extension is not compatible with version 2 and should not be used in new sites anymore. All its functionality is implemented in version 2 out of the box. That also includes the option to dynamically create open-graph images if no image is defined explicitly. So you can safely remove the extension. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @marcantondahmen,
I'm trying to use v2 alpha for the first time but I'm facing an issue with the meta-tags extension in admin mode.
In my page, my first
<p>tag is<p class="lead mt-1">@{ heroSubtitle }</p>line, in admin mode, it messes up with the code of my page because I guess the meta-tags extension looks for the first paragraph in my page and uses the found element as meta description, thus resulting in that... "abomination" :...and messing up the entire
<head>structure because of the admin mode's additional tags (forcing it to close too soon, to open the<body>early, and so on).As much as I liked the elegance of that extension and would have liked to use it properly, I tried to remove the inclusion of the meta-tags extension in my template files to deal with meta myself, but even that way, the extension continues to load and generate the meta tags on top of my page. I get that it is probably an composer autoload issue, but I'm not so used to work with composer, so I don't know how to get passed it. I even tried to
composer remove automad/standard-v1andcomposer remove automad/meta-tagsbut no luck... Meta are still automatically generated at the top of my<head>when it should not. Here' my code, for reference (it looks almost exactly like the automad/standard one) :The only workaround I found was to put a static HTML commented
<!-- <p>Fake description</p> -->at the top of my<body>so that becomes the first paragraph and leaves me alone... But that's not a viable solution in production.Would you (or anyone else) have a proper solution for this issue, preferably to make the extension work as expected, but even if it means disabling the extension and doing the meta part myself ?
Thank you in advance !
Beta Was this translation helpful? Give feedback.
All reactions