|
OEPB
|
January 30, 2017 at 2:45 pm
I Chair a community breakfast.
Unfortunately out Webaster resigned last year and we did not have the knowledge to keep up with the plugin upgrade cycle and it looks like it may not be possible to upgrade from the real old version to the new version.
Apparently there was a major version upgrade required last year that changes the EE Database structure but it wasn’t done… I think we may be now too far behind.
Can I ask your advice as to how we can migrate from 4.8.43.p to 4.9.26.p as it places our whole system into Maintenance mode (including the backend!) and the upgrade fails with this error message, “Update Failed: <!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”> 500 Internal Server Error Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator and inform them of the time the error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log.”
|
|
Seth Shoultes
|
January 30, 2017 at 3:30 pm
Hi there,
That doesn’t sound like much fun. This page has quite a bit of information about migrating and updating: https://eventespresso.com/wiki/how-to-upgrade-event-espresso/#update-event-espresso-4
Down at the bottom of the page there’s a section that discusses troubleshooting:
https://eventespresso.com/wiki/how-to-upgrade-event-espresso/#troubleshoot-a-migration
You could also try migrating to EE 4.9.1, then migrating to 4.9.26. You can download the tag for 4.9.1 from Github: https://github.com/eventespresso/event-espresso-core/archive/4.9.1.p-sans-tests-tag.zip
Please let us know if you are still stuck.
|
|
Tony
|
January 30, 2017 at 5:07 pm
Hi there,
I just wanted to add some more information that may help.
When EE4 runs migrations it checks on the current state of your database and runs the required migrations from that point through to the current release. This means you don’t need to install previous versions, run the migrations and then update and repeat, EE does this for you using the latest version (you’ll have multiple migration steps to run through).
It also means that unless another developer has modified the database structure or code for EE then updating from 4.8.43.p to 4.9.26.p is not a major problem for EE although we do change how things work from time to time depending on what your previous developer did some things may need to be changed/fixed.
This error:
500 Internal Server Error Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request.
Means your server is returning an error when EE runs the migration, EE may well be ‘causing’ the error to throw, but the actual cause of the error we can’t see from the above. It could be your site is running out of memory, some form of mod_security rule is blocking EE from updating the DB or even something completely un-related.
We would need to see the raw error that’s thrown rather ‘pretty’ version your server is currently showing. (Your server will have an error log, usually called error.log or similar that should hold all of these).
If you are unsure how to find the error log you may need to contact your hosting provider and have them either oint you to where they store errors, or have them send you what error is being thrown during the migrations so we can investigate.
|
