Critical Error in Cornerstone 5.3.3 - disables Admin access

[ConsortChorale]

@tristup requested that I make this a separate topic:
Fatal error : Uncaught Error: Call to undefined method ReflectionType::getName() in /var/www/consort_shared/wp/www.consortchorale.org/wp-content/plugins/cornerstone/includes/classes/Plugin.php:106

I have tried deleting the plugin and re-installing. No difference.
I am using:
Wordpress: 5.7.1
X Theme: 8.3.3
Cornerstone: 5.3.3
PHP ver: 7.0.33

I am only able to prevent this by reverting Cornerstone back to 5.1.5, my only available previously saved version. It appears to mostly work, though it is not the compatible intended version with XTheme 8.3.3. I’ve only found one minor rendering error, but we have stopped making changes to any of our Cornerstone pages.

I see that you have other similar topics appearing. One possibility, which I noticed with @gbg4, is that we both are using an older version of PHP, 7.0. We are in the process of updating our PHP, but it will still take a while to complete.

@tristup requested access to our server for testing. Unfortunately I cannot provide that, as our server is shared with other websites, not under my control. Hopefully you will find a solution that will work for all of us.
Thanks.

[tristup]

Hi @ConsortChorale,

I have visited your website and found that you are using the older version X (version 8.3.3) theme whereas the Cornerstone has been updated to 5.1.5. The issue you are having might be due to the incompatibility between X and Cornerstone. I would suggest you follow the below steps while updating the X theme and the Cornerstone.

1. Delete the Cornerstone existing one
2. After deletion of the Cornerstone, please use the link in the dashboard to automatically install the Cornerstone.
   
   

Hope it resolves your issue.
Thanks

[ConsortChorale]

I’m confused. Everything I see says that X 8.3.3. is the most recent version. I know it wants to then have Cornerstone 5.3.3, but that is the version that crashes the Admin area. I reverted Cornerstone back to 5.1.5 in order to avoid the crash. It mostly works, and keeps the site running, but I know it is not compatible.
I see that in the other thread with @gbg4, they are being recommended to upgrade to PHP 7.4. I suspect that may be the same thing we need to do. It seems that the change to Cornerstone in 5.3.3 is incompatible with PHP 7.0.
I have to switch hosting services to upgrade PHP - so hopefully I will be able to test that soon.

[friech]

Hi @ConsortChorale,

Yes, that is true that we saw a lot of crashing site using an outdated PHP version. Please upgrade to PHP 7.4 before updating X and Cornerstone to the latest version.

Let us know how it goes,
Cheers,

[ConsortChorale]

I’ve run into another problem. In order to update PHP we are moving to Dreamhost. I’ve started a staging server in a Dreamhost subdomain in order to make sure everything will work before moving the actual site. But on that staging server it will not let me activate X Theme, and thus I cannot update Cornerstone. I’ve never had this problem on my old dev servers. Perhaps that is because they are local?
Is there a way for me to have a non-local staging server without buying another license?

[ConsortChorale]

Never mind - I finally found where to change the URL of the staging server.

I would suggest a change to your UI. On the left on the account pages you have “Single Licenses”. In that dropdown you show “X url”. I thought, because of the X, that button would remove our existing license’s URL. I don’t think you should have the X there, as it is confusing. Once I did click the url, it took me to the right place to change our staging server URL.

OK - now I finally get the “joke”. The “X” means that the license is for “X Theme”, and its not meant to mean “delete”. Still - the UI is confusing.

I can now also report that updating PHP works. I now have a working Cornerstone.

[ruenel]

Hey @ConsortChorale,

We’re glad that your issue has been resolved. If there is anything else we can help you with, please do not hesitate to open another thread.

Cheers.

[brianjohnsondesign]

Just wanted to add that I had this same error, and it does appear to be an issue with Cornerstone 5.3.3 and PHP 7.0. Updating PHP solved the problem for me.

[marc_a]

Hi @brianjohnsondesign,

We’re glad that it is now working properly on your end! If you have any other concerns or clarifications regarding our theme features, feel free to open up a new thread.

Thank you.