Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By shp.jc on
We're in the middle of an upgrade from 4.6 to 5.1.
We've been doing the upgrade on a snapshot from about 2 months ago.
Next we're skinning the site with a completely new design.
We're also trying to plan the deployment to the live site.
What's the best way to put the new skin and database structure into production with the live data?
Do we have to take the site down and "start over" on the version-wise upgrade?
How have others done it?
Thanks
Comments
=-=
Wouldn't bite off more than can be chewed at one time.
I'd do my upgrade, using a default theme.
Then build my new theme, or add it to the existing installation
We would still need to
We would still need to upgrade the live database to 5.1, even if we postpone the redesign.
=-=
That's my point.
Get the DB upgrade out of the way, using a default theme, not a previously customized theme. To insure that the site will work once its upgraded.
We have a working copy of
We have a working copy of the upgraded site in dev.
I'm not worried about the upgrade working.
But the data in the dev site is several weeks old.
I'm worried about getting the upgrade applied to the live database with minimal downtime and no loss of data.
=-=
Then yes, put the site in maintenance mode. make a back up of the live site, upgrade it, and go.