The following section covers some issues that you might encounter when using AEM, together with suggestions on how to troubleshoot them.
When experiencing problems it is also worthwhile checking the list of Known Issues for your instance (release and service packs).
Users who have administrator privileges, and who want to troubleshoot problems with AEM, can use the troubleshooting methods described in Troubleshooting AEM (for Administrators). If you do not have sufficient privileges, please see your system administrator about troubleshooting AEM.
Issue:
Reason:
Solutions:
There are various possibilities here:
Confirm that the page has been replicated correctly. Check the page status and if necessary, the state of the replication queue.
Clear the cache in your local browser and access your page again.
Add ?
to the end of the page URL. For example:
http://localhost:4502/sites.html/content?
This will request the page directly from AEM and bypass the Dispatcher. If you receive the updated page, it is an indication that you should clear the Dispatcher cache.
Contact your system administrator is there are issues with the replication queues.
Issue:
Reason:
Solution:
Issue:
find
term are replaced on a page.Reason:
The capability of Find & Replace depends on how the content is saved, and whether it can be searched upon. For example, a blog text is stored in jcr:text
property which is not configured to be searched upon. The default scope for the find and replace servlet covers the following properties:
jcr:title
jcr:description
jcr:text
text
Solution:
These definitions can be changed with the configuration for Day CQ WCM Find Replace Servlet using the Web Console; for example, at
http://localhost:4502/system/console/configMgr