Cornerstone will not load

Support
#1

Since I updated to Cornerstone 2.0.6, I am unable to edit any pages or posts. Cornerstone will not load. I am running the following:

Wordpress 4.8.1
X 5.1.1
Cornerstone 2.0.6

I have been searching the forum for the past few hours and trying all suggestions such as modifying wp-config file php memory to 256M and 512M. Turning off plugins. Install and running transient cleaner. Clearing browser cache and cookies.

Nothing has fixed the issue. Do you have any other suggestions?

Regards

#2

Hello There,

Thanks for writing in! Are there any error on the page? An error might be coming from your custom codes in the child theme’s functions.php that may no longer work or no longer compatible with the latest version. Could you please enable the debug mode to find out the error? You can do this by opening wp-config.php and adding define( 'WP_DEBUG' , true ); just above /* That's all, stop editing! Happy blogging. */

For example:

define('WP_DEBUG', true);

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

When you revisit the page, you should have some error output describing the issue in more detail.
Please let us know how it goes.

#3

Hello, I am not using a child theme. The spinner icon just spins. Here is a snap shot:

I tried turning on debug mode but there was nothing to see since page does not open. I used chrome and here is an image of the page in chrome degugger:

I see many other users posting this same issue but I have not seen a resolution.

Please advise.

2 Likes
#4

Hi

You can deactivate and then delete the Cornerstone plugin. Then head to the X mainpage inside WordPress and wait like 30 secs, as Cornerstone will then auto-magically re-install… and then enjoy a working Cornerstone :slight_smile:

#5

Hi,

Thank you for the suggestion but unfortunately it did not work. Here is new image from chrome debugger with same errors. I did notice the errors have “sourcemap” referenced in the js url which is slightly different from before.

Please advise.

1 Like
#6

Hi There,

Can you check in with your hosting and see if memory is enough for your site? We might increase it in wordpress but if it is not enough on your hosting that might be the reason. If that is sufficient, would you mind providing us with login credentials so we can take a closer look? Please provide following information:

Set it as Secure Note

  • Link to your site
  • WordPress Admin username / password
  • FTP credentials

All the best!

#7

I just added secure note

#8

Hello @jnlinn,

Would you mind confirming the password (WordPress) I am unable to login. Here is the error message I am getting:

ERROR: The password you entered for the username jlinn is incorrect. Lost your password?

Thanks.

#10

provided correct password in secure note.

#11

Hi,

Can you try testing for a plugin conflict. You can do this by deactivating all third party plugins, and seeing 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.

Let us know how it goes!

#12

Hello Paul,

I already tried deactivating all 3rd party plugins. I have tried every suggestion tried in this forum. Can you please login and check my account with the information I provided.

Thank you.

#13

Hello There,

We really wanted to login to your account to have a first hand experience of the issue. Regretfully the given credentials is not working for us. Please double check it because at the moment, the password is not working.

We are using this given credentials:

Kindly double check it.

#15

password sent in a secure note

#16

Hi there,

It looks like related to permalink, I switched it to the standard (plain) Permalink and it starts loading. And you’re on NGINX? Please check this https://codex.wordpress.org/Nginx and see if it’s configured correctly.

Thanks!

#17

Hello,

I finally found what was causing cornerstone not to load. It was this line in my nginx.conf file:

rewrite ^([^.]*[^/])$ $1/ permanent;

I added this to redirect all url’s to include the trailing slash. Without this line I have a duplicate content issue.

What is the correct nginx rewrite command to redirect to url with trailing slash?

Regards

#18

Hi there,

Thank you for your input. We are not Nginx experts unfortunately but I did a google search and found interesting results which I encourage you to check here.

Hope it helps.

#19

Thank you for the response, however I should have stated my question more clear. The nginx rewrite commands works fine. I have also tried the alternative nginx rewrite commands in the search you provided me. They all function correctly but cornerstone will not work with any of them.

I did not have to add the nginx trailing slash rewrite command until a recent update to X and Cornerstone.

I suspect the strange url that the new version of cornerstone editor uses “http://www.domain.com/x/#/content/some_number” has a conflict with the nginx rewrite command which adds a trailing slash.

I see a lot of people have similar issue of opening the cornerstone editor in this forum. I have been unable to edit my website for almost a month and it it becoming a major issue. Can this issue be escalated to help get fixed?

Regards

#20

Hi there,

There are similar issues in the forum, but with many different causes. And this is my first time seeing this kind of issue caused by NGINX permalinks, this https://theme.co/apex/forums/topic/cornerstone-does-not-load-on-new-pages-nginx/ could be similar, but it’s about passing the data back to index.php, you could try that too.

Please note that cornerstone doesn’t require any special rewrites, it all depends on Wordpress generated rewrite with simple lines like this (Apache)

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

I recommend contacting the hosting provider to gather information why it fails on their NGINX rewrites. It could be that that data is not properly received by the site due to those rewrites.

Thanks!

#21

Hello,

Unfortunately I am still unable to open cornerstone to edit any of my website pages. I have tried everything that I read in this forum and other forums.

My website has been working fine for over a year and I continually crawl it with Ryte. About two months ago after an update to X and Cornerstone, a Ryte crawl indicated the “non-slash” url was no longer directing to the url with a slash. This started to cause duplicate content issues.

I researched the issue and found two different methods of a rewrite rule to add to the nginx conf file. Either rewrite rule fixes the trailing slash issue. If I add either rewrite rule, cornerstone will not load.

There are other rewrite rules in the nginx config file that work fine.

Please help!

Regards

#22

Hi there,

Since NGINX requires complex customization for rewrites then I’m afraid you will have to remove the line that’s causing it (eg. the redirect that you mentioned).

rewrite ^([^.]*[^/])$ $1/ permanent;

Thanks!