Assets not accessible through browse option | Community
Skip to main content
V
Vani1012
Level 6
January 23, 2023

Assets not accessible through browse option

  • January 23, 2023
  • 1 reply
  • 2264 views

Hi,

when image is added directly to a page through browse option from a computer, it's not rendered on a page. It works if the image is added from the DAM.

Can anyone help me.

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

1 reply

D
Adobe Employee
digarg17Adobe Employee
Adobe Employee
January 23, 2023

Is it a custom component that you are using to render image or core component? When you use image from Dam - its reference is stored in the property called fileReference but if you browse and drop image from local system - it creates a file node with binary.  

If custom component , you can refer teaser/image component to ensure correct rendering.

    V
    Vani1012Author
    Level 6
    January 23, 2023

    I have a custom component 'image' it just has cq:editConfig node and no other implementation and its resource super type is core/wcm/components/image/v3/image

     

      V
      Vani1012Author
      Level 6
      January 23, 2023

      Is it happening on a specific env ? Install wknd reference package and check if you can reproduce the issue on wknd.

      https://github.com/adobe/aem-guides-wknd/releases

      I am unable to reproduce the issue on my local cloud with image v3 core component on wknd reference site.

       

      Are you able to upload the image from local system and see file node added in crxde ? is the issue only in rendering ? can you do view source and verify it's not the css issue.


      I also not able to reproduce the issue on local,

      its on test, stage environments.

      Q:Are you able to upload the image from local system and see file node added in crxde

      A:Yes am able to upload the image from local system and  file node added in crxde,. its not rendering on page

      How to check css issue with page source I dint get you.

        

        Terms & ConditionsAccessibility statement

        Loading footer...