I completed the installation of the update from 7.12 to 7.14. Ran update.php. Everything is working normal except the reminder message box continues to display as if I still need to update. "There is a security update available for your version of Drupal. To ensure the security of your server, you should update immediately! See the available updates page for more information and to install your missing updates."

Also in the admin/reports/updates/update page, it too indicates that the update is available rather than being cleared from the update que.

How can I clear the message and have the drupal core recognize the update to 7.14?

A link to an image of the message-error: http://malibumarlin.com/images/drupal-7.14-message-error-update.jpg

CommentFileSizeAuthor
#4 Screenshot from 2012-05-13 14:48:20.png110.42 KBprogone

Comments

tobbetobbe’s picture

tobbetobbe commented

Tried to delete my comment because I realised I didn´t have the same problem. I was having two identical installations going, updated one of them continued working on the other. Basically, ignore this comment.

mr.marlin’s picture

mr.marlin commented

The message-error window goes away after the http://localhost/update.php script is run. However, it reappears after visiting the http://localhost/admin/appearance/update page.

So to clear the message yet again, I have to run the update.php script.

progone’s picture

progone commented

I can confirm this error exist too.
Only local images are allowed.

progone’s picture

progone commented
StatusFileSize
new Screenshot from 2012-05-13 14:48:20.png110.42 KB

I can confirm this error exist too.

mr.marlin’s picture

mr.marlin commented

A serindipitous result. Since the error could not be solved, I chose to just live with it. However, as time passed, the entire installation became more and more error prone, views would no longer display properly, views slideshow quit working, all kinds of issues. So I rolled back my site and database to 7.12 from a backup which was from the day before updating to 7.14. Thank goodness for back ups!

No loss of work, and the site was back to it's good self again. I added some new modules, and ran the database update. Well, the 7.14 updates were executed in that update. Automatically I must add. You know how it had to be done manually upon the initial release? I didn't really notice it until I went back in to the Administration/Modules and saw that all of the core modules were now showing version 7.14. When I initially ran the update to 7.14, the core modules did not update to 7.14. They indicated that the were 7.12.

So in a nutshell, the update to 7.14 is now automatic?, and the core module version shows 7.14 - as they should. I do not have the error message. But do have a few module issues, but suspect that as time passes, the modules will update to adapt to the new core update.

However, I will be more cautious about updating. Glad I took the time to make backups of my site and database at key milestones, otherwise I would be up the creek without a paddle.

josephsergio’s picture

josephsergio commented
Priority: Normal » Critical

I tried updating once already and had lost my entire site. Can someone help me (step by step) or just give me a brief description how I go about updating my site. I am using drupal commerce and did a commerce kickstart drupal install - not sure if that matters at all. Can someone please provide me with some info?

Thank you

swentel’s picture

swentel commented
Priority: Critical » Normal

Support requests are neither major nor critical.

You can read (briefly) about the update manager at http://drupal.org/documentation/modules/update

There are more pages on d.o re: upgrade/updating modules, but haven't a direct link for that.

swentel’s picture

swentel commented
Issue summary: View changes

included a link to an image of the message error displayed after the update from 7.12 to 7.14 was completed without incident.

Version: 7.14 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.