Have you checked this on your new instance. it seems you custom configs might be causing the issue. my local instance is on AEM 6.5.21 and it doesn't have the issue. Can you also try creating a new folder in your aem dam and try to upload the new valid assets and see how it responds? it might be pos...

you can always check the request.log from AEM publisher to see if the requested url are getting as query params to AEM publisher

Can you check if this happens on vanilla instance as well?  can you refer this as it has similar ask as yours https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/dam-image-renditions-error-while-executing-the-folder-thumbnail/m-p/387339   Try with Folder Preview Rendition Regex...

Please refer to this and do the customization as per your need. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-forms/aem-forms-metadata-schema-editor-create-a-custom-multifield-with/m-p/657870#:~:text=In%20the%20AEM%20forms%2C%20metadataschema,matter%20would%20be%20highly%...

you need to overlay /libs/dam/gui/coral/components/admin/schemaforms/formbuilder/v2/builditems.jsp in your apps folder and create a new custom field in the /apps folder to be included in the overlayed jsp

May be it’s happening because of browser local cache as it’s happening on author instance. try checking this in private/incognito to see if this resolves. You can also select the disable cache from browser settings 

Hi All. welcome to experience league.   thanks prakash

I do have couple of questions on this. is this feature will be available to all costumers on ams and AEMcaS wothout any additional license?sometimes its not possible to do much change on content strategy in large enterprise applications due to limitations from content team requirements and to meet a...

Please take a look on  https://blogs.perficient.com/2021/05/27/how-to-extend-content-fragment-model-data-types/  

Versioned client libs to work will still require to remove the page cache from the directory but not necessarily the clientlibs. As with versioned clientlibs will always have a new file name with the deployment but the page will still refrerence the old clientlibs as its cached so you need to delete...