Drupal 6.13 Upgrade just ruined my website !!!
ramones79 - July 2, 2009 - 13:19
Drupal 6.13 Security Update just ruined my website. I don't know why.
I uploaded the new files, overwriting the old ones. When I tried to access my site to run the update.php - it gives me some parse error regarding ImageCache /as far as I can remember/ and something about line 161...
Why do you release stable releases to the public, which are untested?
:(
I had bad feeling about that, something was telling me not to do it, I should have listened to my inner 'voice' ...
Error message
Can you please retry the update and copy & paste the error message here?
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.
I already get back to 6.12
I already get back to 6.12 from the backup before the upgrade. Now its 6.12 and working perfect.
Anyway, if it is important for fixing this issue I can re-upgrade - check the error and report it here and then again revert to 6.12 :)
Do you want me to do that, please confirm ?
Yes please. You may want to
Yes please. You may want to upgrade a test site (copy of production) rather than the production site itself.
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.
Ok. It's a production-ready
Ok.
It's a production-ready site, not yet deployed (it is on a real web server, but a testing/developer one, not the customer's so I will give it a try now)
Should I really disable all
Should I really disable all non-core modules as stated in UPGRADE.TXT ?
The first time, when I got
The first time, when I got the error message I was making a quick upgrade - i.e. just backup, replaced my installed files with the ones from the 6.13 version package and tried to run the update.php
This time I followed very strictly the instructions from UPGRADE.TXT file.
Here is a summary to what happened:
During the update.php step (first run) of the upgrade there appeared the following message:
The following queries were executed
system module
Update #6051
* ALTER TABLE {users} ADD `signature_format` SMALLINT NOT NULL DEFAULT 0
Could be my mistake, because I forgot that I use PHP 5 (enabled with .htaccess) and I overwrited it during the upgrade. After I turned again PHP 5 and then re-run update.php - no problems reported from the system.
Besides this - no problems at all.
The site appears to function normally and the available updates page says my core is 6.13. Horaay :)
Anyway I'm experiencing some settings lost (for example I had disabled the "submited by.." but now it appears again ?). And I had a video clip on my front page with SWF Tools plus FlowPlayer 3. Now the video does not appear.
Custom content types and Views seem to work properly for now.
I will post more info if I encounter other problems.
By the way I will highly
EDIT: I was able to get the embeded video back, I just forgot to enable a module.
By the way I will highly appreciate if you advise me which version to use for the production site - 6.12 (the original backup) or the upgraded 6.13?
Should I expect to receive any problems with 6.13?
6.12 or 6.13?
Dear Mr ramones79,
what do you suggest, ramones79?
Should I update to 6.13?
I'm a very green greenhorn on IT and on Drupal. Learning till couple of weeks.
Only "test" content & "test" users. :-)
Is there any advantage for me to use the upgrade now?
I think I can wait until it will become hopefully a website for my school.
(I'm a teacher.)
Best regards
Luca
Leipzig, Germany
Same error - site ok...
I got the same error but it didn't seem to break my site. I ran update.php again (after re-enabling my add-on modules) and no error the second time. For the record here are the error reports I got:
----------
Drupal Database Update.php
The following queries were executed
system module
Update #6051
* ALTER TABLE {users} ADD `signature_format` SMALLINT NOT NULL DEFAULT 0
* UPDATE {users} SET signature_format = 1
----------
Error Log
Home › Administer › Reports › Details
Type: PHP
Message: array_pop() [function.array-pop]: The argument should be an array in /home/content/a/b/c/username/html/update.php on line 314.
Severity: error
----------
There don't seem to be any problems with my site, but will report back if I discover any (hopefully not!).