Globally I want to disable the context menu target option in only classic UI, instead of each component level adding the cq:disableTargeting to true, i have checked previous solution of overlaying the parsys component(https://experienceleaguecommunities.adobe.com/t5/Adobe-Experience-Manager/How-to-Disable-Targeting/qaq-p/184183), but when i am checking the parsys component at libs/foundation/components/parsys component it is already having cq:disableTargeting to true for the following nodes./lib...

Can we overlay the file to our custom path or we have to overlay the file to exact folder structure location as in libs, for example i want to overlay the constants.js(/libs/cq/ui/widgets/source/constants.js) file, in this adobe recommended Copy this file to /apps/cq/ui/widgets/source/constants.js for overlaying, but in my project that folder structure is not there, so i have copied to the custom path in apps folder and tested the changes and overlaying is working fine.

We are using custom multi field(multicompositefield) in page properties which saving the values as child node, able to add the values in dialog and those are saving fine, but when we open the dialog, the values are not getting populated in the dialog. The dialog is working fine when it is added as component dialog, issue happening when only the dialog is part of page properties, please suggest how to resolve this issue in classic UI.