Outdated Content fragment while publishing the page | Community
Skip to main content
February 13, 2024

Outdated Content fragment while publishing the page

  • February 13, 2024
  • 3 replies
  • 2925 views

Hello All,

 

I'm fetching the fields of content fragment at the component level, after authoring the content fragment path in authoring dialog and whenever I'm publishing the page, Its always showing as content fragment model as outdated. Even though content fragment is published already and doesn't have any new changes. 

Any help here would be appreciated.

 

Thanks in Advance!

 

3 replies

arunpatidar
Community Advisor
Community Advisor
February 13, 2024

Hi @priyak-1 
Is it the model or the content fragment itself shown as outdated?

Arun Patidar
priyak-1Author
February 13, 2024

@arunpatidar Content fragment model itself is showing as outdated.

arunpatidar
Community Advisor
Community Advisor
February 13, 2024

could you please check the replication date of content fragment model?

Arun Patidar
Jagadeesh_Prakash
Community Advisor
Community Advisor
February 13, 2024

@priyak-1  any thing in logs that you see while you publish the content fragment or on the page load ? 

priyak-1Author
February 13, 2024

@jagadeesh_prakash I don't see any logs as well related to this.

Jagadeesh_Prakash
Community Advisor
Community Advisor
February 13, 2024

@priyak-1  Are you creating the content fragments at right place ?

 

You should have created your Model under a project folder (by default creating a Model at the root folder is disabled). You have to be in a folder with the same name in Assets in order to use your Models. Here is an example of what I mean (using We.Retail): Refer to below URL which might help you 

 

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/published-content-fragment-model-not-available-while-creating/m-p/323420

 

kautuk_sahni
Community Manager
Community Manager
February 28, 2024

@priyak-1 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
Sachin_Arora_
Community Advisor
Community Advisor
March 11, 2025

@priyak-1 @kautuk_sahni I faced same issue while replicating Content Fragment. In my case, issue was happening due to missing property cq:lastModified on jcr:content of the Content Fragment Model. We generally dont push these properties in code and due to which AEM probably not able to figure out that model is modified post activation.

Adding cq:lastModified property solved the issue.