Error: The preview was unresponsive after loading. This is most often related to a plugin conflict or aggressive page cacheing

Support
#1

I am experiencing this error:“The preview was unresponsive after loading. This is most often related to a plugin conflict or aggressive page cacheing.”
Please, how can I resolve this?
I tried increase the memory of my wp-config.php t0 512MB but to no avail.

#2

Hi there,

Please kindly follow up the steps below:

  1. Ensure everything is up to date according to our version compatibility list here. Please follow the best practices when updating your theme and plugins. Click here for more information.
  2. Clear all caches including browser cache then deactivate your caching plugins and other optimization plugins.
  3. If you’re using a CDN, please clear the CDN’s cache and disable optimization services.
  4. Test for a plugin conflict. You can do this by deactivating all third-party plugins, and see if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.
  5. Remove custom CSS and Javascript from the options or Child Theme and test the case.
  6. Reset your htaccess file by renaming it to .htaccess-bak. Then in WP Admin Menu, go to Settings > Permalinks and just click the Save Changes button.
  7. Check the Article Below: https://theme.co/apex/forum/t/troubleshooting-builder-preview-warnings/14404

If the problem persists after the tests above kindly get back to us with the URL/User/Pass of your WordPress dashboard using the Secure Note functionality of the post to follow up the case. Also, tell us if it is only for one page or all pages if it is for one page give us the name of the page.

Thank you.

#3

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.

#4

Hey @ahwul,

There’s currently a known issue with Cornerstone where it gets stuck loading or stopped by the error message when the page has lots of elements on some servers. It looks like you’re having the same issue. The currently solution would be to click “Try Again” or reload the page several times until Cornerstone loads all elements. We understand it’s not ideal. A performance improvement might be included in one of the succeeding releases which might fix the issue.

For now, you could also try increasing the max_execution_time. Here’s a guide.

Thanks.