Not able to move experience fragments | AEM
When someone attempts to move a content fragment in ÃÛ¶¹ÊÓƵ Experience Manager 6.5, the UI will spin, and the move operation is not processed completely. Follow the steps given in this article to resolve the issue.
Description description
Environment
-
Experience Manager 6.5
-
Experience Manager as a Cloud Service
Issue/Symptoms
When someone attempts to move a content fragment, sometimes the UI will spin, and the move operation is not processed completely.
- Not able to move experience fragments.
- The *Move page…*status window popup spins and never completes.
- The issue is occasional - It can be successful when moving to some folders and not others.
- The success seems to depend on the number of nodes in the destination folder.
Resolution resolution
Solution
Follow the steps given below to resolve the issue:
- Browse to your and edit the configuration for Apache Sling Get Servlet. For cloud environments, edit the configuration
org.apache.sling.servlets.get.DefaultGetServlet. - Increase the value for JSON Max Results. The count towards the JSON Limit is the number of all the children and grandchildren (resources) of the target folder. So, if the target folder is /a/b/c, then the count is all resources in /a/b/c and their children.
- Clear the browser cache.
- Retest the use case. A restart is not required.
It is recommended to limit the number of assets in a folder to 1000, as outlined in the below documents. There is no need to increase this number to more than 3000. As long as we comply with this recommendation, we should not experience any performance issues with this configuration.
Go through below mentioned documentation links for more information:
Ask Questions In Our Experience League Campaign Community
If you have any questions you’d like answered about this topic, or read previous answered-questions, we invite you to view our  that includes this article, send us your questions and comments, and join our Experience League Campaign Community!