Cannot upgrade modules - "date" and "webform" - upgrade will not "take"
Using "Update status 6.14 Checks the status of available updates for Drupal and your installed modules and themes." I received notifications last week that Drupal, webform, WYSIWYG, date, CCK, etc. had security updates.
First Attempt
- Backed up my database and files to my local computer
- Downloaded & unzipped Drupal 6.14
- Downloaded & unzipped new versions of all the contributed modules
- Combined all of these into a single directory structure
- Put the site into maintenance mode, disabled all modules
- Used FTP to write the new files, "overwriting" all files
- Ran update.php
- Re-enabled some modules
- Ran update.php
- Drupal core and several modules reflected updates correctly, but date and 1 other did not
- Ran update.php, choosing the last "version" manually for those modules, although the numbers didn't look quite right
- Received an error that a date table couldn't be created because it already existed
- Manually deleted said table
- Ran update.php
- Received another database error
- Rolled back to the previous installation of Drupal and modules
- Dropped all tables from database
- Imported all tables & data from backup
- Deleted all files from drupal installation directory
- Added all files from backup
Second Attempt
- Downloaded & unzipped Drupal 6.14
- Put the site into maintenance mode, disabled all modules
- Backed up all Drupal files to a different directory under the root (drupal_backup)
- Deleted all files from current Drupal Installation
- Uploaded Drupal 6.14 files and my backed-up sites directory
- Ran update.php
- Re-enabled some modules
- Ran update.php
- Downloaded & unzipped new modules
- Disabled all modules
- Deleted all modules
- FTP'ed new module files for those needing updates, same module files for those not
- Ran update.php
- Enabled some modules
- Ran update.php
- CCK and other modules are updated, but date and webform are not according to update status and version number in the modules admin
Third Attempt
Prior to this I backed up my database and drupal files again to preserve the previous successful updates, preserving the old files for date and webform.
- Left modules enabled
- FTP'ed new module for date and webform using overwrite
- Ran update.php
- Disabled modules
- Ran update.php
- Enabled modules
- Ran update.php
- date and webform still do not show update
Forth Attempt
- Disabled modules
- Deleted folders for date and webform
- FTP'ed updated files for date and webform
- Ran update.php
- Enabled modules
- Ran update.php
- Disabled modules
- Deleted date and webform folders
- FTP'ed old files for date and webform
- Ran update.php
- Enabled modules
- Ran update.php
- Disabled modules
- Deleted folders for date and webform again
- FTP'ed new files for date and webform
- Ran update.php
- Enabled modules
- Ran update.php
- Disabled modules
- Ran update.php
- date and webform still do not show that they've been updated
- Left site in maintenance mode all weekend, hoping it was a cache problem
- Ran update.php (3 days later)
- date and webform still do not show updated versions in the update status module OR on the modules admin page.
I have checked the .info files in the date and webform directories, from what I can discern (as a new Drupal user) the versions I have in my modules directory are the new versions.
Is there some way I can determine what changes need to be made for the update, aside from the new files themselves (which are thoroughly updated), make those changes, then manually force the update to register?
I am new to Drupal, so I don't really know where everything is. Thank you in advance for your help.

look in the directories where
look in the directories where those add-in modules live. Make sure that the upgrade is not living as a subdirectory of the date and webform folders. This often happens to me.
---------------------
"He's said to be outspoken, but nobody's actually seen anyone do it"
Thanks -- but no subdirectories here
Thank you for your reply. Unfortunately that's not the case here. The date module has a number of subdirectories, but it's the same structure as before I attempted to upgrade -- the various "bits" of the date module are separated out for that one. The .info files are right under modules/date and modules/webform and show the most recent version.
I'm still completely stumped...
look in the drupal modules
look in the drupal modules directory and be sure you did not accidentally put the old code there (done that)
look in the system table of the database to see what path is provided for the date module. It may surprise you.
---------------------
"He's said to be outspoken, but nobody's actually seen anyone do it"
Well, after I figured out
Well, after I figured out what table to look in -- as I mentioned, this is my first time using Drupal, so I don't really know where anything is :-) I found
/modules/date/date_api.module
/modules/date/date/date.module
etc.
Unless I'm egregiously stupid and don't understand directory paths, this matches the directory structure I have:
http://www.virtualrevolution.net/zbin/date_files.png
You'll have to take my word on the fact that those folders (date, date_php4, etc.) don't have subfolders. I assure you they don't.
And as I mentioned I've deleted and uploaded the files about 6 times now. I got the files from the tar.gz linked from each module's page. I've actually downloaded each package 3 separate times just to make sure it was the right version. I was painstakingly careful about which folder I uploaded. So unless the wrong version of files were packaged in the module downloads with the new .info, the files uploaded are the "new" version, not the "old" version. You see, I've checked the .info files in each of the folders, because that's the only one I know of that states the version (based on my reading dozens of threads on this very website, because, as I mentioned, I don't know much about Drupal since this is my first time using it):
http://www.virtualrevolution.net/zbin/date_infos.png
Basically all the right files are in the right place with the right version numbers, but the update is not showing in either the update module (it continues to notify me that I need to update) nor on the Drupal modules page. I am happy to attempt a *different* process, whether it's manual or not, but I feel redoing the same thing I've done 10 times already would be fruitless.
What I would like is information about a different process. A way to find out what actions update.php is supposed to run on the database/files/whatever and do them myself, then manually change the version number.
Or if there's some Drupal specific something I've missed. I'm a new user, it's certainly possible.
But I have used FTP before. I swear to God that I have checked all the "little common easy to overlook" mistakes like uploading to the wrong folder because the file unzipped 2 levels deep, or uploading the old folder instead of the new one. Those are not, to the best of my ability to determine, the problem. For example, yes, I've cleared all the caches in Drupal and my browser. Several times. And at this point the site's been sitting in maintenance mode for 2 weeks while I try to find out how to manually update a module.
Isn't there a file somewhere that contains batch instructions which update.php uses to do the updates? Where can I find that? And is there anything to look out for about it? That's really all I want.
Oh yeah, same problem
Seems every time I go to update modules or the core or whatever, something goes wrong. Every time.
My FCKeditor upgrade went fine, but just like you, the webform update didn't "take". I followed the directions in INSTALL.txt, which basically just said to put the new files where the old files were and run update.php. Did that a couple of times and each time got the "updating 0 of 0" message. Hmm. Then I went back and tried disabling webform and reran update.php. Same message.
I got the idea from your post to choose the update manually from the list of updates. After I found the version (6205, it's in webform.install) I chose that and ran the update again.
This time I got "updating 1 of 1" and a message that all sorts of things happened. Woohoo! Problem solved.
Nope. Just looked at the available updates page and it says I'm still on version 6.X-2.7.
Any ideas?
Thnx!
veg
Same here
I chased my tail with this one today for about 4 hours.
I made module updates and cleared my cache on my local dev install, and all was good. When I put my new module files up on staging, the changes were not being noticed by Drupal. Cleared cache many times, both through Admin menu and admin > settings > performance. Put site in maintenance mode, cleared cache, disabled/enabled module, added "version" to .info and iterated it, hand-edited .module file on staging... All to no avail.
Fortunately for me, it was a module I had created. I ended up creating a new module with my changes and disabling the old module. I know this is not going to work for everyone.
Grrr. Any ideas out there?
did you delete old module directory?
Did you delete the old module directory?
It tripped me up one day when instead of deleting the old webform directory before extracting the new webform.tar.gz, I just renamed it (webform-1).
This was a big mistake! Drupal was looking at sites/all/modules/webform-1 as well as sites/all/modules/webform so no wonder it got confused.
Lucy C