HTTP 500 on the entire site after update from Pro 1.1.1 to 1.2.3

[hostedpci]

Hi,

I updated to WP 4.8.2 (was previously 4.8.1) and Pro was 1.1.1 before.

When I did, staging looked fine but when I pushed it live the site is showing HTTP error 500 on both the pages and WP-admin.
My host is showing the following error:
PHP Fatal error: Cannot redeclare class Cornerstone_Shortcode_Generator in /nas/content/staging/hpciprimary/wp-content/themes/pro/cornerstone/includes/classes/classic/builder/class-shortcode-generator.php on line 2585

Which is the same error as another topic that wasn’t resolved a couple of weeks ago:

HTTP ERROR 500: Fatal Error after Cornerstone update

My site is using PHP 5.6, so I don’t think it’s the same issue a similar topic had:

HTTP ERROR 500 after update

But the symptoms look the same as both those other topics.

Since I’m using Pro and not X anymore, I re-read the migration instructions and noticed Cornerstone as a standalone isn’t used anymore so I tried to delete that in the hopes that will solve it but it didn’t.

Anyway, right now I left the broken version on staging even though it’s visually working.

EDIT: I provided all the information needed in the secure note.

Staging site URL: https://hpciprimary.staging.wpengine.com/

Thanks for the help!

[Jack]

Hi there @hostedpci,

Thanks for writing in! I’ve taken a look at this and there is a jQuery error coming from the Content Builder on load of the home page when trying to edit the content in the content editor.

I’ve debugged and can’t find that there is an issue in the actual Content Builder itself, but I noticed that some of the plugins are quite old. Could you update those plugins or can we? Just to verify if it’s possibly a conflict with an outdated plugin.

Thanks!

[hostedpci]

Hi Jack,

Thanks for the reply.

Please feel free to update or do anything else to them.

I’ve made sure I have everything I need on production and I also have backups for both staging and live so we should be ok.

Regards,
Elad

[rad]

Hi there,

How did you switch to live server? Maybe the issue is in the process of moving it. I don’t see any issue with the staging, perhaps the copying and duplicating files triggered the issue?

Could you switch live and I’ll set it again? Please provide the live site’s FTP credentials as well so I could check if the files are okay.

Thanks!

[hostedpci]

Hi Rad,

I can’t afford to have the site not working for a full day while you guys get around to test it.
If you want to do it like that, I’d be more than happy if we can setup some time and do it live so I know when to release it live and when to revert it back when it fails.

In terms of how I switched, we use WPEngine and they have a release mechanism that does everything automatically.
Again, the error I initially showed you guys is showing on both staging and live even though on live the site doesn’t respond at all and on staging somehow it still kinda working.

EDIT:
After talking to WPEngine and describing the situation, they suggested I just clone my WP instance and then you will have a cloned live environment to work on without taking my website down so I did.
Mind you because it’s a different URL and you guys pushed an update in the middle of my cloning process, I had to cut corners to validate my license on that new instance using my staging’s site license key.

So I’ll add in the secure note all the new credentials for this clone so you will be able to debug it.
Keep in mind that I tried today to update all plugins and then disable all plugins and it still didn’t solve the issue.
I also noticed that “Edit with Pro” stopped working for me after the update and when I tried to disable the plugins, I found out one of the plugins caused it, but even after disabling that plugin and updating to 1.2.4, I still get HTTP error 500 when pushing live.

So now we have 2 separate problems:

1. HTTP 500 message only on live.
2. Edit with Pro preview shows “A conflict was encountered on the page, please try again” error message.
   I looked up the plugin and turned out that error was already reported in the plugin’s GitHub page. The author of the plugin claims the issue is a bug between Pro’s JS and MooTools framework.
   https://github.com/AndiDittrich/WordPress.Enlighter/issues/84

Anyway, would be great if you could help with problem number 1, I don’t expect a quick fix for problem number 2 but it would be great.

[rad]

Hi there,

Thanks for the detailed information, really appreciated it.

As for problem 2, looks like you’ll gonna wait for their v3 as they are going to remove MooTools.

And for problem 1, looks like I’m not gonna need your staging site anymore since the only way to continue is checking your live site. How about providing your live site’s URL and login credentials? But if you can provide an error log then that could be sufficient to determine the issue.

Please do this,

1( Edit your live site’s wp-config.php and replace this line

define('WP_DEBUG', false);

with these new lines

define('WP_DEBUG', true);
define('WP_DEBUG_DISPLAY', false);
define('WP_DEBUG_LOG', true);

2. Load the page that has 500 error

3. Go to /wp-content/ folder and download the file debug.log and provide it in your reply.

Thanks!

[ADBL]

Any update on this? Same exact problem with latest X and CS. Fine on (WP Engine) staging, 500 error on the live site. All plugins updated.

I’ve got X 5.0.3 and CS 2.0.5 on the live version (works fine). Everything updated on the staging site. I works fine on staging, but as soon as I deploy to live I get this error.

[ADBL]

This workaround fixed the issue.

[christian]

Hey @hostedpci, can you try the solution suggested by @ADBL. If the staging to live process does not change existing files then this could be the cause of the issue.

Thanks.

[hostedpci]

As @ADBL mentioned, that solution indeed fixed the problem.
Spoke with WPEngine about it, their standard staging -> live process basically makes a soft copy or it merges the code, any garbage files in live will remain there which was probably the reason why it worked on staging but not on live.
They have another process which I decided to take advantage of, since my account allows for multiple instances (10 in my case), I’m using a second instance which will be an exact copy of my actual site.
So then we make all the changes to the website on that new live instance and we deploy it to the actual live instance.
So instead of staging -> live, it will be instance1 live -> instance2 live which will guarantee a deep copy.

Anyway, thanks to everyone!

[ruenel]

You’re welcome!
We’re glad we were able to help you out.