I just set up a new project in Typo3 13. I’ve created a sitepackage and so far my test site is running, but: my meta-tags and loading css-files is done inside the body instead of the , as it was ever before by default.
The sitepackage-tutorial told me to include the css-files with fluid as an asset inside my template. So that might be the reason for that and I wonder why the tutorial shows that instead using the typoscript.
My meta-tags are defined in typoscript with page.meta. So why do they get into the body?
I searched the web and asked ChatGPT without success.
Please share the code of your templates.
I just tried this with the site_introduction base package (GitHub - TYPO3-Documentation/site-introduction: Introduction Package Development Environment on #DDEV) - note I had to jump through some hoops to prevent ddev from being wrongly initialized, and had to ensure no “no” site-dummy package was created. See DDEV initializsation · Issue #43 · TYPO3-Documentation/site-introduction · GitHub for that journey.
Once I got it started, I was able to use this:
page = PAGE
page {
10 = PAGEVIEW
10 {
paths {
0 = EXT:my_site_package/Resources/Private/PageView/
10 = {$MySitePackage.template_path}
}
dataProcessing {
# makes content elements available as {content} in Fluid template
10 = page-content
}
}
shortcutIcon = {$MySitePackage.favicon}
meta {
og:site_name = TYPO3
og:site_name.attribute = property
og:site_name.replace = 1
}
}
which set my meta tags in the head section accordingly. So there might be some interference for your at some point. Like chris mentioned it would be good if you can share your full sitepackage example and maybe check if any involved extensions could be involved that cause the unwanted behaviour.
I’ve got news. It allways happens when I add a container-element. If so, the meta-tags and the css includes go into the body. If I remove the container-element or disable it, everything is fine again, so the meta-tags and includes are in the head again.
But what could be the reason for this behavior?
This issue has been reported to the developers of the b13/container extension. Further contributions are welcome there: