Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

DAM ASSET editor default form overlay is not reflecting in AEM 6.2

Kkkrish
Level 5
Level 5

I am trying to overlay the DAM ASSET editor default form under apps, but it doesn't show up the overlay related changes when i test it under below url http://localhost:4502/mnt/overlay/dam/gui/content/assets/metadataeditor.html?item=%2Fconte nt%2Fdam%2Fprojects%2Foutdoors%2Fcover&_charset_=utf8.

am i missing any configurations.

~Kk

1 Accepted Solution
huzaifaha985211
Correct answer by
Level 2
Level 2

Kkkrish wrote...

huzaifaha98521146 wrote...

in AEM 6.2 the correct way to do what you're trying to do is through  "metadata schemas" Here is the doc.

https://docs.adobe.com/docs/en/aem/6-2/author/assets/managing-assets-touch-ui/brandportal/metadata-s...

This would allow you to change the default schemas as well as introduce new ones. Even if you tried to do an overlay of image, application etc it won't work. I do not have an answer on why in this particular instance it's not working for you but have an OOB solution that doesn't require any tinkering.

 

 

Thanks you for your concern, if i modify the default schema from the url directly it will affect the whole AEM instance, can't i use the OVERLAY concept for the DAM Asset editors like other components?

 

 

Finally found the article that explains this. You can't overlay this option. It has to be added manually or via package deployment if you desire

 

https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade/upgrading-custom-search-forms.html

 

In AEM 6.2, the location where Customized Search Forms are stored in the repository has changed. Upon upgrading, they are moved from their location in 6.1 at:

  • /apps/cq/gui/content/facets

to a new location under:

  • /conf/global/settings/cq/search/facets

Because of this, manual adjustments are required after an upgrade in order for the forms to continue to function.

This applies to new Search Forms as well as default Forms that have been customized.

LINK: https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade/upgrading-custom-search-forms.html

View solution in original post

7 Replies
kautuk_sahni
Community Manager
Community Manager

Hi 

Moving this thread to AEM "Asstes" topic so to have better contextual experts have a look at this.

~kautuk

kautuk_sahni
Community Manager
Community Manager

Hi 

Please have a look at this video, this talks about creating an overlay component.

Link:- https://youtu.be/axCKOu3YjmM [11:53]

Another good reference article :- http://blogs.adobe.com/experiencedelivers/experience-management/touch-ui-customizations-part-2/

// It also talks about many DAM overlay

~kautuk

Kkkrish
Level 5
Level 5

kautuksahni wrote...

Hi 

Please have a look at this video, this talks about creating an overlay component.

Link:- https://youtu.be/axCKOu3YjmM [11:53]

Another good reference article :- http://blogs.adobe.com/experiencedelivers/experience-management/touch-ui-customizations-part-2/

// It also talks about many DAM overlay

~kautuk

 

Thanks Kautuk,

but it doesn't provide me any clue why this overlay is not working for the default form for the Asset Editor.

~Kk

huzaifaha985211
Level 2
Level 2

in AEM 6.2 the correct way to do what you're trying to do is through  "metadata schemas" Here is the doc.

https://docs.adobe.com/docs/en/aem/6-2/author/assets/managing-assets-touch-ui/brandportal/metadata-s...

This would allow you to change the default schemas as well as introduce new ones. Even if you tried to do an overlay of image, application etc it won't work. I do not have an answer on why in this particular instance it's not working for you but have an OOB solution that doesn't require any tinkering.

Kkkrish
Level 5
Level 5

huzaifaha98521146 wrote...

in AEM 6.2 the correct way to do what you're trying to do is through  "metadata schemas" Here is the doc.

https://docs.adobe.com/docs/en/aem/6-2/author/assets/managing-assets-touch-ui/brandportal/metadata-s...

This would allow you to change the default schemas as well as introduce new ones. Even if you tried to do an overlay of image, application etc it won't work. I do not have an answer on why in this particular instance it's not working for you but have an OOB solution that doesn't require any tinkering.

 

 

Thanks you for your concern, if i modify the default schema from the url directly it will affect the whole AEM instance, can't i use the OVERLAY concept for the DAM Asset editors like other components?

huzaifaha985211
Level 2
Level 2

The answer to your first statement is Yes. If you want to create a different set of metadata schema for a business use case then you can do so by following the same link. Click on Create --> Create schema form. BTW these schemas in 6.2 are created and kept under /conf/global/settings/dam/adminui-extension/metadataschema........ Your overlay in this case will not work since the path is different in 6.2 vs 6.0 and 6.1. I made similar changes when I performed a recent migration from 6.1 to 6.2

huzaifaha985211
Correct answer by
Level 2
Level 2

Kkkrish wrote...

huzaifaha98521146 wrote...

in AEM 6.2 the correct way to do what you're trying to do is through  "metadata schemas" Here is the doc.

https://docs.adobe.com/docs/en/aem/6-2/author/assets/managing-assets-touch-ui/brandportal/metadata-s...

This would allow you to change the default schemas as well as introduce new ones. Even if you tried to do an overlay of image, application etc it won't work. I do not have an answer on why in this particular instance it's not working for you but have an OOB solution that doesn't require any tinkering.

 

 

Thanks you for your concern, if i modify the default schema from the url directly it will affect the whole AEM instance, can't i use the OVERLAY concept for the DAM Asset editors like other components?

 

 

Finally found the article that explains this. You can't overlay this option. It has to be added manually or via package deployment if you desire

 

https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade/upgrading-custom-search-forms.html

 

In AEM 6.2, the location where Customized Search Forms are stored in the repository has changed. Upon upgrading, they are moved from their location in 6.1 at:

  • /apps/cq/gui/content/facets

to a new location under:

  • /conf/global/settings/cq/search/facets

Because of this, manual adjustments are required after an upgrade in order for the forms to continue to function.

This applies to new Search Forms as well as default Forms that have been customized.

LINK: https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade/upgrading-custom-search-forms.html

View solution in original post