You need to point your header to 1 location, then all the pages see the same changes.
WHat version of AEM are you using?
IN AEM 6.3/6.4 - you should not be using IParsys or static templates anymore. You should be using editbale templates and defining a header on the editable template. Creating a header using JSON is not best practice.
ie - here is a header defined in an Editable Template. In 6.3/6.4 - this is best practice.
Thanks for your reply. I am using version 6.3. However I cannot include my header in template structure as I have multiple microsites around 70+, each for different locales and I will be using same editable template across all the microsites. So, I want different header configurations for each language site. Therefore, I need to use iParsys to have different header configuration for each language site.
Thanks for your reply. What do you exactly mean by having to point header to one location? Header is a component which we have dropped in iparsys so that it can be inherited by child pages.
Have you followed MSM that AEM supports?
Each site should have its own header right?
We are trying to configure header for each micro site and links in header are auto generated from the child page properties.
When we change a child page property and activate that page header change is not reflected for other pages.
Also each site has its own header and that is in iparsys. The reason being we cannot create editable template for each microsite else we will end up creating 70+ templates.
MSM would have solved our problem but we want different configurations for each language site therefore we cannot put it in template.