Closed (duplicate)
Project:
Drupal core
Version:
7.x-dev
Component:
node.module
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Aug 2008 at 15:03 UTC
Updated:
10 Oct 2008 at 03:54 UTC
Jump to comment: Most recent file
Comments
Comment #1
joachim commentedHello from the testing pancake session!
Here's a patch with a test.
But it fails.
We think this is because of a bug in Drupal core, as testing this manually with a user with 'administer nodes' permission gives us a 403 on the autocomplete field.
We're on 7.x-dev so could someone give this a try on CVS HEAD, and if it's still not working file a bug on core?
Here's the patch with the test.
Comment #2
damien tournoud commentedYou will need the 'access user profiles' permission to use the user autocomplete.
Comment #3
dries commentedIt seems like you need to have the 'access user profiles' permission:
Comment #4
catchExisting bug report with patch is here: #284887: Check for access to autocomplete paths during form building
Comment #5
catchActually that's a different but somewhat related issue however the appoach taken there - to disable autocomplete if the permission isn't available, seems like a sane approach, better than a 403 when you're typing at least. I'm hijacking this for the core bug so we can put test and fix in together. I can think of certain situations where these permissions wouldn't be given together, so makes sense to account for it.
Comment #6
dave reidI posted a patch and a test to fix the bigger problem in #284887: Check for access to autocomplete paths during form building
Comment #7
dave reidArg...did not mean to change title at all...
Comment #8
dave reidTest for user autocomplete is in the patch with #284887: Check for access to autocomplete paths during form building. Marking this as a duplicate.