Can't Save In Cornerstone After Adding Any Element

Cornerstone was working fine, then stopped after a few hours. I’ve attempted to restart browser, disable all extensions. Login/out of wordpress. Nothing is getting the application to work properly at all.

Every time I edit a page, create a section, and add an element, it happens every time. I’m dead in the water.

I’m using X Pro 1.1.0.

Hi there,

This should be checked in details for your case. Please kindly get back to us with the URL/User/Pass of your Wordpress Dashboard using the Secure Note functionality of the post.

Also, Please kindly follow the steps of articles below to fix the problem:

​https://theme.co/apex/forum/t/popular-questions/204
​https://theme.co/apex/forum/t/troubleshooting-customizer/196 (Not Working or Showing a White Screen section.)

​You may need to contact your hosting service provider for some of the steps mentioned above.

Thank you.

So far here is the configuration I was testing with no success:

  • Disabled all plugins
  • Removed all custom css from child theme
  • ensured the proper WP_MEMORY_LIMIT & WP_MAX_MEMORY_LIMIT entries are in wp-config file
  • Ensured PHP.ini (server) has 512mb memory limit configured
  • Remove all X Pro designed headers and footers from being applied to page
  • Removed all content sections/elements from page to start over, effectively starting from scratch
  • White-listed my IP from mod_security via CPanel
  • explicitly defined the open_basedir PHP directive
  • change DB collation from *unicode_ci to *general_ci

At some point, eventually, approximately after around 10-15 min. of use. & making a 3 column section & adding a feature box to each, it begins to display this behavior with a “cancel” icon when I hover over Save. Sometimes if I reload the page, the interface sometimes appears to be making changes & saving, but the actual page when tested/refreshed does not show any saves committed.

Hello There,

Thanks for updating in! The given password seems invalid. It does not work for us. Please double check. If you wouldn’t mind, also provide the ftp details so that we can investigate further.

Thank you very much.

:pensive: Sorry about that. I updated the credentials.

Hi,

Upon checking again, I can see the following errors in the console.

Can you try to whitelist those url as well.

Thanks

Just to confirm, are you referring to mod_security whitelisting?

(I also see these 500 errors in my Console panel in my browser Dev Tools.)

The 500 code errors that I see state “Unhandled AJAX error. Expecting valid JSON from response”:

Unhandled AJAX error. Expecting valid JSON from response. Object { readyState: 4, getResponseHeader: getResponseHeader(), getAllResponseHeaders: getAllResponseHeaders(), setRequestHeader: setRequestHeader(), overrideMimeType: overrideMimeType(), statusCode: statusCode(), abort: abort(), state: state(), always: always(), then: then(), 11 more… }

I don’t see any 406 so I’m now doubting you are referring to mod_security whitelisting. So since the URLs you referenced are all local to the site itself, I verified all permissions on those directories are all “0755”.

Please let me know what to do next - perhaps you can be specific as to what white listing you are referencing.

Lastly, I’m also receiving occasional messages when attempting to edit a content page with X Pro that state “A conflict on the front end of your site has prevented the preview from loading.” It seems I’m able to bypass the message, but all the above problems still exist too. I’ve also tried increasing PHP limit to 2048MB on server.

Something else I’ve noticed. I’m getting 404 errors referencing files/directories that don’t exists:

https://mydomain/wp-content/themes/pro/cornerstone/assets/dist/css/fonts/fontawesome-webfont.woff2?v=4.7.0

I’ve re-downloaded & re-installed X Pro on a totally separate environment, & I can re-produce these 404 errors for the fontawesome font each time when accessing the Content editor. I verified the woff files or directories are not there. Do you guys have a bad installer?

I’m beginning to think this has nothing with whitelisting, but is actually a known issue. See this link regarding /cornerstone-endpoint & 500 error:

I’m really trying hard to get this to work & even ran tests with my host. They said they tried increasing the memory significantly to everything & nothing appeared to work, so they need your input on what specifically to try next. It would be appreciated if you could help soon, I’ve got a client in the waiting. Thanks.

Hi there,

Thank you for giving us detailed information regarding the steps you have taken to fix this problem. As we do really have no problem on our servers and in our local installation this must be something related to your environment and the path you are taking is correct to rule out possibilities.

I tried to access the wp-admin of your dev website which you gave the link using Secure Note, but unfortunately, it goes to a 403 access denied page.

For that please kindly make sure all your Wordpress installation files and folders have correct permission according to this document:

https://codex.wordpress.org/Changing_File_Permissions

The Error 500 which you get is an internal server error, but it does not show the exact Server error which is there. Please kindly activate the Wordpress Debug mode:

https://codex.wordpress.org/WP_DEBUG

Then kindly contact your hosting service provider and ask them to check their error log to see what is the error.

On one of your messages, you mentioned that you whitelisted your IP in Mod_Security. Please kindly also add URLs to Cornerstone as well to the white list for the Mod_Security:

For example yourdomain.com/x/

And at last to make 100% sure that this is something related to your environment I suggest that you move your website to your local machine or another server to test.

Kindly get back to us with the reply of the hosting service provider regarding error 500.

Thank you.

Thanks for getting back to me. Between my last post & yours, everything started working. All 500 errors on cornerstone-endpoint seemed to be gone, so I re-enabled all restrictions to site administration. I’m not exactly sure what the magic bullet was.

One thing i did change, and I’m not sure if this impacted the 500 error, was update the database collation from a unicode_ci to general_ci. (I updated my troubleshooting steps above to include in this step to help any future researchers.)

I appreciate all your feedback, & this forum, for providing help!

Glad that you managed to fix the problem. And interesting point regarding the database collation. I did not encounter this before and it si a good point that you shared that with us here so our other customers also check the case as a step of troubleshooting.

Thank you.

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