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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Editor and 'View as Published' pages are blank

Avatar

Level 4

I've been at this for three days and can't figure out why pages for our company's site are all blank in my local AEM 6.5.0 instance. I get the gray top nav bar with the three icons ("Toggle Side Panel", "Page Information", and "Emulator"), but there's no content for any of our pages. The We.Retail pages are fine. Is there a checklist of items I can go through to help identify the issue? I've got the following packages installed:

  • core.wcm.components.all-2.8.0.zip
  • acs-aem-commons-content-4.3.2.zip

 

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi @Codelime ,

 

You could start from here:- 

 

  • Check if all your application (and related) bundles are in an active state.
  • After the page loads Checks error.log, to see if there are any specific errors related to the application code.
  • Sling request trace http://localhost:4502/system/console/requests to see if the page renderers are being picked correctly for page request.
  • Check if you have dependencies on core components for page rendering and if it's installed.
  • Check the status of your sling models. http://localhost:4502/system/console/status-slingmodels 

Hope this helps!

 

Regards,

Nitesh

 

View solution in original post

3 Replies

Avatar

Community Advisor

Hi @Codelime 

 

Could you please check the below things:

  • open /system/console/bundle and check if all bundles are active - If not, start from there why bundles are not active.
  • Please check the error logs after loading the page and check if you see any error in logs that might cause the issue.
  • Check for console error in the page.

Regards,

Arpit Varshney

Avatar

Level 4

Thanks for the reply. 

  • All bundles are active, although the following four have status "Fragment":
    • Adobe - XMPFiles Worker platform fragment linux (com.adobe.xmp.worker.files.native.fragment.linux)
    • Adobe - XMPFiles Worker platform fragment macosx (com.adobe.xmp.worker.files.native.fragment.macosx)
    • Adobe - XMPFiles Worker platform fragment win (com.adobe.xmp.worker.files.native.fragment.win)
    • Day Communique 5 License Branding (com.day.cq.cq-licensebranding)
  • Errors
    • 18.01.2023 00:00:58.661 *ERROR* [sling-default-2-health-com.day.cq.compat.codeupgrade.impl.hc.MissingPackagesHealthCheck] com.adobe.granite.queries.impl.hc.QueryHealthCheckMetrics Error in refreshing the health check gauge
      com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 1 column 1480105 path $.data[580].contentPackage
    • 18.01.2023 00:01:58.653 *ERROR* [sling-default-3-health-com.day.cq.compat.codeupgrade.impl.hc.MissingPackagesHealthCheck] com.adobe.granite.queries.impl.hc.QueryHealthCheckMetrics Error in refreshing the health check gauge
      com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 1 column 1480105 path $.data[580].contentPackage

Avatar

Correct answer by
Employee

Hi @Codelime ,

 

You could start from here:- 

 

  • Check if all your application (and related) bundles are in an active state.
  • After the page loads Checks error.log, to see if there are any specific errors related to the application code.
  • Sling request trace http://localhost:4502/system/console/requests to see if the page renderers are being picked correctly for page request.
  • Check if you have dependencies on core components for page rendering and if it's installed.
  • Check the status of your sling models. http://localhost:4502/system/console/status-slingmodels 

Hope this helps!

 

Regards,

Nitesh