By mcsolas on
I was running 5.2 and patched all the changed files to my install to the 5.3 version.
Pretty sure I made all the right changes, I do it line by line with a file comparison tool.
...
I ran the update and cron .. but it still says that I am running version 5.2.
What do I need to do here to 'finish the update' ..
Comments
Patching isn't the same as
Patching isn't the same as replacing... Did you patch or did you overwrite?
Pobster
.
I patched the files... what would be the difference, if the ones I left alone were unchanged?
update from 5.1 to 5.3 still shows 5.1 in the core modules list
I upgraded according to the upgrade.txt file.
I deleted the old drupal directory and replaced all files. I then copied by in my non-core modules, files, and non-core themes.
when I ran update.php - there was nothing to update.
???
Am I missing something?
Patching files just fixes
Patching files just fixes the security issue, none of the version IDs of your files are updated though... That's why you should upgrade properly - you're essentially just running a 'fixed' version of 5.1.
Update.php only updates database schema and when the database hasn't altered, then there's nothing to update. This latest update isn't a load of bug fixes or anything, it's literally just taping up a newly found security hole... Well okay it's slightly more than that, but it's more code changing than database changing.
Pobster
overwriting worked.
I overwrote most of the files .. and it worked. Im still having trouble understanding how that worked but at least I know now.
My upgrade
I just upgraded 8 sites in less than 10 minutes - some from 5.1 and some from 5.2. No problems at all.
Nancy W.
Drupal Cookbook (for New Drupallers)
Adding Hidden Design or How To notes in your database
NancyDru
update status too
There is also a lag period where the "update status" tool might tell you the wrong information - i.e. that your "5.3 site should be upgraded to 5.2".
In general, the best solution is to follow the full upgrade instructions from the handbook.
--
Knaddisons Denver Life | mmm Chipotle Log
--
Morris Animal Foundation
.
http://drupal.org/upgrade/tutorial-introduction
I will overwrite the files next time... strange but I guess you need to.
----------------------------
www.pacificallsurf.com
Better yet
Delete everything and reload. Oh, and since enabling modules clears the cache, you might do at least one to force Update Status to get new information.
Nancy W.
Drupal Cookbook (for New Drupallers)
Adding Hidden Design or How To notes in your database
NancyDru
5.1 to 5.3?
I managed to screw-up my upgrade from 5.1 to 5.2 last week (by not replacing all files as in the instructions) but site still seems to run OK. If I follow the tutorial is it possible to go straight from 5.1 to 5.3 or should I do 5.2 first?
Tried to set up 'test_site' database but Phpmyadmin refused to upload my SQL file as it was too large....any ideas?
Surely there must be an easier way of upgrading these security issues?
Tom
Yes
Staying within any major release, you should be able to skip interim releases without any trouble. The worst that might happen is that the update.php runs longer.
Upload problem: First, there is no need to upload the contents of any of the "cache_" files, or watchdog. Often deleting those will be adequate to reduce the size. You could also zip/gzip the file before upload. Or, you could ask the host to temporarily raise the upload limit.
Nancy W.
Drupal Cookbook (for New Drupallers)
Adding Hidden Design or How To notes in your database
NancyDru
www.aviceda.org Hi
www.aviceda.org
Hi Nancy,
Have just completed the upgrade to 5.3 on a test-site, followed the instructions to the letter, but when I go to "Status Report" the site still appears to be 5.1 and is telling me to upgrade!
What now?
Tom