By JoOngle on

I've copied my modules / scripts and other files over to my old 6.14 installation...
And ran mysite/update.php

But it keeps bugging me of not being 6.15, but 6.14.

What is wrong?

⋅ Categories: Drupal 6.x

Comments

drupaul.z’s picture

drupaul.z commented

Did you upload includes directory?
clear cache.

JoOngle’s picture

JoOngle commented

Yes, the Includes directory was uploaded.

Tried "Clear Cached data" under Performance.

No difference.

Elteto’s picture

Elteto commented

Did you run update.php?

JoOngle’s picture

JoOngle commented

Yes of course.

exile_ch’s picture

exile_ch commented

Hy there, got the same strange behavior.

Actually i'm using a PHP Actionhandler in .htaccess, but even with the new .htaccess, the upgrade is not registered.

only difference, i'm trying to upgrade from 6.13 to 6.15.

pau1y’s picture

pau1y commented

I had the same problem but then realised that I had a folder called drupal-6.14 in sites/all/modules. I must have copied it here by mistake when I updated from 6.13 to 6.14. I must have (without realising) been running 6.14 from this location rather than from the site root. So, when I updated to 6.15 at the site root, the 6.14 version at sites/all/modules didn't see it. To remedy this, I (1) used phpMyAdmin to replace the string "sites/all/modules/drupal-6.14/modules" with the string "modules" in the DB and (2) deleted the sites/all/modules/drupal-6.14 folder. Now it's fine.

ronline’s picture

ronline commented

Got the same problem.
Includes directory uploaded, Cached data cleared, update.php ran all root files has been replaced with Drupal 6.15.
When I go to update reports Drupal core is still showing as 6.14 and asking for the security update.
I do have drupal-6.14 in sites/default/modules, when I take it off the I get WSOD.
Including drupal-6.15 to sites/default/modules doesn’t change anything.
@pau1y Could you pls mention in what DB table we have to replace "sites/all/modules/drupal-6.14/modules" with the string "modules".
Thx

pau1y’s picture

pau1y commented

Hi lamachine_fr,

DB tables "menu_router" (field="file") and "system" (field="filename"). The SQL I used was:

update menu_router set file = replace(file, "sites/all/modules/drupal-6.14/modules", "modules");
update system set filename = replace(filename, "sites/all/modules/drupal-6.14/modules", "modules");

Only after this did I proceed to delete the "sites/all/modules/drupal-6.14/modules" folder. Also, I switched to the garland theme before doing all this. Hope this helps.

ronline’s picture

ronline commented

Thx Pauly the SQL cleaning fixe the issue.

arton’s picture

arton commented

I'm having the same problem, upgrading from 6.14 to 6.15.

I did everything normally, replacing all files but the "sites" folder, going to upgrade.php, tried clearing cached data, retried multiple times. The upgrades page still shows the current version as 6.14 and is asking me to upgrade.

Update

I found out why this was happening with my site.

Somehow, a drupal-6.14 folder got into my sites/default/modules folder with the rest of my modules (Maybe it was in the folder of modules I had put together to use for this project). When I noticed it, I removed it, which made my site stop functioning completely. Apparently somehow drupal decides to use the system modules from a complete drupal folder nested inside a module folder (might be something to fix?).

Anyway, to repair the damage, I deleted the drupal-6.14 folder from the modules folder, opened up the database, found the module paths inside the "system" table, deleted the "sites/default/modules/drupal-6.14/" part of all of the required paths, and then ran the update.php file. That seems to have repaired the site and made the 6.15 update be recognized.

Maybe that will help someone else with such a bizarre problem.

sfks’s picture

sfks commented

A bit strange that we all, accidentally, put "drupal-6.14" into sites/all/modules, isn't it?

Thanks for the work around.