On 6.5 localhost, touch UI, as user "admin", the edit mode doesn't work for one site.

Forum|Forum|5 years ago
May 25, 2020
4 replies
6954 views

hi folks,

On the site navigator, I can click on the page and open it using "Edit" but once the page is displayed, I can't edit anything.

I can't click on any component to edit them.

The "Edit" option on the top right hand core is greyed out. If I click on it, it goes Blue for a few seconds, then reverts to greyed out.

The Preview button also doesn't work and the "Design" and "Develop" options are missing entirely.

If I look at localhost:5402/useradmin, then the Admin user has all the permissions for the /content/<site> clicked.

I can't see anything relevant in the logs.

Any ideas?

thx

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 Hamid1350

Check the same scenario in incognito window.

Invalidate Caches then click Rebuild Libraries.

http://[host]:[port]/libs/granite/ui/content/dumplibs.rebuild.html

Ankur_Khare

Community Advisor

Check the console logs.

Refer this thread a s well-

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-2-too-many-calls-sling-exception/qaq-p/224517

F

fionas76543059Author

Level 6

Thanks all for the very useful suggestions which I will file away for future problems. In this case, I decided that the problem site had too many pages that I downloaded from the production server and that my localhost didn't have enough memory etc to cope. So I scrapped the entire localhost installation and restarted it with more refined packages with smaller numbers of pages. It has been fine so far.

BrianKasingli

Community Advisor and Adobe Champion

Have you tried using another browser, other than Chrome?

Ravi_Pampana

Community Advisor

Hi,

Seems you are having custom code deployed. There might be scenarios where you are still referring to login administration in your code which might be throwing exception and failing to load the page correctly.

Go to view source of the page without editor.html and check if you see any exception.

Also, check browser console for any js errors which might be causing because of adding custom code to OOB clientlibs category.

Is the issue happened suddenly or happening while migration/upgrading the code to new version of AEM ? It will be helpful if you can provide background after when the issue is started happening.

Hope this helps!

F

fionas76543059Author

Level 6

Thanks all for the very useful suggestions which I will file away for future problems. In this case, I decided that the problem site had too many pages that I downloaded from the production server and that my localhost didn't have enough memory/cpu/diskspace to cope. So I scrapped the entire localhost installation and restarted it with more refined packages with smaller numbers of pages. It has been ok so far.