Posted by rotnme on June 20, 2011 at 3:16am
What am I missing. It should be a simple update from 6.20 to 6.22. However, I have tried numerous times via ftp after following all the normal procedures. After I run update.php, and put everything back online, etc, I check available updates and it is still telling me I have 6.20 installed and there are updates available. I'm confused....... What am I not doing?
Comments
problems going from 6.19 to 6.22
hi,
I have the same problem, from version 6.19 to 6.22.
I tried locally with EasyPHP.
Just a feedbackI went from
Just a feedback
I updated from 6.17 to 6.22 using drush in bluehost with a multisite setup with no apparent issues. I'm keeping an eye on it.
Hitch? What hitch?
I've performed at least 30 6.19/20 site updates to 6.22 without a hitch.
Without specifics, (namely, environment, modules and error output) this is thread too ambiguous to be productive.
Still have not resolved it on
Still have not resolved it on my end. Obviously we here are not the only ones. Found this. http://drupal.org/node/1174896
Remains ambiguous
Mathematically, in world of 6 billion people and countless drupal installations, the possibilities are limitless. I'm not doubting anyone having difficulty with an upgrade, just that it's not consistently true for everyone. Please re-read my second sentence. Without that, there's nothing for us to go on.
Remains ambiguous
so to is the possibility such as double posts on groups sites.
This problem still exists.
This problem still exists. The update was performed via ftp with all non-core modules disabled and in maintenance mode. There is no drupal-6.20 folder in /sites/all/modules, no references to this folder in the System table. Also, /modules/system/system.module reports the version is 6.22. There are no related log entries, just the update warning.
Related link.
Hmm, I wonder if your system
Hmm, I wonder if your system table is pointing to some strange location for the system module..
Try running this query in your SQL admin tool:
SELECT filename FROMdatabasename.systemwhere name like '%system%';Where "databasename" is the name of your Drupal Database (a.k.a. Catalog or Scheme). See settings.php $db_url to find this if you don't know what it is. The name with be the last work after the last /.
This will return the path relative to your index.php file to the system.module. It should be modules/system/system.module
If this correct, it might be that there is an alias statement in your apache config redirecting urls to other places (e.g. /var/share/...) or maybe some custom rewrite rules in your .htaccess file that are doing something similar.
The query shows the path to
The query shows the path to system.module is correct, modules/system/system.module. I checked .htaccess on Drupal's root but found nothing suspicious. In fact, this is the same .htaccess packaged with the 6.22 release. As far as I can tell, all of the files were overwritten correctly (6.20 -> 6.22), the system is merely reporting the version is old.
Is it possible there is an apache alias when the system was working correctly before the update and with previous updates? Unfortunately, I don't have shell access to this server.
Back to basics...
OK, to just check some basics stuff that you probably have done...
You have gone admin->build
You have run the "Available Updates" report (admin->reports->Available Updates) or run cron.php? These both are involved in setting / resetting the "Updates available" messages.
The upgraded install does have the Update Status module enabled? The message might be from when it was enabled but isn't cleared because the modules is now disabled.
Another bit of useful info/checking is to run the same query as above but replace "filename" with "info". The output will be a long string starting with a:. Look thru this for s:7:"version"; right after this will be the module version that Drupal thinks is installed (e.g. s4:"6.22" ) = Version 6.22.
Do this AFTER visiting the modules page since that updates this info.
If this is not 6.22, then chances are your "document root" may not be what you think it is. There may be some alias magic happening in the config files you don't have access to.
Wow
CG, that's an excellent basic overview for troubleshooting. I'm curious to know if that helps.
re:back to basics
I ran following query:
"SELECT info FROM databasename.system WHERE filename LIKE '%system%' "
Output:
a:10:{s:4:"name";s:6:"System";s:11:"description";s:54:"Handles general site configuration for administrators.";s:7:"package";s:15:"Core - required";s:7:"version";s:7:"6.x-dev";s:4:"core";s:3:"6.x";s:7:"project";s:6:"drupal";s:9:"datestamp"; ..... }