Pro Editor Isn't Working even after plugins have been deactivated

[mtrokic]

I’m having issues with Pro. Initially I was having problems with cornerstone as it wouldn’t load. Everything was up to date.

I updated to Pro thinking that it would help and it didn’t. In some cases I can’t open the editor, in others I can’t see the preview.
I either see the circle of death spinning and never ending or a message: The preview was unresponsive after loading. This is most often related to a plugin conflict or aggressive page cacheing.

I don’t have Hummingbird downloaded. I have WP Smush and I deactivated the plug in, but the problem still occurs.
JS and CSS minification are deactivated on WP Rocket.

[nico]

Hi @mtrokic,

Thanks for writing in.

I believe that you still have cornerstone. Cornerstone is not needed anymore in Pro. If still not helping, please share us your admin credentials so we could check your setup closer.

Don’t forget to set it in a secure note.

Thanks.

[mtrokic]

Hi Nico, I have added a secure note. Cornerstone is deactivated but Pro still isn’t working. Someone suggested having Cloudfare in another thread, but i don’t have it and never have.

Thank you for looking into this.

[paul.r]

Hi,

You forgot to include your site url.

Please provide link to your site.

For the mean time, you can try adding the code below in your wp-config.php file located at the root directory of your site.

define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

You may add it before this line of code

/* That's all, stop editing! Happy blogging. */

Hope that helps.

[mtrokic]

Sorry about that! My website URL is added now.
I have tried adding the code into my wp-config.php file, however the problem still persists.

[Joao]

Hi @mtrokic

When Pro is trying to load we get the following message on the console:

Failed to load http://www.sibername.com/: Response for preflight is invalid (redirect)

Seems like your installation is causing your browser to send a CORS preflight OPTIONS request that does a redirect.

Browsers currently refuse to follow the redirect in that case, because the CORS spec previously required browser to do that. The restriction is actually no longer in the spec, but browsers need to update their implementations to match the spec change.

You may contact your hosting provider to see if they can find out something about it in order to avoid triggering the browser to send the request.

Let us know how it goes.

Thanks

[mtrokic]

I got a response from the provider. Not sure what to do at this point? See below:

Please note that the website is hosted on a shared hosting platform and almost all websites hosted on the server uses CORS (Cross-origin resource sharing). This pre-flight request is made by some browsers as a safety measure to ensure that the request being done is trusted by the server. In other words, Attacks like DDOS, Injection insertion does not use CORS and this allows the server to distinguish the requests received.

Unfortunately, It’s not realistic to set the flag for all users and being a security feature at the server side as this request cannot be disabled on a per user basis and it is not recommended as well. If you are on a VPS or a dedicated server for your website, this could be feasible.

[mtrokic]

Provider changed the PHP version and Pro finally started working. Solved!

[christian]

Glad it’s fixed now.

[jbillh]

What PHP version did they change it to?

[lely]

Hi There,

Theme and plugins are compatible to PHP 7. In case you are having issues, please do open a new thread with complete information so we can help you better.