AEM Re-publishing already published Fragment Model | Community
Skip to main content
A
ashish_mishra1
New Participant
May 9, 2023
Solved

AEM Re-publishing already published Fragment Model

  • May 9, 2023
  • 1 reply
  • 671 views

I am facing an issue w.r.t giving access to our authors. I have given them replicate access for /content/dam path, but when they are creating a content fragment using the fragment model and trying to replicate it. 

AEM is trying to re-publish the fragment model too, even though they are already activated. Because of this replication action is failing with 403 as /conf/ replicate access is not given to authors.

 

Any idea, why AEM is trying to activate the fragment model again?

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 ShubhanshuSi2

@ashish_mishra1 
When you create a content fragment using a fragment model, it creates a reference to the model in the content fragment metadata. When you publish CF, AEM needs to ensure that CF Model (CFM) is also available on publish instance.


If the model is not available on publisher or is not activated, then AEM will try to replicate the model along with the content fragment, which is resulting in the 403 error because the authors don't have replicate access to /conf path.

You may try either of the below options.

  1. Give replicate access to the /conf path to the authors. This should allow author to replicate CFM along with the content fragment. (This is not an option in your case)
  2. Make sure that the CFM is activated (“cq:lastReplicationAction” = Activate) using a user having higher permissions or as an admin. This way, AEM will not try to replicate the model again when the content fragment is replicated.

 

Check-in replication logs if CFM itself has some references to resources outside of /content/dam

1 reply

S
ShubhanshuSi2Accepted solution
New Participant
May 9, 2023

@ashish_mishra1 
When you create a content fragment using a fragment model, it creates a reference to the model in the content fragment metadata. When you publish CF, AEM needs to ensure that CF Model (CFM) is also available on publish instance.


If the model is not available on publisher or is not activated, then AEM will try to replicate the model along with the content fragment, which is resulting in the 403 error because the authors don't have replicate access to /conf path.

You may try either of the below options.

  1. Give replicate access to the /conf path to the authors. This should allow author to replicate CFM along with the content fragment. (This is not an option in your case)
  2. Make sure that the CFM is activated (“cq:lastReplicationAction” = Activate) using a user having higher permissions or as an admin. This way, AEM will not try to replicate the model again when the content fragment is replicated.

 

Check-in replication logs if CFM itself has some references to resources outside of /content/dam

    Terms & ConditionsAccessibility statement

    Loading footer...