[quote]Well, you have access to the whole page content in the template rendering the HTML header, so I think that should give you all you need to render the OG tags.[/quote]
Yes, I can find out, that there is [i]my-module:components/productDetail[/i] component somewhere in the main area of my page, but the actual product is not defined there - it is loaded from elsewhere (e.g. from some REST service) according to the productID from the request. As far as I understand the rendering order in Magnolia, the (area and) component models are created and executed only during the rendering phase of the page template. I.e. 1. PageModel is created 2. PageModel execute() 3. Page template rendering 3.1 page template hits [@cms.area name="htmlHeader"/] 3.1.1 area model is created 3.1.2 area model execute() is called 3.1.3 area template is rendered 3.2 page template rendering continues ... 3.x template rendering hits @cms.content tag of my (e.g. Product) component 3.x.1 component Model is created 3.x.2 component Model execute() is called 3.x.3 component template is rendered 3.x+1 page template rendering continues ... This means that in the moment of rendering the htmHeader area (3.1.3), I have no idea which product is going to be loaded in step 3.x.2 (remember, it is not defined in JCR, but loaded from a REST service), and what's its title and picture URL. Or do I understand the rendering steps wrong? Jozef. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=0999d41a-22d6-4d62-806c-0b5aaf28a627 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
