Pro 2.1.6 Editor endless loading

Hey guys,

while trying to open the pro editor I am getting these errors:

The cornerstone-logo is endless loading and I cant access the live-view. In skeleton mode I can edit my page.
Do you have a fix for me?

Best and thanks!

Hi There @RSMG

Thanks for writing in! I’m sorry to hear that you’re experiencing this issue. Most probably you’re running out of your allocated memory on your server. First make sure that you’re fully updated by referring to our version information here. Then once you updated your Pro theme, you need to clear style cache by head over to Pro -> Settings page. Also if you’re using a caching plugin, you need to purge server cache as well.

If you’re still having issues, then please check with the following as well.

Please install the following plugin ( activate it and then head over to Dashboard -> WP-Serverinfo section. Then check the following server configurations.

  • PHP Version - We recommend PHP v5.6.x or higher to avoid incompatibility issues. Some hosts allows to switch PHP versions within the hosting control panel. If not, you can contact your hosting provider and ask them to update.

  • PHP Memory Limit - We recommend PHP memory limit of 512 MiB. You can follow our guide here. Please check to see from WP-Serverinfo page whether it has been increased. Some hosting providers does not allow to increase it manually, so you will have to contact them directly.

  • PHP max script execution time - We recommend the value of 120 or higher (300). Here’s how to increase that value (

Also follow our troubleshooting guide here (

If you’re still experiencing this issue, please provide us with your WordPress login credentials along with your FTP credentials in a secure note to check your issue further.

Let us know how it goes.


both caches are already cleared multiple times.
My PHP version ist 7.1 (Cloudways), PHP memory limit is 512 MiB and max script execution is 1000s.
Do you have any other hint?


I found the problem: It was cloudflare. Now there is a rule not to cache /pro/ and it works again. Thank you for your help :slight_smile:

Glad that we could be of a help :slight_smile: For future references and other customers I will share the workaround with the CloudFlare here:

Thank you.

1 Like

Thanks very much for sharing this workaround!

1 Like

you are most welcome!

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