since ‎26-09-2019
‎30-07-2020
Anderson_Hamer
Level 2
Re: cq:allowedTemplates is not working with experience fragment in AEM 6.4.8 Anderson_Hamer - Adobe Experience Manager
Thanks for your reply. allowedPath is not working at /content/experience-fragments level but it worked when I change regulr expression at the static tempalte level. making this change at 20+ template may not be a correct approach. Why cq:allowedTemplates & allowedPath props are not working at ef level? Is this a bug?
54
Views
0
Likes
0
Replies
cq:allowedTemplates is not working with experience fragment in AEM 6.4.8 Anderson_Hamer - Adobe Experience Manager
I see all my static templates while creating experience fragment. Checked the property cq:allowedTemplates on /content/experience-fragments, it contains /libs/cq/experience-fragments/components/experiencefragment/template/libs/settings/screens/experience-fragments/templates/experience-fragment-template-screens/conf/we-retail-screens/settings/wcm/templates/experience-fragment-screens-variation/conf/we-retail/settings/wcm/templates/experience-fragment(.*)? Only conf and libs templates should be sh...
70
Views
0
Likes
3
Replies
Re: Vanity url is not working with dispatcher in AEM 6.4 Anderson_Hamer - Adobe Experience Manager
Yes, it resolved. Rewrite rules were causing the issue.
36
Views
0
Likes
0
Replies
Re: Unable to add component on segment and experience fra... Anderson_Hamer - Adobe Experience Manager
Yes, Aem gives only warning on this page. There is no error. Are you sure it is working with sp8?
87
Views
0
Likes
0
Comments
Re: Unable to add component on segment and experience fra... Anderson_Hamer - Adobe Experience Manager
I have already mentioned error logs above. Error logs - 25.06.2020 18:07:21.218 *WARN* [0:0:0:0:0:0:0:1 [1593088641140] GET /editor.html/conf/we-retail/settings/wcm/segments/test123.html HTTP/1.1] org.apache.sling.caconfig.resource.impl.def.DefaultConfigurationResourceResolvingStrategy Ignoring reference to /conf/we-retail/settings from /conf/we-retail/settings - Probably misconfigured as it ends with '/settings'
111
Views
0
Likes
0
Comments
Re: Unable to add component on segment and experience fra... Anderson_Hamer - Adobe Experience Manager
Yes, I restarted my AEM instance after installtion of service pack 8, tried restarting my entire machine. Note I tried to setup 3 AEM instances and all ended up the same problem
180
Views
0
Likes
0
Comments
Unable to add component on segment and experience fragment - AEM 6.4 with service pack 8 Anderson_Hamer - Adobe Experience Manager
We can not add any component on segment page, the parsys does not have + button to add component and drag and drop is also not working. Tried to create a segment with new configuration and also with we.retail config, facing the same problem on both.Note - we have not overlay any component, it is just plain Vennila Instance + SP 8Segmentation page screen shotEven experience fragment also have the same problem, no + plus button and drag and drop is also not working.Experience fragment page screen ...
265
Views
0
Likes
6
Answers and Comments
Re: AEM 6.4 - Editable Template not allowing to add new component Anderson_Hamer - Adobe Experience Manager
I am facing this problem on segment and experince grament page . Can you pls tell me in detail to resolve this issue.
142
Views
0
Likes
0
Comments
Re: Vanity url is not working with dispatcher in AEM 6.4 Anderson_Hamer - Adobe Experience Manager
Updated the dispatcher logs in description section
10806
Views
1
Like
0
Replies
Re: Vanity url is not working with dispatcher in AEM 6.4 Anderson_Hamer - Adobe Experience Manager
Dispatcher logs- [root@disp-server-1:/path/path]# tail -f *.log | grep vanityUrls [Fri May 15 10:21:27 2020] [D] checking [/libs/granite/dispatcher/content/vanityUrls.html] [Fri May 15 10:21:27 2020] [D] cache-action for [/libs/granite/dispatcher/content/vanityUrls.html]: NONE [Fri May 15 10:21:27 2020] [I] "GET /libs/granite/dispatcher/content/vanityUrls.html?Ad3=3" 200 none [farm/rend01] 40ms 10.56.0.58 - - [15/May/2020:10:21:27 +0000] "GET /libs/granite/dispatcher/content/vanityUrls.html?Ad3=...
10737
Views
1
Like
0
Replies
Re: Vanity url is not working with dispatcher in AEM 6.4 Anderson_Hamer - Adobe Experience Manager
Downloaded the package from package share - https://www.adobeaemcloud.com/content/marketplace/marketplaceProxy.html?packagePath=/content/companies/public/adobe/packages/cq600/component/vanityurls-components Package version - vanityurls-components-1.0.2 Is there any higher versions available?
10748
Views
1
Like
0
Replies
Re: Vanity url is not working with dispatcher in AEM 6.4 Anderson_Hamer - Adobe Experience Manager
Hi Noksc - No, the dispatcher is not blocking this path. vanityUrls service is accessible even from dispatcher URL – https:/{disaptherDomain}/libs/granite/dispatcher/content/vanityUrls.html. I could also the Dispatcher is making call to AEM publisher, the response to this request is 200 as well. Allowing this path - /0100 { /type "allow" /url "/libs/granite/dispatcher/content/vanityUrls.html" } Not caching this path - /0001 { /type "deny" /glob "/libs/granite/dispatcher/content/vanityUrls.html" ...
10817
Views
1
Like
2
Replies
Vanity url is not working with dispatcher in AEM 6.4 Anderson_Hamer - Adobe Experience Manager
I am trying to setup vanity url in AEM 6.4. Followed and verified the below stepsInstalled the VanityURLS-ComponentsAllowed ‘Read’ permission to /libs/granite/dispatcher/content/vanityUrls for the ‘everyone’ group on the publish serversAdded a filter rule in the dispatcher to allow the vanity URL/0100 { /type "allow" /url "/libs/granite/dispatcher/content/vanityUrls.html" }Added a caching rule to prevent caching of this URL/0001 { /type "deny" /glob "/libs/granite/dispatcher/content/vanityUrls.h...
11495
Views
0
Likes
8
Replies
Re: How to specify nested “not” operation in specific gro... Anderson_Hamer - Adobe Experience Manager
No, it is not applying operator on given group id. Posted solution, Please check it
3237
Views
0
Likes
0
Replies
Re: How to specify nested “not” operation in specific gro... Anderson_Hamer - Adobe Experience Manager
I found that we should use nested group in order to specify operation on specific group id path=/content/course/type=cq:Pagep.limit=-11_property=jcr:content/eventgroup.1_group.1_group.daterange.lowerBound=2019-12-26T13:39:19.358Zgroup.1_group.1_group.daterange.property=jcr:content/xyzgroup.1_group.2_group.daterange.upperBound=2019-12-26T13:39:19.358Zgroup.1_group.2_group.daterange.property=jcr:content/abcgroup.1_group.3_group.relativedaterange.property=jcr:content/courseStartDategroup.1_group.3_...
3231
Views
0
Likes
0
Replies
How to specify nested “not” operation in specific group id in AEM? Anderson_Hamer - Adobe Experience Manager
I have a little complex predicator in which I need to have some nested not operation path=/content/course/ type=cq:Page group.1_daterange.lowerBound=2019-06-12T13:39:19.358Z group.1_daterange.property=jcr:content/xyz group.2_daterange.upperBound=2019-06-12T13:39:19.358Z group.2_daterange.property=jcr:content/abc group.3_relativedaterange.property=jcr:content/courseStartDate group.3_relativedaterange.lowerBound=0 group.p.not=trueI don’t want to include the result of group 1 and group 2 hence I am...
3267
Views
0
Likes
3
Replies
How to stop datetime conversion in aem 6.4? Anderson_Hamer - Adobe Experience Manager
We have a logic in back-end that gets the time & sets the timezone and finally sets the property in aem. The final property set as 2019-11-25T07:00:00.000+01:00 (Amsterdam timezone). When I try to read this property in jsp, like ${propName}, this is somehow getting converted and displaying as Mon Nov 25 11:30:00 IST 2019, All I can understand is that it is converting the time to local system/ or where jvm is located.All I need is, display the value as it stored in content repo .Is there any we c...
989
Views
0
Likes
0
Replies
AEM Query result is not in same order Anderson_Hamer - Adobe Experience Manager
We have a JCR query which will get the result of pages based on jcr:title property. There is no issue in the query and it is working as expected. When we run the query in two different AEM versions(6.0 & 6.4) the order is not same but we see the exact result. Both AEM versions don’t have any custom index and sorting mechanism but the end result is not having any same order. Has there any order logic implemented in AEM 6.4? What should we do in order to get the same order in AEM 6.0 and AEM 6.4? ...
1718
Views
2
Likes
3
Answers and Comments