TYPO3 Core

Hi Daniel,

In my own setup I don't have any problems with this. So I do have some questions for you:

- Which version of TYPO3 do you use?
- Do you have a snippet of the code that is setting your metatag by the API?
- Is it a metatag that is also set by other plugins or by page settings?

Thanks,

Richard

Hi Richard,

I'm using TYPO3 9.5.10

I created a MetaTagService which gets the MetaTagManagerRegistry via inject method (but I also tried it manually with the ObjectManager):

/**
 * @var \TYPO3\CMS\Core\MetaTag\MetaTagManagerRegistry
 */
protected $metaTagManagerRegistry;

/**
 * @param \TYPO3\CMS\Core\MetaTag\MetaTagManagerRegistry $metaTagManagerRegistry
 */
public function injectMetaTagManagerRegistry(MetaTagManagerRegistry $metaTagManagerRegistry)
{
    $this->metaTagManagerRegistry = $metaTagManagerRegistry;
}

Example for "description"-Tag:

$this->metaTagManagerRegistry->getManagerForProperty('description')->addProperty('description', $description, [], true);

In an uncached action the MetaTagManagers properties in the page renderer wont be replaced, the value set by the page settings will be used.
For me it seems like something with the singleton instance isn't working properly, because in my understanding the MetaTagManagerRegistry in the PageRenderer and in my service should be the same object, but they are not.

Greetings
Daniel

Can you try it like:

        $metaTagManagerRegistry = GeneralUtility::makeInstance(MetaTagManagerRegistry::class);

        $ogMetaTagManager = $metaTagManagerRegistry->getManagerForProperty('og:title');
        $ogMetaTagManager->addProperty('og:title', 'Entry from uncached plugin', [], true);

This works for me even on mixed pages. On mixed pages the uncached plugin will always overrule the other cached data.

It worked... but why?

Is there enough time or operations between calling the constructor and the action using the registry, that there's a difference?
(I also instanciated the registry via GeneralUtility but in the constructor)

Maybe I'm lacking knowledge about singleton instances and the core, or is there an issue deep down the rabbit hole?

Even with GeneralUtility you had this problem? Maybe something was wrong with the injection? Should work as far as I know.

I have no hooks or anything special, just moved everything in a service class and used dependency injection