Cannot use Pro

Support
#1

Hi guys,

Odd one here - recently my site stopped working with pro - cannot use the editor in any shape or form.

I have disabled all plugins, cleared cache and put cloudflare into dev mode. But still issue persists…

Look forward to your help :slight_smile:

#2

Hi There,

Thanks for writing in!
I can see the Pro editor is working fine and I am able to edit any page.
Also theme option.

Let me know any particular issue you are facing.

Thanks

#3

Apologies,

forgot to say it is header and footer specifically :frowning:

Cheers.

#4

Hello @kademcconville,

Thanks for updating thread. :slight_smile:

I see following error message in browser console in Launch Page Failed to load resource: the server responded with a status of 500 () https://rkade.uk.com/cornerstone-endpoint. What that error message tells us is that there’s something in your system preventing cornerstone-endpoint from loading thereby blocking Cornerstone from saving/functioning correctly. If you could contact your host and they should be able to whitelist the Cornerstone endpoint and get this working. Along with that please make sure that the hosting you are using is compliant with the specifiations that WordPress community has recomended:

Thanks.

#5

Thanks for your help,

Seems odd because I have made no changes whatsoever and this has stopped working :frowning:

This is what my hosts had to say;

Hello Kade,

Thank you for contacting Smart Hosting.

I understand rkade.uk.com is actually hosted on your VPS? So it won’t be anything our end blocking it, as any settings will be managed VPS side which is currently not managed by us.

If you have any security settings on the VPS it might be worth reviewing these to see if they conflict with it.

See I have cloudflare installed but have always had the following page rule enabled;

rkade.uk.com/x/

Which stops the caching of Cornerstone. Not sure what to do next here…

#6

Hi there,

Some say it’s due to 1.2.7 update which contains the updates for WP 4.9, but I think it’s due to 4.9 and it caused some internal issues. I’ll continue checking, but in my installation, I’m having timeout issues with 1.2.7 and WP 4.9 BUT works pretty well with 1.2.7 and WP 4.8.3. I say it’s due to WP 4.9 since the recent Pro/X update only contains fixes for MEJS (media players) for 4.9. But maybe I’m wrong, I checked your site and It has the same issue with my installation, the preview timeout issue, but it works after a couple of reloading then mostly works.

Plus, I’m getting this error from your builder (header/footer)

(index):1 Uncaught SyntaxError: Unexpected end of input jquery.js:2 Uncaught Error: Syntax error, unrecognized expression: #function ROOT() {}

Which indicates that the page doesn’t load well or incomplete. Plus, the jQuery error is originating from WP Core. How about cloning your site and downgrade its core to 4.8.3?

Would you mind providing your CF login credentials? The Unexpected end of input error is may be related to it.

Thanks!

#7

Thanks for the update! :slight_smile:

An interesting read!

I have updated my secure note :slight_smile:

#8

Hi There,

I have checked again and see the same error but then this is the error I found on the console:

It is not the same error found previously with @Rad but the result on header being not accessible is the same. Since that is the consistent error, that might be the reason behind this error. Please check error log. Let’s see if we can find more details in there.

1 Like
#9

Error log shows last cornerstone issue at 02 October, 2017.

:frowning:

#10

Hey @kademcconville,

I see the issue like @Lely.

This is mostly due to server configuration. There really might have been changes in your configuration or other third party factors such as CDN. Regretfully, we could not provide support in troubleshooting server configurations. Would you mind copying your site to a staging server then give us its WP admin and FTP access so we could deactivate everything and just test the header builder?

Thanks.

#11

Even when disabling the CDN and caching, this problem persists however, would that make a difference?

Thanks for the on-going support :slight_smile:

#12

The only change made from me is the update to wordpress 4.9 :frowning:

#13

Hi there,

I’m also getting the same error like Lely and Christian.

That error would normally indicate an error on the server, not anything with the theme code. I would suggest contacting your host regarding this issue.

Thanks for understanding.

#14

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