Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
Hi there,
In an attempt to update my Drupal 7 to a Drupal 8 site, my first step was to transfer the working drupal 7 site from a provider to my local server.
I Did this several times but somethings changed I Think
Steps I took in the past
1 Copy all the files from te provider to my local machine
2 Make an export from the Db with phpMyAdmin
3 Import that database to my local DB (phpMyAdmin from Xamp)
4 Change settings.php (dbname,user pwd) to my local settings
5 Up and running.
While upgrading to 8.3.0 on the update.php step I got an awful Ajax error http 500.
A first few steps seems having updated part of the database but hang on "blocks" step.
I have "customized blocks" without any content. That may be from a contributed module hanging the process?
Tried 2 times. I reverted to versions 8.2.7 being unable to fetch any log, server log or else. It is on a production site. I never encountered that problem before though upgraded previous core minor versions 3 times without any difficulties.
Hi all, I ran into a funny situation when updating to Drupal 8.3.0 from the 8.2.x series. When I used composer update, the packages kept swapping back and forth in a repeating cycle (downgrade-upgrade-downgrade-upgrade)
I was able to break out of this by deleting the whole vendor library and running 'composer update' from scratch. I also removed composer.lock . Now everything is fine.
Here is what the issue looked like when it was happening:
"An error has occurred.
Please continue to the error page
An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /ministry of trade/batch?id=75&op=do StatusText: OK ResponseText: Fatal error: Maximum execution time of 30 seconds exceeded in C:\xampp\htdocs\ministry of trade\includes\common.inc on line 976"
on line 976 the code is "$chunk = fread($fp, 1024);"
I'm recently trying to update my Drupal site from 8.2.7 to 8.3.0.
The site uses Display Suite and Bootstrap Layouts modules, both requiring the Layout Plugin module.
After several attempts, I was forced, before the update, to uninstall Display Suite, Bootstrap Layouts and Layout Plugin modules and then, after core update, to activate the new experimental core module Layout Discovery (incompatible with Layout Plugin), before reinstalling the updated Display Suite and Bootstrap Layouts modules.