Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Unable to add component on segment and experience fragment - AEM 6.4 with service pack 8

Avatar

Avatar
Validate 1
Level 3
Anderson_Hamer
Level 3

Likes

13 likes

Total Posts

34 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 5
View profile

Avatar
Validate 1
Level 3
Anderson_Hamer
Level 3

Likes

13 likes

Total Posts

34 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 5
View profile
Anderson_Hamer
Level 3

25-06-2020

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 8

Segmentation page screen shot

segmentIssue.JPG

Even experience fragment also have the same problem, no + plus button and drag and drop is also not working.

Experience fragment page screen shot

experienceFraIssue.JPG

Error log -

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'

 

The we-retail config shipped with aem and I dont see any misconfiguraion. The interesting thing is we have tried the same steps without service pack 8 where we don’t see this issue at all, able to see + button to add component on both segment and experience fragment pages. Is this known issue on service pack 8?

 

Note -  Restarted my AEM instance after installation of service pack 8, tried restarting my entire machine as well. Tried to setup 3 AEM instances and all ended up the same problem.

AEM 6.4 Experience Fragments Segments service packs Touch UI

Replies

Avatar

Avatar
Validate 1
Level 4
raghavc
Level 4

Likes

63 likes

Total Posts

61 posts

Correct Reply

19 solutions
Top badges earned
Validate 1
Give Back 5
Give Back 3
Give Back
Boost 50
View profile

Avatar
Validate 1
Level 4
raghavc
Level 4

Likes

63 likes

Total Posts

61 posts

Correct Reply

19 solutions
Top badges earned
Validate 1
Give Back 5
Give Back 3
Give Back
Boost 50
View profile
raghavc
Level 4

26-06-2020

It works properly in my local aem 6.4.8 instance, Please find the screenshot of the same.

Did you try to restart the AEM instance after installing the service pack ? If you see the issue , Can you try with a new AEM instance as it does not look like SP issue.

Selection_059.pngSelection_060.png

Avatar

Avatar
Validate 1
Level 3
Anderson_Hamer
Level 3

Likes

13 likes

Total Posts

34 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 5
View profile

Avatar
Validate 1
Level 3
Anderson_Hamer
Level 3

Likes

13 likes

Total Posts

34 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 5
View profile
Anderson_Hamer
Level 3

27-06-2020

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

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,127 likes

Total Posts

6,121 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,127 likes

Total Posts

6,121 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

29-06-2020

@Anderson_Hamer Do you see some error in console and error.log?

Avatar

Avatar
Validate 1
Level 3
Anderson_Hamer
Level 3

Likes

13 likes

Total Posts

34 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 5
View profile

Avatar
Validate 1
Level 3
Anderson_Hamer
Level 3

Likes

13 likes

Total Posts

34 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 5
View profile
Anderson_Hamer
Level 3

02-07-2020

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'

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,127 likes

Total Posts

6,121 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,127 likes

Total Posts

6,121 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

06-07-2020

I can only see Warning but not the error.

Avatar

Avatar
Validate 1
Level 3
Anderson_Hamer
Level 3

Likes

13 likes

Total Posts

34 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 5
View profile

Avatar
Validate 1
Level 3
Anderson_Hamer
Level 3

Likes

13 likes

Total Posts

34 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 5
View profile
Anderson_Hamer
Level 3

06-07-2020

Yes, Aem gives only warning on this page. There is no error. Are you sure it is working with sp8?