DAM folder not visible in assets UI

Avatar

Avatar
Boost 10
Level 2
jezwn
Level 2

Likes

11 likes

Total Posts

76 posts

Correct reply

2 solutions
Top badges earned
Boost 10
Give Back 5
Contributor
Shape 1
Springboard
View profile

Avatar
Boost 10
Level 2
jezwn
Level 2

Likes

11 likes

Total Posts

76 posts

Correct reply

2 solutions
Top badges earned
Boost 10
Give Back 5
Contributor
Shape 1
Springboard
View profile
jezwn
Level 2

23-06-2021

I've this folder in DAM, named xyz where I've the permissions to Read, Modify and Delete. When checking the assets UI this folder is not visible <domain>/assets.html/content/dam. If I hit the URL at <domain>/assets.html/content/dam/xyz I have the persmissions as above. I have checked with other folders as well inside DAM, some other folders are also having the same issue with these given permissions.

Replies

Avatar

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

233 likes

Total Posts

295 posts

Correct reply

67 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

233 likes

Total Posts

295 posts

Correct reply

67 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile
Shashi_Mulugu
MVP

24-06-2021

@jezwn What is the version of AEM are you using? Please check the permissions of parent folder as well, as child folders/nodes will be read relative to parent folder.

Avatar

Avatar
Boost 10
Level 2
jezwn
Level 2

Likes

11 likes

Total Posts

76 posts

Correct reply

2 solutions
Top badges earned
Boost 10
Give Back 5
Contributor
Shape 1
Springboard
View profile

Avatar
Boost 10
Level 2
jezwn
Level 2

Likes

11 likes

Total Posts

76 posts

Correct reply

2 solutions
Top badges earned
Boost 10
Give Back 5
Contributor
Shape 1
Springboard
View profile
jezwn
Level 2

24-06-2021

@Shashi_Mulugu  The AEM version we're using is 6.5.4. The parent folder does contain these three permissions. One thing I observed later is there's a cloud config(/conf/global) to these folders which are not visible and no permissions has been set for /conf/global, which I assume would be the cause. But there's one outstanding folder with this cloud config and is visible in the assets UI. The only difference I see in the node properties is that, this one contains a property called 'sourcing' which is set to false.

Avatar

Avatar
Boost 5
Level 7
Ritesh_M
Level 7

Likes

179 likes

Total Posts

142 posts

Correct reply

44 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Applaud 5
Affirm 1
View profile

Avatar
Boost 5
Level 7
Ritesh_M
Level 7

Likes

179 likes

Total Posts

142 posts

Correct reply

44 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Applaud 5
Affirm 1
View profile
Ritesh_M
Level 7

24-06-2021

@jezwn ,

 

It might be because one of the content node under DAM is corrupted. Please check if you have jcr:content node under DAM. Also, check if you are getting error in browser console/network tab or in error logs.

 

Avatar

Avatar
Boost 10
Level 2
jezwn
Level 2

Likes

11 likes

Total Posts

76 posts

Correct reply

2 solutions
Top badges earned
Boost 10
Give Back 5
Contributor
Shape 1
Springboard
View profile

Avatar
Boost 10
Level 2
jezwn
Level 2

Likes

11 likes

Total Posts

76 posts

Correct reply

2 solutions
Top badges earned
Boost 10
Give Back 5
Contributor
Shape 1
Springboard
View profile
jezwn
Level 2

24-06-2021

@Ritesh_M  The issue is only with certain users. One thing I observed later is there's a cloud config(/conf/global) to these folders which are not visible and no permissions has been set for /conf/global, which I assume would be the cause. But there's one outstanding folder with this cloud config and is visible in the assets UI. The only difference I see in the node properties is that, this one contains a property called 'sourcing' which is set to false.