Even after publishing the CAconfig changes, changes are not reflected in publisher domain. Changes are reflected in view as published mode.
this issue is not replicated in local instance, in local instance it is working fine in publisher. But in publisher domain the changes area not reflected.
what are the possible scenario creating this issue.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @ashwinka
1: Check the author replication Queue.
2: If you have access to publisher crx/de (or else, ask with Dev ops team), check the jcr node. Whehter CA config is present or not.
3: Try to hit the IP based URL of publisher. If its work here, then issue might be in dispatcher level.
Hi @ashwinka
1: Check the author replication Queue.
2: If you have access to publisher crx/de (or else, ask with Dev ops team), check the jcr node. Whehter CA config is present or not.
3: Try to hit the IP based URL of publisher. If its work here, then issue might be in dispatcher level.
What configuration do you change, which is not reflecting?
(If it's in custom code, your code could do the resolution of the caconfig values are startup time only; in that case runtime changes are not reflected.)
I recommend you to install the Context Aware Configuration Editor on your AEM environments, and so your content author's can create CaConfigs and publish configurations as expected, https://sourcedcode.com/blog/aem/how-to-embed-wcm-io-context-aware-configuration-editor
@ashwinka Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.
Views
Replies
Total Likes