-
Posts
-
Hi there,
How about keeping the old theme on your live site for the moment and setting up a staging site in a separate sub-domain to test your issues? You can follow our migration guide here (https://community.theme.co/kb/cornerstone-migration/).
Then we should be able to help to identify your issues.
Thanks!
Thought it might be because I hadn’t update my separate installation of Cornerstone yet on my multisite install, but after I did that, I get this error on my realtyparadigm.com site:
Fatal error: Class ‘Cornerstone_Integration_X_Shortcodes’ not found in /home7/jcbhomes/public_html/realtyparadigm/wp-content/plugins/cornerstone/includes/classes/common/class-integration-manager.php on line 52
Can you guys please help me out here? Can I set up a phone call or something? I’ve got to get this straightened out ASAP. I’ll gladly pay whatever I need to pay for upgraded support or whatever. I just need to get it fixed.
Hi there,
The installation and update process corrupted the files. Please delete your cornerstone and install another one that comes with X 4.4.2 and don’t update it.
Then clone your site into staging using All in one migration plugin. Let’s do the testing and update on your staging site without doing damages on your live one.
Thanks!
How do I do that with a wordpress multi-site installation? I have 6 sites and they’re all using the same wordpress files. And my biggest concern is getting X 4.6.4 installed on my flatfeeindiana.com site. I’ve been uploading the new folder via FTP and renaming them for my upgrades. I’ve never had any problems with any other previous upgrades. Both current versions of X and Cornerstone are working fine. But every time I try to upgrade X or Cornerstone now, I get these errors.
Hi there,
You will have to clone the entire multi-site, we recommend to test the update before doing it on a live site. Any mistake can break it and it’s a common mistake. The update itself has no issue, but there are many contributing factors why it fails including the environment it’s running.
Please do that first before we continue. You may use All in one migration plugin on your main site (root) as network administrator. You can activate the migration plugin on network admin I think, and do the migration there.
Thanks!
All in one migration plugin won’t clone a multisite installation without a $180 extension – https://servmask.com/products/multisite-extension
I’ve had these sites running for years with no problems upgrading anything, ever. There’s got to be some trouble shooting you can recommend without requiring to go through all the trouble and expense of closing my entire multisite installation.
Hi there,
You can manually clone your site, but that something should be done by your developer to ensure that it’s identical to your live one.
There should be no problem, but the problem could be related to the filesystem (the process of adding and writing the files). All the errors that you provide are looking for the functions that supposed to be existing, but they aren’t because some files are missing. The update only uses WordPress resources to implement the updates, and it’s WordPress that to the file transfers and not the theme or plugins.
In this case, you could just backup your entire site then I’ll try updating it and if it fails, then your site may go down but you can restore it from your backup.
Thanks!
Well, unfortunately I’m the developer. 🙂 The way I’ve been “upgrading” is uploading the new files via FTP and renaming the old folder x-old. Is there a better way that I should be trying?
Hello There,
Thanks for updating in! Your method could also be correct. And if I am the one to make it the safest way of updating X, I would probably download the x folder to my computer so that I will have some backup. Delete the x folder to make sure that new files will be used. Then lastly upload the x folder of the latest version.
Hope this helps.
Well, I got it to finally run. What I did was uploaded the new X theme folder (named x-new). Then I renamed x to x-old. Then instead of renaming x-new to x like I had been doing, I went into my backend and into themes. It said something was broken in x theme (obviously because there was no x folder currently) so it was diverting to the default theme. I then went to the site and loaded it and it loaded fine into 2016 theme or whatever it was. Then, I went into filezilla and changed the x-new to x. Then i went back into the backend into themes and activated the X theme (2016 was set as the active theme). After that, I went to the site, refreshed, and all was well!!! Not sure why doing it this way would have any impact on how it worked, but I’m glad it did.
- <script> jQuery(function($){ $("#no-reply-1260470 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>
