Converted X -> Pro. Unable to edit any content

Support
#1

Hello,

I reviewed all of the posts with similar issues.

Issue: The website looks just like it did from X. Cornerstone is disabled (automatically) & when I attempt to edit anything with pro (headers, footers, content, etc), It just continues spinning.

What I have attempted:

  1. Confirmed PHP version (7.2)
  2. Updated links (changed htaccess & saved in perma-links)
  3. Cleared site & browser cache
  4. Disabled ALLLLLLLL plugins
  5. Increased memory limits

If I switch back to X & enable cornerstone, it works without any issues. If I switch to Pro, I am unable to “edit with pro”.

Am I missing anything?

#2

Hello Michael,

Thanks for writing in!

As you have tried the preliminary troubleshooting solutions and content builder in Pro is still not working, please share website login details in secure note for us to take a closer look.

Thanks.

1 Like
#3

Done. Thank you :slight_smile:

#4

Hi Michael,

Thank you for the credentials, most of the time status 500 error is a server side issue.



Please contact your hosting support regarding this matter as they have a better overview of what is happening on the /cornerstone-endpoint it could be blocked by a security feature of your server.

Let us know how it goes,
Cheers!

1 Like
#5

Thank you. I will reach out for support & let you know what they find.

#6

Feel free to let us know how it goes.

1 Like
#7

Update secure note with detailed errors from the server dev when you all have a chance. Please note, I did attempt to roll back the PHP version with no luck. Let me know your thoughts :slight_smile:

#8

Hey Michael,

Based on the error log, it seems that the error is because of a missing file. Kindly reinstall Pro again and make sure that the installation went through correctly then load the pages again in the Content Builder.

If the issue persists, please also provide us with the FTP details of you site so that we can check this further.

Thank you.

1 Like
#9

Thanks for setting me on the right track.

It reminded me of an issue from about a year ago. Essentially there was a file in the X theme that for whatever reason, my server host didn’t like. Originally it would automatically remove file permissions & I would get an error. Once we solved it, they manually added the file permissions (I couldn’t even do it via FTP or server side. They physically had to do it).

Long story short, this similar problem appeared on the pro version in class-model-content-template-entry.php. It was uploaded but it was not given the proper permissions by the server like all of the other files. Once I brought this to their attention, they were able to rewrite the permission. Not sure why they keep picking on your files but this was the issue.

This was NOT a theme.co issues at all but a server side issues as you expected. I really appreciate the support you all give us in your community. You have been nothing short of amazing over the past year for me!

Keep up the great work team.

#10

Thanks a lot for your kind words, Michael and glad to hear it’s sorted.

Have a nice weekend!

1 Like
#11

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