Download & Extend

updates marked as security update do not appear in the update list

Project:Plugin Manager
Version:6.x-1.10
Component:Code
Category:bug report
Priority:critical
Assigned:Unassigned
Status:closed (fixed)
Issue tags:DRUPAL-6--1-11

Issue Summary

Hello,

It seems Plugin Manager does not include a security update in the available updates list.

Anyone else getting this?

Comments

#1

I am also seeing this in 6x-1.9. Other updates work fine, but security updates don't show up.

#2

Version:6.x-2.x-dev» 6.x-1.x-dev
Priority:normal» critical

#3

me too has this issue. 6x-1.10

#4

Me too. I have a webform security update that needs to be run, but it's not showing up in the plugin manager as an available update.

#5

#6

Same here

#7

Me too using the last stable version and drupal 6.14, but I was thinking that this is not a problem, just if there are some security fixes, could be that it need special upgrade, for example to delete files and then reupload or some secial dependencies to read irst to upgrade automatically, for example panels 3 need many details to read first to upgrade from 2.

#8

I've just been doing a search in the plugin manager for the module that needs to be updated, and then installing the new version. It's not as simple as I would like it to be in order for my clients to run their own updates, but it's easier than going to drupal, downloading the new version, unzipping the module, and then uploading the new version.

#9

I would really like to be able to install security updates like any other updates too!

#10

Version:6.x-1.x-dev» 6.x-1.9
Component:User interface» Code
Status:active» needs review

In plugin_manager_admin.inc change line 533

from:   if ($project['status'] == UPDATE_NOT_CURRENT) {

to:    if ($project['status'] == UPDATE_NOT_CURRENT | $project['status'] == UPDATE_NOT_SECURE ) {

Tested and works in 6.x-1.9

#11

Version:6.x-1.9» 6.x-1.10

Sorry, got the version number wrong. Actually tested in 6.x-1.10

#12

Status:needs review» fixed

Thanks DrewMathers! That has just been committed.

#13

Status:fixed» closed (fixed)

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

#14

+1

#15

Will this ever be pushed to the production version? I see the 6.x-dev is not being updated.

#16

Also noticed that updates marked as "Not Supported" are also omitted. If you add another or clause to the above on line 533, it will pick up those updates as well:

if ($project['status'] == UPDATE_NOT_CURRENT | $project['status'] == UPDATE_NOT_SECURE ) | $project['status'] == UPDATE_NOT_SUPPORTED) {

Keep in mind, I don't know if the above is recommended, as the "Not Supported" status is a different animal from the previous 2 statuses.

#17

Status:closed (fixed)» fixed

modctek,

Thanks, I have included your contribution to the fix for #832464: Core update listed

#18

Status:fixed» closed (fixed)

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

nobody click here