Project

General

Profile

Actions
Copy link

Bug #93383

closed

og:image only works on rootsite with typoscript & rootline-slide

Added by Gabriel Kaufmann / Typoworx NewMedia almost 4 years ago. Updated 4 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2021-01-29
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

My customer requires og:image working on all pages. I tried to fetch the og_image from rootpage (og_image reference).

But it doesn't seem to work on subpages (only rootpage).

og:image {
    required = 1
    attribute = property

    cObject = FILES
    cObject {
        maxItems = 1
        # Notice:
        # og_image has been added to $GLOBALS['TYPO3_CONF_VARS']['FE']['addRootLineFields'] .= ',og_image';
        references.data = fullRootLine: 0, og_image

        renderObj = COA
        renderObj {
            10 = IMG_RESOURCE
            10 {
                file {
                    import.data = file:current:uid
                    treatIdAsReference = 1

                    width = 1200
                    height = 630c
                }

                stdWrap {
                    typolink {
                        parameter.data = TSFE:lastImgResourceInfo|3
                        returnLast = url
                        forceAbsoluteUrl = 1
                    }
                }
            }
        }
    }
}

Btw. twitter:image works fine the same way - even without having to add it to addRootLineFields!

I think there might be a bug or something?! Did not figure out either in TypoScript nor PHP/Core stuff where it stucks.

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #87625: MetaTagApi gives an Error in the Frontend when "og:image" is a stdWrap Value in TypoScriptClosedRichard Haeser2019-02-02

Actions
Actions
Copy link
 #1

Updated by Gabriel Kaufmann / Typoworx NewMedia almost 4 years ago

Did some debugging. For some reason in MetaTagGenerator TSFE-<pSetup['meta.'] will not have og:image even if it is defined in typoscript like in the example above!

Actions
Copy link
 #2

Updated by Gabriel Kaufmann / Typoworx NewMedia almost 4 years ago

Also noticed TYPO3 throws exception trying to set og:image:url using Typoscript. But this sub-property is defined in \TYPO3\CMS\Seo\MetaTag\OpenGraphMetaTagManager to be allowed!

Actions
Copy link
 #3

Updated by Simon Schaufelberger over 2 years ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by Riccardo De Contardi 4 months ago

  • Related to Bug #87625: MetaTagApi gives an Error in the Frontend when "og:image" is a stdWrap Value in TypoScript added
Actions
Copy link
 #5

Updated by Riccardo De Contardi 4 months ago

  • Status changed from New to Closed

Sorry for this late reply. I tend to close this issue for the following reasons:

1. $GLOBALS['TYPO3_CONF_VARS']['FE']['addRootLineFields'] has been removed since version 13.2 - see https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Configuration/Typo3ConfVars/FE.html#confval-typo3-conf-vars-fe-addrootlinefields

2. The issues about setting og:image via TypoScript should have been solved - see the related issue #87625. I have been able to set a simple working TypoScript example like the one written on #87625:

page.meta {
og:image.stdWrap.cObject = TEXT
og:image.stdWrap.cObject {
    if.isFalse.field = og_image
    stdWrap.typolink {
        parameter.stdWrap.cObject = IMG_RESOURCE
        parameter.stdWrap.cObject.file = fileadmin/Images/some_image.png
        returnLast = url
        forceAbsoluteUrl = 1
    }
}
}

If you think that this is the wrong decision or there is still work to be done here, please reopen this issue or open a new issue with a reference to this one. Thank you.

Actions
Copy link

Also available in: Atom PDF