Steps:
Actual: page is not opening in live copies console since it has large amount of data. Expected: All pages should be opened in the live copies console.
I tried above steps in my local, there live copy console opened successfully. What is the exact issue and is there any workaround for this issue?
Solved! Go to Solution.
Views
Replies
Total Likes
You may consider disabling the unified shell in the Adobe Cloud environment and then attempting to open the page. I personally encountered a similar issue with a content fragment having too many RTEs, and was able to resolve it after disabling the unified shell.
Hi @prahlad-dutta
Have you verified with the same amount of content locally where it worked? You might need to check error logs and thread dumps if there is any relevant information.
Regards,
Arpit Varshney
Yes, we have verified in local the content amount is same in local as well as on environment.
This issue is not happening with other pages. The page which we are trying to see the live copy it has around 84 child pages.
Below error noticed in error log:
06.02.2023 07:04:36.462 [] *INFO* [152.58.17.175 [1675666807888] GET /libs/wcm/msm/gui/content/livecopies.html/content/<site-name>/language-masters/en/page HTTP/1.1] org.mongodb.driver.connection Opened connection [connectionId{localValue:176, serverValue:436}] to <url>.mongodb.net:27017
06.02.2023 07:04:49.108 [] *INFO* [qtp558410539-526] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials
06.02.2023 07:05:13.825 [] *INFO* [qtp558410539-526] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials
06.02.2023 07:05:16.205 [] *INFO* [qtp558410539-439] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials
Hello,
How did you identify that its because of number of child pages?? the log you shared has only info no error, probably try to grab the error/warning coming during the process in error.log and share.
another work around to clear the doubt is to create a new live copy page hierarchy with less number of pages and test it.
Thanks!!
You may consider disabling the unified shell in the Adobe Cloud environment and then attempting to open the page. I personally encountered a similar issue with a content fragment having too many RTEs, and was able to resolve it after disabling the unified shell.
Views
Likes
Replies
Views
Likes
Replies