reference pages showing empty from AEM assets while selecting any Asset and open references | Community
Skip to main content
R
raju-komari
Level 3
November 17, 2023

reference pages showing empty from AEM assets while selecting any Asset and open references

  • November 17, 2023
  • 4 replies
  • 2539 views

Hi All,

We are seeing reference pages showing empty from AEM assets while selecting any Asset and open references rail from left top.

 

This image used one of the test page and able to see image in page as well.

 

As per validation, we are seeing below servlet call is returning empty results instead of showing results.

https://localhost:4502/mnt/overlay/dam/gui/content/assets/jcr:content/rails/references/items/references.provider.html?item=%2Fcontent%2Fdam%2Fweb%2Femailtemplate%2Fheader-o-nepl.png&_=1700228984004

 

It could be great if some one share comments /suggestion's on this.

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

4 replies

aanchal-sikka
Community Advisor
aanchal-sikkaCommunity Advisor
Community Advisor
November 18, 2023

@raju-komari 

 

Requesting you to please check error.log, if you are noticing any errors or traversal queries, on accessing the references.

Aanchal Sikka
    R
    raju-komariAuthor
    Level 3
    November 18, 2023

    Hi Sikka

    Thanks for the update, unfortunately there is no errors related to this call from error log.

      Shashi_Mulugu
      Community Advisor
      Shashi_MuluguCommunity Advisor
      Community Advisor
      November 19, 2023

      @raju-komari I strongly feel you should see something in error logs, also can you post page screenshot on how image is used in page..

        R
        raju-komariAuthor
        Level 3
        November 20, 2023

        Hi Shashi,

        Please find the screenshot below for JCR node structure and for this image ( this is the existing site ) references are showing, but when ever adding /replacing newly uploaded image into same place, not showing references.

        Same issue for newly created pages with new images - not showing references and also logs not helping much to proceed further.

         

        Existing site - Image showing references

         

        After replacing with new image for above image

        Logs also attached here

        2023-11-20 18:00:00.343 INFO [com.abc.aem.filters.ValidateLicenseFilter] path information/mnt/overlay/dam/gui/content/assets/jcr:content/rails/references/items/references.html/content/dam/web/aaa/bbbbb/cccc/ddd/images/redesigned/header-o-nepl.png
        2023-11-20 18:00:00.369 WARN [javax.mail] expected resource not found: /META-INF/javamail.default.address.map
        2023-11-20 18:00:00.390 ERROR [org.apache.sling.servlets.get.impl.DefaultGetServlet] No renderer for extension html, cannot render resource MergedResource [path=/mnt/overlay/dam/gui/content/assets/jcr:content/rails/references/items/references/items/list/items/copies/items/assetLanguageCopies/items/update/items/trigger/granite:rendercondition, resources=[/libs/dam/gui/content/assets/jcr:content/rails/references/items/references/items/list/items/copies/items/assetLanguageCopies/items/update/items/trigger/granite:rendercondition]]
        2023-11-20 18:00:00.415 WARN [javax.mail] expected resource not found: /META-INF/javamail.default.address.map

         

          TarunKumar
          Community Advisor
          TarunKumarCommunity Advisor
          Community Advisor
          November 20, 2023

          Hi @raju-komari ,

          Can you see in browser console and check if you are getting error related to JS. Also let us know if you have customized any feature around it? A others suggested please do check the error log as well.


          Thanks
          Tarun


            R
            raju-komariAuthor
            Level 3
            November 20, 2023

            Hi Tarun,

            We are not seeing any JS error while selecting references where not showing references for newly added images , but existing ones showing references.

            Attaching logs for opening image folder and selecting the image to show references.

             

            2023-11-20 18:00:00.343 INFO [com.abc.aem.filters.ValidateLicenseFilter] path information/mnt/overlay/dam/gui/content/assets/jcr:content/rails/references/items/references.html/content/dam/web/aaa/bbbbb/cccc/ddd/images/redesigned/header-o-nepl.png
            2023-11-20 18:00:00.369 WARN [javax.mail] expected resource not found: /META-INF/javamail.default.address.map
            2023-11-20 18:00:00.390 ERROR [org.apache.sling.servlets.get.impl.DefaultGetServlet] No renderer for extension html, cannot render resource MergedResource [path=/mnt/overlay/dam/gui/content/assets/jcr:content/rails/references/items/references/items/list/items/copies/items/assetLanguageCopies/items/update/items/trigger/granite:rendercondition, resources=[/libs/dam/gui/content/assets/jcr:content/rails/references/items/references/items/list/items/copies/items/assetLanguageCopies/items/update/items/trigger/granite:rendercondition]]
            2023-11-20 18:00:00.415 WARN [javax.mail] expected resource not found: /META-INF/javamail.default.address.map

             

              kautuk_sahni
              Community Manager
              kautuk_sahniCommunity Manager
              Community Manager
              November 20, 2023

              @raju-komari 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
              R
              raju-komariAuthor
              Level 3
              November 20, 2023

              Hi Sahni,

              As i have mentioned in above reply, we are seeing issues with newly added images and also seeing issues with newly created pages where we are using existing images/new images .

              I have shared logs and jcr node content structure as well, but there is no difference while updating new image into existing image.

               

              I will ensure to share solution steps here once it is fixed, but it is not fixed yet and still analysis going on with different templates /pages/ new images etc ..

               

              We are unable to proceed much due to this weird issue.

                kautuk_sahni
                Community Manager
                kautuk_sahniCommunity Manager
                Community Manager
                November 23, 2023

                The potential factors contributing to this issue could be:

                1. Rendering Issues: The error log indicates an absence of a renderer for the "html" extension, potentially hindering the references page's rendering.

                2. Missing Resource: The log mentions an inaccessible resource, "/libs/dam/gui/content/assets/jcr:content/rails/references/items/references/items/list/items/copies/items/assetLanguageCopies/items/update/items/trigger/granite:rendercondition." This resource might be crucial for the references page to function correctly.

                3. Data Retrieval Issues: The error log suggests that the servlet call is returning empty results, implying that references are not being properly retrieved from the repository.

                Troubleshooting Steps:

                1. JavaScript Error Check: Verify that no JavaScript errors are occurring on the page where the references should appear. JavaScript errors can sometimes disrupt page rendering.

                2. Resource Availability Verification: Ensure that the resource "/libs/dam/gui/content/assets/jcr:content/rails/references/items/references/items/list/items/copies/items/assetLanguageCopies/items/update/items/trigger/granite:rendercondition" exists and is accessible. If the resource is missing, it might need to be restored or reinstalled.

                3. Server Log Examination: Review the server logs for any additional errors or warnings related to the issue. The logs might provide further insights into the underlying cause.

                4. Template and Page Testing: Replicate the issue with different templates and pages to determine if it is specific to a particular configuration. This could help narrow down the problem's scope.

                5. Analyze the JCR node structure and compare it with the expected structure to identify any discrepancies.
                Kautuk Sahni
                Terms & ConditionsAccessibility statement

                Loading footer...