|
Claire Kennard
|
January 27, 2016 at 6:52 am
Hi,
I am moving my site from one domain to another (company name change) and taking the opportunity to move hosts too.
I have backed the database up from the existing site and imported it into the new site and have also copied across the latest version of EE. The new site is running WP 4.4.1 and the database from WP updates and runs fine.
When i try to upgrade the EE database it gets to 100% then just hangs and the whole site goes down with a 500 error.
When i try and start with a clear database the same thing happens, it crashes out with a 500 error
This is causing major disruption as the new site is due to go live soon
Please can someone help?
|
|
Claire Kennard
|
January 27, 2016 at 7:07 am
Sorry, Just to update, this is actually form 4.7.0 to 4.8.0
|
|
Josh
|
January 27, 2016 at 8:00 am
Can you check the new server’s error log to find the cause of the 500 error? Many times it’s an error that’s caused by the server running low on memory, so one thing that can help is you bump up the amount of memory that WP can use. You can bump up the amount of memory available to WordPress by following this guide:
https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
|
|
Claire Kennard
|
January 27, 2016 at 8:14 am
Hi, Sorry i don’t have access to the error logs, ill try increasing the memory though if i can
|
|
Josh
|
January 27, 2016 at 8:30 am
You can also set up your own error.log file and capture errors in the wp-content folder by setting up error logging. Here’s another guide from the WordPress codex that you can follow:
https://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_Debugging
|
|
Claire Kennard
|
January 27, 2016 at 8:31 am
Hi,
I tried upping the memory but still the same, crashed out at 98%
Thanks
|
|
Claire Kennard
|
January 27, 2016 at 9:03 am
Hi, I appear to have fixed it, I deactivated all plugins except EE and then ran the migration and it worked
Thanks for your help
|
|
Tony
|
January 27, 2016 at 9:04 am
If you add something like this:
define( 'WP_DEBUG', true ); // Or false
if ( WP_DEBUG ) {
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
}
To your wp-config.php file WordPress will create a debug.log file within /wp-content/ that stores any errors being thrown whilst WP_DEBUG is enabled.
|
