Expand my Community achievements bar.

SOLVED

Latest Archetype 51 | Issue | Homepage not being rendered.

Avatar

Level 1

Hi Community,

 

I created a new project from scratch based on the latest archetype, but it loads blank after trying to load the home page.

It is important to mention all bundles are up and running all dependencies are OK, the only log messages I get are the following.

 

================================================================================================

 

13.11.2024 10:15:23.646 *WARN* [[0:0:0:0:0:0:0:1] [1731514523581] GET /editor.html/content/aem-library/language-masters/en/home.html HTTP/1.1com.adobe.cq.wcm.launches.impl.LaunchesAdapterFactory Failed adapting resource [/content/aem-library] to [interface com.adobe.cq.launches.api.Launch]: {}
13.11.2024 10:15:23.647 *WARN* [[0:0:0:0:0:0:0:1] [1731514523581] GET /editor.html/content/aem-library/language-masters/en/home.html HTTP/1.1com.adobe.cq.wcm.launches.impl.LaunchesAdapterFactory Failed adapting resource [/content/aem-library] to [interface com.adobe.cq.launches.api.Launch]: {}
13.11.2024 10:15:23.648 *WARN* [[0:0:0:0:0:0:0:1] [1731514523581] GET /editor.html/content/aem-library/language-masters/en/home.html HTTP/1.1com.adobe.cq.wcm.launches.impl.LaunchesAdapterFactory Failed adapting resource [/content/aem-library] to [interface com.adobe.cq.launches.api.Launch]: {}
13.11.2024 10:15:23.932 *WARN* [[0:0:0:0:0:0:0:1] [1731514523926] GET /content/aem-library/language-masters/en/home.html HTTP/1.1com.adobe.cq.wcm.launches.impl.LaunchesAdapterFactory Failed adapting resource [/content/aem-library] to [interface com.adobe.cq.launches.api.Launch]: {}
13.11.2024 10:15:23.983 *WARN* [sling-pageinfoproviders-processing-pool-2com.adobe.cq.wcm.launches.impl.LaunchesAdapterFactory Failed adapting resource [/content/aem-library] to [interface com.adobe.cq.launches.api.Launch]: {}
13.11.2024 10:15:23.990 *WARN* [[0:0:0:0:0:0:0:1] [1731514523957] GET /mnt/overlay/wcm/core/content/editor/jcr:content/content/items/sidepanel.content.html/content/aem-library/language-masters/en/home.html HTTP/1.1com.adobe.cq.wcm.launches.impl.LaunchesAdapterFactory Failed adapting resource [/libs/settings/cq/search/facets/manuscript] to [interface com.adobe.cq.launches.api.Launch]: {}
13.11.2024 10:15:23.995 *WARN* [[0:0:0:0:0:0:0:1] [1731514523957] GET /mnt/overlay/wcm/core/content/editor/jcr:content/content/items/sidepanel.content.html/content/aem-library/language-masters/en/home.html HTTP/1.1com.adobe.cq.wcm.launches.impl.LaunchesAdapterFactory Failed adapting resource [/libs/settings/cq/search/facets/pages] to [interface com.adobe.cq.launches.api.Launch]: {}
13.11.2024 10:15:23.996 *WARN* [[0:0:0:0:0:0:0:1] [1731514523977] GET /libs/wcm/core/content/pageinfo.json HTTP/1.1com.day.cq.wcm.core.impl.servlets.PageInfoServlet Configured provider com.day.cq.wcm.core.impl.servlets.ContentLanguageServlet not loaded for resource /content/aem-library/language-masters/en/home
13.11.2024 10:15:23.999 *WARN* [[0:0:0:0:0:0:0:1] [1731514523957] GET /mnt/overlay/wcm/core/content/editor/jcr:content/content/items/sidepanel.content.html/content/aem-library/language-masters/en/home.html HTTP/1.1com.adobe.cq.wcm.launches.impl.LaunchesAdapterFactory Failed adapting resource [/libs/settings/cq/search/facets/products] to [interface com.adobe.cq.launches.api.Launch]: {}
13.11.2024 10:15:24.015 *INFO* [[0:0:0:0:0:0:0:1] [1731514524008] GET /libs/wcm/core/content/components.1731513890901.json HTTP/1.1com.day.cq.wcm.core.impl.components.ComponentServlet provided components.
 
==============================================================================
 
Screenshot 2024-11-13 at 10.15.11.png
1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi, 
I think there should be something else in the log to indicate what's going on. I just used the archetype 51, as you mentioned, to generate a project and deploy it into my local SDK Version 2024.10.18311.20241017T104455Z, and it worked without any problems.

mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \
 -D archetypeGroupId=com.adobe.aem \
 -D archetypeArtifactId=aem-project-archetype \
 -D archetypeVersion=51\
 -D appTitle="My Site" \
 -D appId="mysite" \
 -D groupId="com.mysite"

EstebanBustamante_0-1732022730165.png

Here are a few things to check:

  • Ensure you are deploying to the correct version (AEM Cloud to a valid SDK version, and On-Premise to an on-premise AEM instance).

  • In my opinion, the logs should point to something else. Please double-check and see if you find anything, and post it back.

  • Try installing the same project on a fresh AEM instance.

Hope this helps



Esteban Bustamante

View solution in original post

2 Replies

Avatar

Administrator

@EstebanBustamante @SureshDhulipudi @Jörg_Hoh @h_kataria would you please take a moment to review this question? We would be grateful if you could share your suggestion on this question.



Kautuk Sahni

Avatar

Correct answer by
Community Advisor

Hi, 
I think there should be something else in the log to indicate what's going on. I just used the archetype 51, as you mentioned, to generate a project and deploy it into my local SDK Version 2024.10.18311.20241017T104455Z, and it worked without any problems.

mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \
 -D archetypeGroupId=com.adobe.aem \
 -D archetypeArtifactId=aem-project-archetype \
 -D archetypeVersion=51\
 -D appTitle="My Site" \
 -D appId="mysite" \
 -D groupId="com.mysite"

EstebanBustamante_0-1732022730165.png

Here are a few things to check:

  • Ensure you are deploying to the correct version (AEM Cloud to a valid SDK version, and On-Premise to an on-premise AEM instance).

  • In my opinion, the logs should point to something else. Please double-check and see if you find anything, and post it back.

  • Try installing the same project on a fresh AEM instance.

Hope this helps



Esteban Bustamante