Cornerstone - Can't Install, Not in X Extensions

Support
#1

I updated Cornerstone before updating X, site crashed, deleted Cornerstone through Filezilla, site came back with gobbledegook on pages. Now, can’t find Cornerstone in X Extensions. Saw note on X admin panel to install Cornerstone manually, link led me to support, not a Cornerstone zip file I can use.

Someone told me Cornerstone update problem due to host’s php version, so I’m considering WPEngine immediately - would go with you guys, but I’m traumatized and need a hug.

T. Lavon Lawrence

1 Like
#2

Hi there @tlavonlawrence,

Don’t worry! Help is at hand. :slight_smile:

First of all follow the following steps.

1: Deactivate and delete X
2: Make sure you don’t have a “cornerstone” folder within your wp-content/plugins folder via FTP.
3: Download the latest copy of X via your Apex dashboard
4: Upload the zip via your wp-admin > appearance > themes > add new > upload
5: Upload and activate.
6: Cornerstone will now automatically install and you should be back up and running.

Thanks!

#3

Followed instructions as listed, however, after reactivation of X, get error message about Cornerstone NOT installing, do it manually:

Plugin could not be activated because it triggered a fatal error. Parse error: syntax error, unexpected ‘[’ in /var/www/vhosts/74/239649/webspace/httpdocs/loboy.com/wp-content/plugins/cornerstone/includes/classes/admin/class-updates.php on line 222

  • The NEW Cornerstone folder from the new X upload is showing in my FTP file manager.

  • Cornerstone is showing in Plug-ins list, but I can’t activate. Gobbledegook still showing on landing page, etc.

Ready for next suggestion…

#4

Okay, it’s fixed. Per Support Forum instructions, I found a similar topic and made some code changes - completely out of my area of daily work but I stumbled through to the finish line: https://theme.co/apex/forum/t/cornerstone-fatal-error-after-update/10199/4?u=tlavonlawrence

You guys rock.

#5

Glad you were able to fix it :slight_smile:

#6

Looks I have a similar problem!

#7

I saw on your other thread you were able to get it fixed. Feel free to followup there, or in a new thread if you need anything else.