The message advising that a Drupal update is available sometimes is shown 2 or 3 times:

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.
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.

Comments

Version:7.15» 8.x-dev
Issue tags:+needs backport to D7

Moving to D8.

Status:Active» Closed (duplicate)

Version:8.x-dev» 7.x-dev
Status:Closed (duplicate)» Active

So I see from #1428032-19: Default drupal_set_message $repeat to FALSE instead of TRUE (followup) that it isn't committed to D7. The admin messages need to declare the $repeat parameter as FALSE for D7.

Status:Active» Needs review
StatusFileSize
new1.14 KB
PASSED: [[SimpleTest]]: [MySQL] 39,548 pass(es).
[ View ]
new27.2 KB
new31.5 KB

This has bothered me for a while now. Simple fix. Sorry don't know how to write a test for this or if it needs one.

Here are some manual steps to test:

  1. Clean install Drupal
  2. Install a module that has a security update available (I chose entity 7.x-1.0-beta11)
  3. Edit the Article content type Tags field
  4. Try to set a default value a couple times and save the settings, you should have multiple security update notices

I have uploaded a couple screenshots to demonstrate the patch.

Status:Needs review» Reviewed & tested by the community

Looks good to me. As for a test you would need to get the values of the message array and test that there was only one entry for the notification. I don't think it is worth a test at this point, but if there is it would need to be a new issue for D8.

Status:Reviewed & tested by the community» Fixed

Committed to 7.x - thanks! http://drupalcode.org/project/drupal.git/commit/2b86b82

Yeah, I agree, it's probably not worth the effort to write a test for this one.

Automatically closed -- issue fixed for 2 weeks with no activity.