Upgrade/update process too cumbersome
I've harped on this before so I apologize for returning to the same subject. But I just checked a website after a couple of months and find there are a bunch of module updates needed, many of them security issues, and a new core security update. I'm starting dread running the status report because it's such a cumbersome process. I've heard that updating a site takes 15 minutes, but it takes me 2 hours, and it seems I always end up with plenty of errors and confusion! CCK fields go missing, or I forget to turn off a contrib module, etc…. I just can't imagine that everyone who uses drupal is not having the same issues? And as I now have three drupal sites running and many more planned I'm getting worried that the process will become overwhelming.
With everything else that is so awesome about drupal I can't understand why all this update process is not automated? I’m will forever be a newbie with limited programming skills. I hope version 7 will fix streamline or eliminate the update process.
I’ve assembled a list of modules that help with the process below. But if you have any new ideas please let me know. I never got into the 'drush' thing because I completely didn't understand it, but it looks like I will have to take a better look. Let me know your thoughts on it.
•http://drupal.org/project/drush
•http://drupal.org/project/admin_menu
•http://drupal.org/project/devel
•http://drupal.org/project/backup_migrate which backs up the database.
•http://drupal.org/project/contrib_toggle which disables the contributed modules with one-click. (doesn't yet have 'enable' though!)
Please add yours.
I’ve also been told that I don’t have to disable the contrib modules, but every time I’ve run an update but I ran into nightmares when I didn’t. Below is the current overwhelming procedure I follow, and it doesn’t take into account that I’m meant to do this entire process locally before I do it on the production site! There is no way; (and I gave up on that because every time I try to publish the site locally, and/or back to production, I always lose all the images even though they are in their correct folder locations and I’ve never worked out why.) So I now just back up the database and files and run the updates/upgrades straight on the production site.
Here is the cumbersome procedure:
1. Back up database
2. Back up the files.
3. Put site in maintenance mode
4. Change from a contrib theme to garland
5. Upload new Drupal core (6.14 now)
6. Replace the Sites folder with my old one
7. Disable Contributed modules (thank goodness for the disable contrib toggle module)
8. Run update.php
As I have modules needing updating, I next
9. Remove the out-of-date modules
10. Upload updated modules
11. Enabled all the contributed modules (what a waste of time re-selecting all the boxes!)
12. Run Update.php again (no problems)
13. enabled theme
14. Put site back online.
So please give me your recommendations. This is all just too much and something always seems to go wrong! Let me know if Drush will solve all my issues and if you think I should take the time to figure that out? Or if you have any other modules or methods that will work correctly and safely?

I'm such a lazy person.
This is what I do ...
1. Check that my nightly cPanel backup didn't crash.
2. Upload the new Drupal core ... omitting the sites folder and .htaccess file (which usually has some extra config stuff I've put in).
3. Run update.php without bothering to put the site in maintenance mode ... it only takes a minute or so.
if a module needs updating ...
4. delete old module folder
5 upload new module folder
6. Check the status report.
7. run update.php if and ONLY if status report complains about db schema being out of date.
I'm assuming that you're only doing minor upgrades ... within Drupal 6 ... not a major upgrade from D5 to D6. For that ... I'd follow your 14 step program of monotonous drudgery.
Maybe I'm living dangerously ... but so far my lazy approach hasn't ended in tears or tantrums.
Wow Matt, I won't say it was
Wow Matt, I won't say it was easy, but it sure beat the nightmare I've been going through! Everything seems fine; I certainly don't have the problems I've had every other time.
How come your instructions go against everything I've read? How did you figure it out; just common sense?
I have to try this on the another site now... thanks
I've been using Drupal for a
I've been using Drupal for a few years now ... and developed these shortcuts because I'm so lazy. I also have nearly 300 sites to manage (nearly all Drupal) .. so I had to find a way to streamline the process a bit.
I agree with everyone's observations here regarding the Drupal upgrade process. It is quite cumbersome.
However ... I've got a few Wordpress, OpenX, LinkX and Sugar CRM sites with fancy schmancy install routines ... believe me ... they DON'T always work ... and the manual recovery process is a sheer nightmare.
I'm sure Drupal will eventually ship with a nice install process. Like many though ... I'm more interested in security, robustness, scalability, SANITY, and reliability than convenience.
There are commercial services spouting up that provide Drupal site moderation, etc ... I expect some enterprising individual will create a commercial auto-update service soon (hint hint).
Thanks!
That worked like a charm for my 6.13-->6.14 update on a CentOS 5.4 system.
My update looked like this:
use backup_migrate module to download a copy of my database
stop httpd
download updated modules into /tmp
use gzip and tar to extract the new module directory for each updated module
delete the module directory in in my /sites/all/modules directory for each updated module
mv the new module directories from /tmp to /sites/all/modules
chown -R apache.apache for each new module directory
download drupal 6.14 and extract contents on top of my drupal directory
run update.php
everything continues to work as expected and I'm all up to date now
Yay!
Yep
I have to agree with kellyllek, I nearly went the wordpress route for this very reason. In wordpress it is simply a case of clicking the update button - easy! In the end Drupal won in its other areas of power and flexibility. Please, though, can we have an easy update process. Please!
There is mass confusion with
There is mass confusion with the process too and I reckon it leads to a ton of problems for users. I know it sounds obvious but I wonder how we'd submit a streamlined update/upgrade request to the development teams? I'm worried they are so overwhelmed with individual aspects of Drupal that collectively they don't realize what a huge problem this is, especially for beginners. Many are left in the cold when something goes wrong. I know because I've submitted many requests for help and if it weren't for some kind forum members, extra tenacity and some luck I would have given up a long while ago.
Aside note; I thought about setting up a paid support site that would work just like the forum does, but members would be able to offer payment for help requests and experts could bid up or simply answer the question and receive a reward if the answer is accepted. There are so many questions that go unanswered and sometimes it might be something minor, yet the person having the problem may spend hours or even days searching for the answer. I know people can hire a developer but there is a support level below that yet above the regular forum which is missing. This is one of my many projects on the back burner but if anyone wants to pursue this please let me know.
Anyway, just thoughts. My whole business is heading to Drupal and I'm apprehensive to say the least!
Thanks
Thanks Matt,
I've upgraded using your method and it was *much* easier than before. I still agree with kellyllek, this process needs streamlining. It really is a deal killer - I'm sure I'm not the only person who has nearly given up on Drupal just because of the upgrading issues.
Aside note; As a newbie I
@kellyllek wrote: Aside note;
As a newbie I agree with this. Would also love to pay someone for a quick answer. It's frustrating asking for help and getting no answer. I know people do this for free but let us have a forum where people are paid to help us beginners or else we maybe give up on Drupal.
Also agree with the BIG time it takes for updating and so and hope it will be easier in version 7.
totally agree
I completely agree with you about the upgrade process and ranted about it in another thread
http://drupal.org/node/590152
Matt, can you be a little more specific about what you're doing? First, are you saying you don't bother to delete all the old files/directories, and second, are you uploading the tarball and just expanding it on the site, meaning its basically overwriting everything? Or do you expand it all on your dev machine or whatever and then upload the files etc.
Thanks!
Howard Johnson
My shortcuts apply only to
My shortcuts apply only to minor updates within a major Drupal version. If you're upgrading from Drupal 5 to Drupal 6 , I'd follow the official instructions to the letter.
When updating the core files ... I don't bother to delete the original files first. The "logic" behind this is that minor versions don't tend to remove or rename files.
The same does NOT apply to contributed modules ... always delete the original folder first. Chances are the module developers rearrange and rename files more often than the Drupal core does.
I always expand the tarball on my dev machine and upload using FTP in overwrite mode. I'd prefer a more economical approach as you suggest, but I don't have SSH access to my server, just FTP.
shortcuts or longcuts, still not working...
I have tried the long way and the short way to update from 6.13 to 6.14. I have checked system.module and it says I'm running 6.14; SimpleScripts also agrees that I'm running 6.14. But in my admin pages it keeps asking me to update. I have overwritten, deleted then re-uploaded, tinkered with default.settings, turned contrib modules off and on...to no avail. This has happened to me with modules before and I've been able to get them to work by deleting the old version and then uploading; not so with this core update. Any suggestions or other things to try?
Thanks in advance for any suggestions!
Jessica
Paid Drupal services
I have found this site http://drupal.org/paid-services and maybe there are several more out there?
Upgrade to 6.14 Newbie Nightmare
The initial install of Drupal on Ubuntu desktop worked fine but there was an immediate request to upgrade to 6.14 and I complied. After some problems (like where is "Drupal Core", and how would I know what user Apache runs as?) I got it apparently ready to go, but this morning another security request pops up - and it's the same one, 6.14 and now I'm ballistic.
=-=
The long upgrade procedure in the UPGRADE.txt is more for moving from one major version to another. ie: from Drupal 6.x to Drupal 7.x when it is released. The steps are necessary because 6.x custom/contrib modules and custom/contrib themes won't work with the next major version. Those steps likely won't change much.
For updating a minor version to another minor version (6.13 - 6.14), some of the steps in UPGRADE.txt can be ignored as seen in this thread.
I tend to draw a line where many don't. An upgrade being, from one major version to the next and an update being from one minor version to the next.