I was following the documentation for the archtype setup. I get everything setup from this link: https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-wknd-tutorial-devel...
I'm working on a Mac Pro (intel). I didn't have any problems instaling java, maven etc. Can someone explain what I might have missed that the content and compoents aren't showing up when I log into my local and edit the site pages?
Solved! Go to Solution.
I was able to fix the problem. I couldn't use @RajaShankar solution. The build wouldn't work at all, having issues with the pom.xml in the ui.content. In the end I changed the aemVersion to 6.5.5 and the archetypeVersion to 34.
While this worked for a time, when I came back after restarting AEM, I was given a 503 error. I've seen this error before from not closing down AEM properly, but that wasn't the case this time. I did close it properly.
I think part of this fix is to have the documentation portion of the site updated. For now I'll just continue to re-install things and move on. This can be closed.
I am not sure what param you passed for archetype.Please try with below and let me know
mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=32 -D appTitle="WKND Sites Project" -D appId="wknd" -D groupId="com.adobe.aem.guides.wknd" -D aemVersion=6.5.9.0 -D includeDispatcherConfig=y -D frontendModule=general -D datalayer=y -D artifactId="aem-guides-wknd"
Above worked for me with all components and content.
Note: Execute the Command prompt in Admin Mode.
Please refer the below steps to debug the issue -
1. Please check error.log file and find out the page path and verify whether you are getting any exceptions or not.
2. Regarding the none of the components load issue , please traverse the content path in crx/de as shown below and check whether component node is available or not after drag and drop the relevant component -
3. Please access the 'en' page as view as publish using page information and verify whether you are getting any exception or not -
I feel these steps will help us to debug the issue.
I was able to fix the problem. I couldn't use @RajaShankar solution. The build wouldn't work at all, having issues with the pom.xml in the ui.content. In the end I changed the aemVersion to 6.5.5 and the archetypeVersion to 34.
While this worked for a time, when I came back after restarting AEM, I was given a 503 error. I've seen this error before from not closing down AEM properly, but that wasn't the case this time. I did close it properly.
I think part of this fix is to have the documentation portion of the site updated. For now I'll just continue to re-install things and move on. This can be closed.
How did you manage to fix this issue?
Views
Replies
Total Likes
I am getting the below error. when using aemVersion to 6.5.5 and the archetypeVersion to 34.
Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.12.0:npm (npm run prod) on project aem-guides-wknd.ui.frontend: Failed to run task: 'npm run prod' failed. org.apache.commons.exec.ExecuteException: Process exited with an error:
Views
Replies
Total Likes
Yeah, looks like I am still facing this issue as well with AEM 6.5
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies