Why has 6.x-3.0 come up as unsupported in the list of Available Updates? Is this related to the mistaken release of 6.x-4.x, or is there an actual security problem with 6.x-3.0 which means we should all move across to 6.x-5.0-RC ASAP? I generally try to avoid moving to pre-released versions of modules, but if there is an actual security problem with 6.x-3 I would do so without hesitation.

Comments

todd nienkerk’s picture

todd nienkerk commented
Status: Active » Fixed

James: This is unrelated to the 6.x-4.x release, and is not entirely a security issue (though the 6.x-5.x version is more secure).

If you do not want to switch to a release candidate, you can safely wait until 6.x-5.x is fully released. I'm marking 6.x-3.x unsupported because the module has been completely rewritten since ownership changed, and after nearly a year of working on 6.x-5.x, we need to encourage people to move.

jamesoakley’s picture

jamesoakley
Primary language English
Location North Yorkshire, UK
commented

Makes sense: Thanks

jamesoakley’s picture

jamesoakley
Primary language English
Location North Yorkshire, UK
commented

6.x-3.0 is back. It seems to alternately be unsupported and then supported again!

Status: Fixed » Closed (fixed)

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