When you press Edit in Cornerstone only the cornerstone logo apears and STUCK!

Support
#1

I setup a theme.co X demo (App demo) and when I go to a page and try to edit only cornerstone logo appears. if I press the page in the content list the page shows, but when I press the edit button only cornerstone logo appears and stuck.

I am using cornerstone 2.1.7, theme.co X 5.2.5 and word press 4.9.

#2

Hi There,

Since you just set it up, you might not have plugins or customizations yet, correct? If that is the case, please provide site URL and credentials on a secure note.

In case not and you have other plugins, you could 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!

#3

Can you see the secure note? is it private?

#4

Hi There,

Yes that is correct. Please provide username too.

#5

the user name is the website.

#6

Hi There,

Please double check credentials to avoid back and forth . It says password is incorrect.

#7

my bad. please find it here

#8

Hi,

Please provide your site url and login url as well.

Thanks

#9

www.picotera.co
http://www.picotera.co/wp-login.php?loggedout=true

#10

Hi,

Upon checking I can see some errors in the console.

What that error message tells us is that there’s something in your system preventing cornerstone-endpoint from loading. Please contact your hosting provider and request to whitelist the Cornerstone endpoint in any security rule. Along with that please make sure that the hosting you are using is compliant with the specifiations that WordPress community has recomended:

Thanks

#11

We are using ipage as a host.
Is it possible that this is a problem caused by permission and access. currently everything is on 755 on the server. do you have any comment on that ?

#12

Hi there,

Cornerstone works correctly with the normal recommendation of the WordPress. For more information:

https://codex.wordpress.org/Changing_File_Permissions

According to the article above the recommended file permissions for files is 644 and for the folders is 755. Advise your hosting service provider and check if they may need other permissions for their settings.

Also, I suggest that you enable the WordPress to debug mode so instead of the error 500 which my colleague gave the screenshot, you will see the actual error:

https://codex.wordpress.org/Debugging_in_WordPress

I also suggest that you ask your hosting service provider to give you the error log so you can check the case.

Lastly kindly make sure that the cornerstone URLs which in your case is www.picotera.co/x and all it’s sub URLs will be ruled out of your hosting service provider mod_security settings. This is something that they can change on their side and you probably do not have access.

Thank you.

#13

thanks for the comments. I talked to the host and they seems to think it is not from their side. I am quite frustrated. can you please help me fix this?

#14

Hi There,

I’m getting an Internal Server Error when logging to your site. Could you please post your FTP credentials in secure note also if possible, provide your web hosting control panel access (iPage vDeck).

Thanks!

#15

I believe for both of them you can use this credentials.

#16

Hi,

I tried logging in to FTP and ipage but the login credentials you provided doesn’t seem to work.

Kindly check again and let us know.

Thanks

#17

the first letter is capital only. Please note.

#18

Hi There,

Upon checking, I see that you’re running PHP v5.5.22 on your server. Is is possible to update it to PHP 5.6.32 or PHP 7.1.x as WordPress recommends it to avoid incompatibility issues.

Let us know how it goes.
Thanks!

#19

I am getting the same type of error when updating to the latest versions.

Failed to load resource: the server responded with a status of 500 (Internal Server Error)
cs.js?ver=2.1.7:56152 Rejecting AJAX promise Object__ember1511985560269: "ember575"proto: Object
handleResponse @ cs.js?ver=2.1.7:56152
cs.js?ver=2.1.7:41932 Object__ember1511985560269: "ember575"proto: Object
cs-vendor.js?ver=2.1.7:19500 TypeError: Cannot read property ‘indexOf’ of undefined
at getStack (cs-vendor.js?ver=2.1.7:19456)
at defaultDispatch (cs-vendor.js?ver=2.1.7:19500)
at Object.dispatchError (cs-vendor.js?ver=2.1.7:19483)
at onerrorDefault (cs-vendor.js?ver=2.1.7:33226)
at Object.trigger (cs-vendor.js?ver=2.1.7:51931)
at cs-vendor.js?ver=2.1.7:52925
at invoke (cs-vendor.js?ver=2.1.7:1335)
at Queue.flush (cs-vendor.js?ver=2.1.7:1399)
at DeferredActionQueues.flush (cs-vendor.js?ver=2.1.7:1207)
at Backburner.end (cs-vendor.js?ver=2.1.7:521)
defaultDispatch @ cs-vendor.js?ver=2.1.7:19500

#20

@kytmagic2, Unfortunately, it doesn’t have any details of the error. Would you mind creating a new thread and provide this information in a secure note?

  • Site’s URL
  • FTP login credential
  • Admin login Credential

If you don’t wish to provide the credentials, then please provide the error log :slight_smile:

  1. Edit your site’s wp-config.php
  2. Replace this line define('WP_DEBUG', false); with this
define('WP_DEBUG', true);
define('WP_DEBUG_DISPLAY', false);
define('WP_DEBUG_LOG', true);

  1. Load the page that has that error (to trigger the error), it will only log new errors.

  2. Download the file /wp-content/debug.log and provide its content in a secure note of your own thread.

Thanks!