I tried to update my site from 6.21 to 6.22. I followed the directions very closely (I've been doing this for almost three years) and everything seemed to work fine.
Old files removed
New Files uploaded
Update ran No errors
Activated modules & Ran Update No errors
I check the logs and nothing there
Ran the Status and received the "Not secure! (version 6.22 available)"

The site seems to be working fine, and I did not see anything in any of the logs.

It seems like the database or something is not getting updated. Any ideas or suggestions would be greatly appreciated.

CommentFileSizeAuthor
#7 Drupal_core_issue.jpg87.02 KBsarav.din33

Comments

Bob4613’s picture

Bob4613 commented
Component: database update system » other

Ok, I'm not sure what is going on, but this is really getting very frustrating. To add to the problem,

I'm also having problem with updating a module "Token" from 1.15 to 1.16. I removed the old version, uploaded the new version and ran update. Everything ran fine with no errors detected, except the module list still shows 1.15 and the status reports an outdated module.

In addition, I have theme that is still showing in the theme list despite the fact I completely removed the folder from the sites/all/themes folder.

Does anyone know what is going on? I'm not even sure where to post this problem now.

rjlhughes’s picture

rjlhughes commented

I'm also having problems upgrading from 6.19 to 6.22. Doing all the right things, I think and still it says security upgrade required. Watching this thread with interest

rjlhughes’s picture

rjlhughes commented

http://drupal.org/node/1001774

suggests it may be an APC cache issue, and even suggests that waiting for the cache to flush may fix the issue

Bob4613’s picture

Bob4613 commented

rjlhughes,

I checked the APC issue with my hosting service and they said do not run APC on their shared servers, so that wold not be the problem.

They did complete a re-install of Drupal 6.22 manually and updated the Drupal database. So the status report reflects the proper software version for the Drupal core.

However, as mentioned above I still have the Token module and theme issue going on. They are looking into that and I'm waiting to see what they say.

LetUsBePrecise’s picture

LetUsBePrecise commented

subscribing

dddave’s picture

dddave commented
Status: Active » Closed (duplicate)

Sounds like: #1001774: Status Issue for Drupal > 6.19

sarav.din33’s picture

sarav.din33 commented
StatusFileSize
new Drupal_core_issue.jpg87.02 KB

@Bob4613,

I faced a similar issue when some of the custom modules’ .info file had the wrong date stamp, Project Name & drupal version.

The custom.info file had the below piece of code(something like that) embedded in it.

; Information added by drupal.org packaging script on 2011-05-25
version = "6.21"
project = "drupal"
datestamp = "1306357015"

The update module mistook such custom modules as part of durpal core project. As the timestamp for these modules were not updated the update status on the Available update page for Drupal core showed the message: “Security update required!”

Please check the Available updates page at http://examplesite/admin/reports/updates/list, to verify if any of your modules are listed below the Drupal core section. See attached image for reference.

If any such custom modules exists, edit .info file to resolve the issue.

I hope this will helps you.

Thanks & Regards
Sarav.

abi2’s picture

abi2 commented

I had this problem and after looking into all the .info files I found a timestamp in the block module.
after deleting it I am back to drupal core 6.22