Has anyone else experienced an issue were some of their Asset Folders do not show any media (when navigating through Touch UI)?
CRXde confirms that media exists in these folders.
Folders were not created with any out of norm special characters (ie: Landing-Pages)
There is between 100 & 200 pieces of media (images, pdfs) including a few subfolders within these directories.... however, its well under the recommended limit (i've seen both 500 & 1000 as being the limit)
Any ideas?
I am not seeing anything in the error.log when attempting to navigate to these specific Asset folders... and again, other asset folders do show media.
Is it possibly a timeout due to the fact that there are a larger amount of media (as compared to the other folders) loaded into these folders with issue?
If so, what is the limit?
Solved! Go to Solution.
Views
Replies
Total Likes
Try a query like (1) and adjust the path which doesn't load. This might give you the nodes which are missing jcr:content nodes under 'test' folder
(1) :
/jcr:root/content/dam/test//element(*, dam:Asset)[not(jcr:content/@jcr:primaryType = 'dam:AssetContent' )]
Views
Replies
Total Likes
How about classic ui? Can you see such folder/files in classic ui ?
Can you switch touch ui views (column, card , list) and see if the folder/files appear? If they do, repeat the exercise and see if you get any exception in browser console or error.log
Usually this happens when the node structure has a missing jcr:content node and becomes inconsistent to display in touch ui
Views
Replies
Total Likes
So these folders do not work in any of the touch ui views.
However, I was able to view the assets from the classic ui. (granted, this does not help my authors - as they do not use the classic ui)
So besides manually going through each node within this folder in crxde - is there another way where I can determine if there is a missing jcr:content node? Would it be just that one is missing - or containing incorrect metadata?
Views
Replies
Total Likes
Try a query like (1) and adjust the path which doesn't load. This might give you the nodes which are missing jcr:content nodes under 'test' folder
(1) :
/jcr:root/content/dam/test//element(*, dam:Asset)[not(jcr:content/@jcr:primaryType = 'dam:AssetContent' )]
Views
Replies
Total Likes
Ran the query above (manipulated with new path) - but did not get results.
I went ahead and entered a support ticket.
Thank you for your assistance.
Views
Replies
Total Likes
Views
Like
Replies
Views
Likes
Replies
Views
Likes
Replies