Level 1
Level 2
Melden Sie sich an, um alle Badges zu sehen
When I try to create a content fragment in DAM and click the “Create” button, the options to create a content fragment do not appear. I can create CF models, and the configuration is set up correctly in the CF DAM folder.
Note: I am using admin user.
Version : AEM 6.5.20
Logged user: Admin
Gelöst! Gehe zu Lösung.
Anhand von Themen werden Community-Inhalte kategorisiert und Sie können so relevanten Inhalt besser finden.
Zugriffe
Antworten
Likes gesamt
Thanks Everyone for the reply. I got resolved this issue. Its because of the resource got hidden through the resource merger overlay (Because of some security issue checks). have enabled it to true and now its working fine.
Zugriffe
Antworten
Likes gesamt
On the parent folder you are attempting to create CF, goto Properties, Policies tab and add models you created.
Zugriffe
Antworten
Likes gesamt
@sarav_prakash Models are already added to the policies tab of parent folder page properties. But still not able to get the create options
Zugriffe
Antworten
Likes gesamt
ok. Your screenshot doesnt show Create Folder, Metadata options, suggesting this is not Content Fragment issue.
This specific folder seems to have issues. Sometimes bad oak:index might prevent ootb dam features https://experienceleaguecommunities.adobe.com/t5/adobe-experience-Cmanager/existing-folders-new-fold...
Please share server logs when opening this folder.
Your screenshot shows UGC, configured for Livefyre. Try adding cfm policy to different folder outside Livefyre configuration. Maybe Livefyre is interrupting with normal dam functions.
Zugriffe
Antworten
Likes gesamt
Hi @Nishanth_KR
If updated policies to the DAM folder still not able to see the create content fragment option, please try below -
1. Check if the content fragment model is enabled like below
2. Check the necessary folder permissions for below path -
/conf/global/settings/dam/cfm/models/<model_name>
Hope this helps
Zugriffe
Antworten
Likes gesamt
Thanks Everyone for the reply. I got resolved this issue. Its because of the resource got hidden through the resource merger overlay (Because of some security issue checks). have enabled it to true and now its working fine.
Zugriffe
Antworten
Likes gesamt
Zugriffe
Likes
Antworten
Zugriffe
Likes
Antworten