By Lakeside on

Just upgraded multisites from 6.0 to 6.22. Most of the sites show that the core files are 6.22, but several sites say that the core files need to be updated to 6.22. However, at the top of the status report it does show 6.22.

The issue appears only on the sites that use the aggregator module. When the aggregator module is deactivated the status report shows everything is up to date, but reactivating the module brings back the message that the core files need to be updated.

Tried running a cron, but the status report still shows that the core files need to be updated.

Anyone else having this problem? More to the point, anyone figure out how to resolve it?

⋅ Categories: Drupal 6.x

Comments

adeb’s picture

adeb commented

But it only happens on my production server, not on the test/dev server. Also, even status report tells me I'm still running 6.20.
Still investigating.

adeb’s picture

adeb commented

Ok, problem solved. It was a misplaced core directory inside /sites/all/modules (/sites/all/modules/drupal-6.20/) Probably happened during a previous update moving all updated modules including core by ftp to /sites/all/modules dir.

Lakeside’s picture

Lakeside commented

Looks like in my case it is the aggregator module, since those are the only sites that have the problem. The Status Report on all of the other sites report as expected.

Thought the theme might have something to do with it, but get the same results with all themes.

Also, when the aggregator module is removed the problem also goes away. Don't know why a module would effect the Status Report in such a way.

jahwe2000’s picture

jahwe2000 commented

Hello,

I had the same problem - how did you get rid of the folder? When I deleted it, I got plenty of errors with undefined functions. Somehow the module search paths were messed up.

Now I have replaced the "inner" core directory with a current one, but I don't want to update two core dirs with every update ;-)

kind regards,
Philip

Lakeside’s picture

Lakeside commented

Adeb's post got me to thinking about the one module moved from the core's module folder to the sites/module folder...the aggregator module. The reason was that the aggregator module (as packaaged) showed some unwanted characters.

Copied the aggregrator module to replace the one in the sites/module folder. It appears to have solved the problem.