since ‎27-04-2018
‎23-09-2020
rajup64088879
Level 1
Re: Not able to select the image from page property Thumbnail Tab(AEM 6.4.5.0) rajup64088879 - Adobe Experience Manager
I have gone though some issue like same as menioned, i have found that if we install sp4 issue will resolve, i have installed latest 6.4 version service pack(6.4.8.0) but still issue is not resolved.Same kind of issue link:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-page-property-image-drag-drop-issues/m-p/288672#M17500
739
Views
0
Likes
0
Comments
Re: Not able to select the image from page property Thumbnail Tab(AEM 6.4.5.0) rajup64088879 - Adobe Experience Manager
Hi , No errors in both browser and error log
771
Views
0
Likes
0
Comments
Not able to select the image from page property Thumbnail Tab(AEM 6.4.5.0) rajup64088879 - Adobe Experience Manager
Not able to select the image as the thumbnail of the touch ui page, only we are able to upload the image as thumbnail.When we click on the 'Select image' in 'Thumbnail' tab of the page properties nothing happens, AEM version we are using is 6.4.5.0, is there any way page thumbnail selection can be selected from /content/dam path ?
795
Views
0
Likes
3
Answers and Comments
Re: How to disable the target option in context menu only... rajup64088879 - Adobe Experience Manager
added foundation/components/parsys/cq:childEditConfig editconfig node manually and set the cq:disableTargeting to true after that target option is not appearing.
329
Views
0
Likes
0
Answers
How to disable the target option in context menu only for classic ui globally (AEM 6.4) rajup64088879 - Adobe Experience Manager
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...
341
Views
0
Likes
1
Answers and Comments
Re: Custom multifield in page properties not working as expected in classic UI( AEM 6.4 version) rajup64088879 - Adobe Experience Manager
If we open the page properties, "page-path/jcr:content.1.json" request is going and its taking the node values with first level, the multicompositefield values are stored in inner levels, due to that those values are not getting populated in the dialog.we can overcome this behavior by changing the constant CQ.PAGE_PROPERTIES_MAX_RECURSION_LEVEL value,this constant value controls the maximum depth of the node subtree under the page /jcr:content node, this can be change by overlaying the constants...
533
Views
0
Likes
0
Answers
Can we overlay the file to our custom path rajup64088879 - Adobe Experience Manager
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.
354
Views
0
Likes
1
Answers and Comments
Re: AEM 6.2 to 6.5 Upgrade - dialogs missing value rajup64088879 - Adobe Experience Manager
The property CQ.PAGE_PROPERTIES_MAX_RECURSION_LEVEL controls the maximum depth of the node subtree under the page /jcr:content node, default value is 1, this can be overriden by overlaying the constants.js, which is present under path /libs/cq/ui/widgets/source/constants.js.
2606
Views
0
Likes
2
Replies
Custom multifield in page properties not working as expected in classic UI( AEM 6.4 version) rajup64088879 - Adobe Experience Manager
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.
638
Views
0
Likes
1
Answers and Comments