Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
There is something I don't really catch. The documentation sais that site-upgrade can be executed with the production site because the production site is not going to be modified. But I have tried to site-upgrade the production site and I found site-upgrade disabled all modules in production site.
The documentation sais source site isn't going to be modified but from my experience this is not true... I had to restore the backup to recover original state.
Am I doint anything wrong? Or did I misunderstand anything?
Comments
Comment #1
greg.1.anderson CreditAttribution: greg.1.anderson commentedI usually upgraded a copy of the production site; this is certainly safer. I am assuming that you are using a different site for the upgrade and the source? I think drush sup catches it if you try to upgrade a site over itself. Drush does disable all of the modules in the target site before beginning the upgrade; perhaps you set up your target site to use the same database as the source site? There could be some other bug in Drush sup as well; more info is needed to diagnose.