I assume you have two publish instances running.Then make 1 publish down and upgrade or do what ever you want to do with that mean time second instance will be up.
then dont add it in page properties rather do it like this- <meta property="og:title" content="${construct it through page title as per your need}"/>What i meant by this is-<meta property="og:title" content="${properties.pageTitle ? properties.pageTitle : properties.jcr:title }"/> In this way you do...
Add a field in page properties for og tag-And in your page component head.html include meta tag like this-<meta property="og:title" content="${properties.ogtag}"/>
I am facing the same issue with archtype 23 anyone is facing the same issue, it works fine in my local environment but the same doesn't work client network, so how to debug it or any specific network change we need to do?
Did you try to override page properties dialog in your page template, if yes then then isseu is in ur page properties dialog please check that.You can compare your custom page component with we retail or wknd you will be able to identify the issue.
Hi Team, We are integrating AEM with Service Now.We have few queries before we start implementing the same- 1. Is it fine to go ahead and develop the components using sightly and sling models.2. Or we should be using SPA framework.3. What will be the benefits if we use SPA with react or just traditi...