CAconfig changes not reflected in publisher instance | Community
Skip to main content
ashwinka
New Participant
December 10, 2023
Solved

CAconfig changes not reflected in publisher instance

  • December 10, 2023
  • 5 replies
  • 1338 views

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.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Mahesh_Gunaje

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.

5 replies

kautuk_sahni
Employee
December 11, 2023

@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.

Kautuk Sahni
BrianKasingli
New Participant
December 11, 2023

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

 

arunpatidar
New Participant
December 10, 2023

Hi @ashwinka 
Please check the CDN/dispatcher cache as well? Could be a cache issue.

Arun Patidar
joerghoh
Employee
December 10, 2023

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.)

Mahesh_GunajeAccepted solution
New Participant
December 10, 2023

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.