Posted by ghmercado on December 28, 2008 at 7:36am
| Project: | Update Status |
| Version: | 5.x-2.x-dev |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Issue Summary
Hi I have four different d5 sites, and have been using drupal since 4.3. Am saying this to say I know how to install and update drupal properly.
Despite this and after many attempts to update my 5.12 to 5.14, my site still insists I am using 5.12. Normally I just set filezilla to write over everything and that's usually enough to upgrade, but since that didn't work I went so far as:
- backup /files and /sites folders
- delete everything.
- upload 5.14
- upload /files and /sites folders
- after that still reported 5.12, I wrote over the update.status module even though its the same version at /sites/modules, still no go
here is screencap of /admin/logs/status. Notice drupal version says it's 5.14 but there's still a 'drupal core update status - not secure' warning, saying 5.14 is available.
Help me drupal folks. You're my only hope.
| Attachment | Size |
|---|---|
| dec282008_drupal_not_updating.png | 50.15 KB |
Comments
#1
correct link to .png file should be:
http://www.lefthandedlayup.com/wp-content/uploads/2008/12/dec282008_drup... (otherwise see attached).
Also, all my drupal sites are on hostgator.com, so I am trying to install it on a different host to see if the issue has to do with that.
#2
Judging from the screen print the update module is showing behavior that shouldn't be possible and I believe that qualifies as a bug.
No idea how it happened though.
- Arie
#3
i just dunno what else to do at this point other than to start all over again using 5.14, which is a hell of a waste of time considering the work I'd already done when it was still 5.12. Attached is a screencap of the modules i used in case that's important.
#4
- You're talking about http://drupal.org/project/update_status from D5 contrib, right? If so, this would be an issue for a completely separate issue queue. The core issue queue's "update system" component is about database updates, update.php, etc. If you were using D6 or D7 core and running update.module (what update_status turned into), you'd want to use the "update.module" component. Anyway, I hadn't seen this request until today when I happened to scan through the "update system" component looking for misclassified issues...
- None of your screenshots work except the one you attached at comment #3, which doesn't display the bug itself.
- Sounds a lot like #184418: update(_status) results stale for up to 6 hours. Did the problem resolve itself the next day?