AEM Content pages getting deleted after maven build | Community
Skip to main content
akashkriz005
akashkriz005
Level 2
April 9, 2023
Solved

AEM Content pages getting deleted after maven build

  • April 9, 2023
  • 4 replies
  • 1509 views

Hello Team !

 

Recently I have created a project with Maven Archetype 40 and AEM version of 6.5.15. Development was going through and suddenly after build the content page structure got deleted after the build. This happens intermediately in each time. The filter.xml on the ui.content is given for merge and not given any delete exclusions. 

 



Is this an issue with Archetype version or any other ? Please advice if anyone have faced this issue recently ?

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 kdatta

check out for filter.xml under ui.content. and try to add following with mode "merge" .

<filter root="/content/yourproject" mode="merge"/>
<filter root="/content/experience-fragments/yourproject" mode="merge"/>

Thanks ,
kaushik



4 replies

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
April 9, 2023

This is normally caused by an incorrect filter.xml; please note that you have multiple content packages as part of your deployment, not only ui.apps; as content is removed, you should check the filter of the ui.content module.

    B_Sravan
    Community Advisor
    B_SravanCommunity Advisor
    Community Advisor
    April 9, 2023

    check your filter.xml to see if there are any root-level paths, which override your content pages.

    if you would like to maintain a separate content package, you can exclude the content path filter altogether.

    Thanks,
    Sravan

      Jagadeesh_Prakash
      Community Advisor
      Jagadeesh_PrakashCommunity Advisor
      Community Advisor
      April 10, 2023

      @akashkriz005  I recommand you to delete the /content/<content path> and /content/experience-fragment path from your filter.xml file and validate it. 

       

      As you said this is intermediately happening then it should not be a issue with Archetype. I tried Archetype 40 in my local and its absolutly fine 

        K
        kdattaAccepted solution
        Level 2
        April 10, 2023

        check out for filter.xml under ui.content. and try to add following with mode "merge" .

        <filter root="/content/yourproject" mode="merge"/>
        <filter root="/content/experience-fragments/yourproject" mode="merge"/>

        Thanks ,
        kaushik



          Terms & ConditionsAccessibility statement

          Loading footer...