AEM 6.5 | Content Import Issue | Community
Skip to main content
M
MukeshAEM
Level 3
July 11, 2023
Solved

AEM 6.5 | Content Import Issue

  • July 11, 2023
  • 4 replies
  • 1007 views

While porting pages from the higher environment to the lower environment, I discovered missing experience fragments and images. I realized that the created package does not contain these elements. I'm unsure if I overlooked something during the package creation process. Do I need to locate and include all the images and experience fragments used in pages manually in the package? 

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 Mahedi_Sabuj

Hi @mukeshaem,

You need to include experience fragment and asset path to the content package filter as well.
If your assets and experience fragments in a specific folder, you need to include those filter path like below:

my-project.content-package-20230711.zip
/content/my-project
/content/dam/my-project
/content/experience-fragments/my-project

4 replies

Mahedi_Sabuj
Community Advisor
Mahedi_SabujCommunity AdvisorAccepted solution
Community Advisor
July 11, 2023

Hi @mukeshaem,

You need to include experience fragment and asset path to the content package filter as well.
If your assets and experience fragments in a specific folder, you need to include those filter path like below:

my-project.content-package-20230711.zip
/content/my-project
/content/dam/my-project
/content/experience-fragments/my-project

Mahedi Sabuj
    EstebanBustamante
    Community Advisor and Adobe Champion
    EstebanBustamanteCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    July 11, 2023

    Hi @mukeshaem 

     

    YES, you need to add the paths (images and XF location) manually to the package's filters. Usually, you will have organized all the images under the same parent folder, for example: /content/dam/my-company-images, so the task is not as hard as you think. Just keep in mind that packaging images can produce a huge package, so depending on your content, you can keep a couple of separate packages, one for images and one for pages, or so. The same applies to XF, just a common parent path where all the XF lives into the same or a dedicated package.

     

    I Hope this helps.

    Esteban Bustamante
      Sudheer_Sundalam
      Community Advisor
      Sudheer_SundalamCommunity Advisor
      Community Advisor
      July 11, 2023

      @mukeshaem ,

       

      If you are using Cloud Manager or AEM as a CS, you can use Content Copy tool to move pages, XFs, DAM content from higher environments to lower environments.

      Consider taking a look at this option:

      AEM Cloud Manager: https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/content/using/content-copy.html?lang=en

       

      AEM as a CS: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developer-tools/content-copy.html?lang=en

        DPrakashRaj
        Community Advisor
        DPrakashRajCommunity Advisor
        Community Advisor
        July 11, 2023

        Filter in aem package manger has 1:1 mapping with its filter node. It will never automatically pulls the references via package manager. So you need to update the filter to include assets and experience fragments 

          Terms & ConditionsAccessibility statement

          Loading footer...