Authoring pages are blank while accessing the content pages | Community
Skip to main content
Raja-Karuppsamy
Community Advisor
Raja-KaruppsamyCommunity Advisor
Community Advisor
November 15, 2021
Solved

Authoring pages are blank while accessing the content pages

  • November 15, 2021
  • 1 reply
  • 1474 views

Hi All,

 

We are unable to access the content pages in author instance and seems to be clientlib files are corrupted. We have tried to invalidate the cache/rebuild the jsp file but the issue didn't resolve.

Any thoughts ?

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Raja-Karuppsamy

Can you try installing this in your local and check if that is working fine in your local ? Also if it throwing error, just check the we-retail or install wknd project https://github.com/adobe/aem-guides-wknd in your local and check if those are loading fine ? 

 

If yes, then the issue is with your project code. 


We have fixed the issue by deleting the "outputcache" directory from the bundle248 from AEM repository file system.


Clientlibs associated bundle is Adobe Granite UI Clientlibs (com.adobe.granite.ui.clientlibs) - bundle248 under "aem/author/crx-quickstart/launchpad/felix/bundle248/data/outputcache".


After AEM restart - outputcache directory re-created and pages are accessible now.
Reference: https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-16543.html?lang=zh-Hans

1 reply

Bhuwan_B
Community Advisor
Bhuwan_BCommunity Advisor
Community Advisor
November 15, 2021

@raja-karuppsamy Please check your Bundle status in OSGI Console. Please check for console error as well as if you are observing something in your Log files (Ex: error.log).

    Raja-Karuppsamy
    Community Advisor
    Raja-KaruppsamyCommunity AdvisorAuthor
    Community Advisor
    November 15, 2021

    @bhuwan_b All the bundles are in active state. We don't find any errors while accessing the content page.

      Raja-Karuppsamy
      Community Advisor
      Raja-KaruppsamyCommunity AdvisorAuthorAccepted solution
      Community Advisor
      November 15, 2021

      Can you try installing this in your local and check if that is working fine in your local ? Also if it throwing error, just check the we-retail or install wknd project https://github.com/adobe/aem-guides-wknd in your local and check if those are loading fine ? 

       

      If yes, then the issue is with your project code. 


      We have fixed the issue by deleting the "outputcache" directory from the bundle248 from AEM repository file system.


      Clientlibs associated bundle is Adobe Granite UI Clientlibs (com.adobe.granite.ui.clientlibs) - bundle248 under "aem/author/crx-quickstart/launchpad/felix/bundle248/data/outputcache".


      After AEM restart - outputcache directory re-created and pages are accessible now.
      Reference: https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-16543.html?lang=zh-Hans

        Terms & ConditionsAccessibility statement

        Loading footer...