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

Parsys not appearing with editable template - AEM 6.4.4 with nosamplecontent runmode

Avatar

Avatar
Boost 1
Level 1
BaluM
Level 1

Likes

2 likes

Total Posts

5 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
BaluM
Level 1

Likes

2 likes

Total Posts

5 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
View profile
BaluM
Level 1

19-03-2020

Hi,

We are getting issue when page created with Editible template where parsys is not showing to edit page.

 *This issue occurred only if instance created with "production / nosamplecontent " run mode, this is working fine in a lower environment where sample content is available. 

 

We are getting the same issue with below sample custom template package. 

https://github.com/Adobe-Marketing-Cloud/aem-sites-example-custom-template-type

 

Error logs: 

19.03.2020 17:34:29.117 *WARN* [10.50.134.19 [158463926906] GET /conf/projname/settings/wcm/templates/test/structure.html HTTP/1.1] org.apache.sling.caconfig.resource.impl.def.DefaultConfigurationResourceResolvingStrategy Ignoring reference to /conf/projname/settings from /conf/projname/settings - Probably misconfigured as it ends with '/settings'.

 

Please share your thoughts.

 

AEM 6.4 parsys Templates

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

582 likes

Total Posts

564 posts

Correct Reply

218 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

582 likes

Total Posts

564 posts

Correct Reply

218 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
BrianKasingli
MVP

25-07-2020

@BaluM,

When you generated the /conf folder, you might have copied over some references of we.retail example, rather than using AEM's out of the box configuration manager, http://localhost:4502/libs/granite/configurations/content/view.html/conf, where this is a common mistake as most developers take templated or inspiration from the we.retail project. 

How to fix: My suggestion is to analyse the nodes from "/conf/projname/settings", and ensure there are no references to the we.retaill components & configuration, and also ensure all referenced sources in AEM exists.

Please take a moment to follow this video tutorial, as it will show you exactly how to create an editable template from scratch, https://www.youtube.com/watch?v=4FWTs_RAO34

I hope this helps,

Brian.

Answers (0)