I've checked a number of installations and found that the 6.x-3.4 release is not appearing in the available updates page (admin/reports/updates). I'm seeing "Up to date" notations with the 6.x-3.3 version. I don't know why this is the case, but as this is an important module and other security releases from today are appearing - I thought I should at least mention it.

Comments

TallDavid’s picture

Priority: Normal » Critical

Bumping to critical since it affects a security release. After upgrading from FileField 6.x-3.3 to 6.x-3.4 I get the following message in Available Updates:

"Release revoked: Your currently installed release has been revoked, and is no longer available for download. Disabling everything included in this release or upgrading is strongly recommended!"

What is the proper course of action?

  1. Ignore the warning
  2. Revert to 6.x-3.3
  3. Disable FileField and break the site
fitter’s picture

subscribing, same issue as #1

quicksketch’s picture

I have no idea where this error would come from. It's certainly not from FileField or Drupal core. My guess is Acquia Drupal?

mule77’s picture

I've the same problem as #1

the solution suggest in http://drupal.org/node/829856?mode=2&sort=2 is the right solution?

mule77’s picture

I tried this patch (http://drupal.org/files/issues/filefield-missing-argument-filefield-view...) and seems to solve the problem correctly

gillesbailleux’s picture

Also applied patch successfully

Update: the warning disappeared but it did not solve the problem (http://drupal.org/node/829992)

Argus’s picture

subscribing, same issue as #1

edit: curiously enough this only occurs in 2 out of 3 Drupal installations.

bengtan’s picture

I think you will find there are two separate issues which some people are confusing with each other.

One is #829856: warning: Missing argument 2 for filefield_view_access() which has a fix there.

The other issue is this one which, I believe, is due to the release history file for Filefield (http://updates.drupal.org/release-history/filefield/6.x) being temporarily out of date. In this history file, version 6.x-3.4 was momentarily marked as unpublished.

This seems to have been cleared up as the history file now looks correct and up to date.

Other people may have applied the fix for #829856: warning: Missing argument 2 for filefield_view_access() and then this issue fixed itself (by the history file being brought up to date) and came to the mistaken conclustion that these two issues are related.

croryx’s picture

Subscribing. Same problem on a standard Drupal install.

JayNL’s picture

I always hate such replies, but sorry: Subscribing!

scottsawyer’s picture

Priority: Critical » Minor
Status: Active » Fixed

oh, dear lord, I love you ALL. What a fast response! The patch worked like butter on toast.

grndlvl’s picture

Status: Active » Reviewed & tested by the community

Patch from #0 applies w/ a little fuzz but still applies just fine. Works well and I would agree with #8.

Also not sure why this was marked as fixed :/ I checked CVS and fix is not in so I am thinking this was an accident?

Ignore the above comment I seemed to have cross posted myself... Gong o_O However I still think this still was closed on accident. Was meant for #829856: warning: Missing argument 2 for filefield_view_access()

grndlvl’s picture

Priority: Minor » Critical
Status: Fixed » Active
Argus’s picture

Running update.php for a second time solved the problem for me in my 2 remaining Drupal installations.

croryx’s picture

Thanks bengtan/Argus. Another running of update.php fixed it.

pwolanin’s picture

Status: Reviewed & tested by the community » Closed (fixed)

this was some temporary glitch in the update system.