Expand my Community achievements bar.

SOLVED

Authoring pages are blank while accessing the content pages

Avatar

Community Advisor

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 ?

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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

View solution in original post

6 Replies

Avatar

Community Advisor

@Raja-kp 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).

Avatar

Community Advisor

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

Avatar

Community Advisor

Hi @Raja-kp 

Hope you must have tried blow if not you can give a try and see if that helps: 

 

1. If you have we-retail OOTB site on author, check whether you're able to access those pages or not so that we can know whether it's global issue or issue related to the specific project.

2. Check error logs and see if you can find anything while accessing pages.

3. Did you verify core components are up to date or not?

4. Did you try restarting AEM server and see if that helps?

5. Make sure all the bundles are active 

 

Thanks

Avatar

Community Advisor

@Siva_Sogalapalli This issue is with all the projects. We have restarted the AEM service multiple times but No luck.

Avatar

Community Advisor

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. 

Avatar

Correct answer by
Community Advisor

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