images in content fragment don't show in content fragment component after installing site

[mpalme1]

I'm fairly new to AEM development.

I'm trying to find the cause of an issue, and I don't really know where to look. If I do the following, the functionality works as expected:

1. install AEM (6.5) on my development machine

2. create a content fragment model that includes a mulit-line field

3. use that cf model to create a cf in /content/dam/we-retail/en/people/mens, adding text and image to the multi-line field.

4. create a page under /content/we-retail/us/en/men using content page template

5. add a content fragment component to the new page and link it to the cf created in step 2 and 3, select single text element, and choose the content in the multi-line field.

The text and image from the content fragment appear on the page.

After I "mvn clean install -PautoInstallPackage" a project my team is working on, if I repeat the same steps, the text from the content fragment will show up on the page, but not the image. Given those results, I believe something in our project must be causing this problem, but I don't know where to look to find that cause. I'm looking through the error.txt file in \crx-quickstart\logs and see messages that appear to be about my content fragment and/or page like:

05.06.2020 13:06:33.075 *WARN* [0:0:0:0:0:0:0:1 [1591380392844] GET /content/we-retail/us/en/men/after-install.html HTTP/1.1] com.day.cq.wcm.msm.impl.LiveRelationshipManagerImpl StarResource given at /content/we-retail/us/en/men/after-install/jcr:content/root/responsivegrid/contentfragment/par0/*: no parent: no LiveCopy

(am reading here that those aren't anything to worry about: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/no-parent-no-livecopy-erro...)

05.06.2020 13:06:37.981 *ERROR* [sling-threadpool-8c53abc7-81f0-4e9e-bcc6-bbc8770b56eb-(apache-sling-job-thread-pool)-33-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish >> Handle: /content/dam/we-retail/en/people/mens/test-wr-store-info-cf

05.06.2020 13:09:41.146 *ERROR* [sling-threadpool-8c53abc7-81f0-4e9e-bcc6-bbc8770b56eb-(apache-sling-job-thread-pool)-4-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish Replication (DELETE) of /content/dam/we-retail/en/people/mens/test-wr-store-info-cf not successful: java.net.ConnectException: Connection refused: connect Conversation follows

By comparison, if I look at the logs after performing these actions on a clean AEM instance (before the mvn install), I don't find these errors. 

Does anyone have any recommendations for how to further investigate this issue?

Thanks,

Marvin

[Shashi_Mulugu]

Seems to be some vault filter issue. Are you able to see image in DAM as well in CF directly? If not I believe after men clean install, images might be getting deleted..

[mpalme1]

Thanks for responding. These are my filter.xml files:

<?xml version="1.0" encoding="UTF-8"?>
<workspaceFilter version="1.0">
<filter root="/conf/pineapple/settings/dam"/>
<filter root="/conf/pineapple/settings/wcm"/>
<filter root="/conf/pineapple/settings/workflow"/>
<filter root="/conf/global/settings/workflow/launcher/config/pineapple-launcher"/>
<filter root="/var/workflow/models/conf/pineapple/settings/workflow/models/pineapple_page_verification"/>
<filter root="/content/dam/pineapple/us/en/fruitjuice"/>
</workspaceFilter>

In ui.apps, it looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<workspaceFilter version="1.0">
<filter root="/apps/pineapple"/>
</workspaceFilter>

The content fragment model, content fragment, and page were all under we-retail. The image was at /content/dam/we-retail-screens/we-retail-instore-logo.png and I can see it in both the DAM and in CRXDE at that path.

[khamat_bn · Accepted solution]

Hi @mpalme1 ,

There might be issue with synchronisation, Please verify that the images in your project (/content/dam/<project>) will also be present in the backend (ui.apps/.../jcr_root/dam/<project>). There is a high possibility that Assets are not present in ui.apps and it's going to delete the assets in AEM when you fire -PautoInstallPackage.

If you are using vault then please check the filter files as well 

References -

https://helpx.adobe.com/in/experience-manager/6-3/sites/developing/using/ht-vlttool.html 

Happy Coding

~BK

[mpalme1]

I think I may have left out an important detail. The project I used to mvn clean install -PautoInstallPackage was called , let's say, "pineapple". However, i'm not building my content fragment models, content fragments, pages, etc in that "pineapple" project. I'm building them in we-retail and used this image "/content/dam/we-retail-screens/we-retail-instore-logo.png" in the content fragment multi line field. I don't think my "pineapple" project that I installed has any references in it to we-retail assets, pages, etc. I did this test because our AEM servers will have multiple projects/sites, and I'm concerned that something in this "pineapple" project is breaking AEM functionality for all the projects/sites that will be on the server/instance. So, to be clear, I only did the mvn clean install of "pineapple" once. But after I did, all subsequent attempts to perform the 5 listed steps in we-retail (or any other project on the site) resulted in a page showing the text of the content fragment but not the image.

[mpalme1]

Also, we are using our filter.xml files. In ui.content, the filter.xml looks like this: 

<?xml version="1.0" encoding="UTF-8"?>
<workspaceFilter version="1.0">
<filter root="/conf/pineapple/settings/dam"/>
<filter root="/conf/pineapple/settings/wcm"/>
<filter root="/conf/pineapple/settings/workflow"/>
<filter root="/conf/global/settings/workflow/launcher/config/pineapple-launcher"/>
<filter root="/var/workflow/models/conf/pineapple/settings/workflow/models/pineapple_page_verification"/>
<filter root="/content/dam/pineapple/us/en/fruitjuice"/>
</workspaceFilter>

In ui.apps, it looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<workspaceFilter version="1.0">
<filter root="/apps/pineapple"/>
</workspaceFilter>

[mpalme1]

(duplicate, tried to delete but couldn't)

[manising]

@mpalme1 The way your image is stored in a page is by storing its reference. So, you first go to crx/de and investigate content/we-retail/us/en/men/after-install/jcr:content/root/responsivegrid/contentfragment. Do you see the image reference?

If you see the image reference, then check for the image. Is it available at its location?

[mpalme1]

Thanks for the response. In this case, I used /content/dam/we-retail-screens/we-retail-instore-logo.png. In crxde, at /content/we-retail/us/en/men/test/jcr:content/root/responsivegrid/contentfragment/par1/we-retail-instore-logo-1591393385495, I do see a "fileReference" with value "/content/dam/we-retail-screens/we-retail-instore-logo.png" and I also see that image at that path in crxde.