Check this similar threadhttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-0-download/qaq-p/191544 

here is one similar threadhttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/could-not-find-the-main-class-com-adobe-granite-quickstart-base/qaq-p/265493double check these points as well Step 1: Add the Remote Debugging JVM ParameterTo use remote debugging, you must start AEM ...

if the thumbnail image is coming from DAM ,then the page have "image" node in jcr:content of page and that image node will be having fileReference property which will have your image path of thumbnail. In this case you can make use of resource object and get the child node image and then get the pro...

I would say first you check the purpose of this CSS class why they have added in classic UI. And then to implement the same for Touch UI dialog.There could be a case where you might not need this in touch UI dialog or there could be a different way to serve the purpose.   

Add cq:allowedTemplate property in your root page and add path for both of your static and editable templates as given belowcq:allowedTemplates="[/conf/yourprojectname/settings/wcm/templates/.*,/apps/yourprojectname/templates/.*]"

See these threads they have mentioned the workaround https://blogs.perficient.com/2020/06/16/how-to-easily-access-crx-de-on-adobe-ams-after-aem-6-5-5-upgrade/https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-easily-access-crx-de-on-adobe-ams-after-aem-6-5-5-upgrade/td-...

This is one similar thread https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-could-not-find-model-for-workflow-dam-xmp-writeback/qaq-p/240182 Check the comments provided by Hemant . 

similar threadhttps://stackoverflow.com/questions/18864317/start-a-workflow-on-page-activation-without-activating-the-page-in-cq5

Use jquery or javascript functions(document.cookie) to get the cookie value.Add any class or id in div tag and with help of that identifier add the value in div tag[  $("#id").val()  ].

Try adding the fix at template level. This might solve the issue for most of the pages.