On Internet Explorer 7, typing in the DJs field gives a pop-up error dialog, saying 'HTTP error 403' and the url [base site]/user/autocomplete/.
It works fine on Firefox and IE6.
On Internet Explorer 7, typing in the DJs field gives a pop-up error dialog, saying 'HTTP error 403' and the url [base site]/user/autocomplete/.
It works fine on Firefox and IE6.
Comments
Comment #1
joachim commentedThis isn't just Station.module -- the user autocomplete in the node authoring options causes the same error.
Comment #2
joachim commentedPossibly a duplicate of http://drupal.org/node/117151
Comment #3
drewish commenteddoes drupal's core user auto-complete cause problems?
Comment #4
joachim commentedI assume autocomplete in the node authoring options is from core -- is it?
Comment #5
drewish commentedyeah, it is. also does it make a difference what you type? i know starting with a space used to cause errors.
Comment #6
joachim commentedPeople were trying to type their user names.
Error came up on every letter.
I'm applying the patch from http://drupal.org/node/117151, will report back as soon as I can get someone to try it with IE7.
Comment #7
bonobo commentedIs this issue still live? Both this issue and the related issue (http://drupal.org/node/117151) have been silent for a couple months --
Setting priority to normal; please re-elevate if this issue is still outstanding.
Comment #8
joachim commentedThe patch from http://drupal.org/node/117151 fixed the problem, but it doesn't seem to have been committed yet.
Comment #9
chrisfive commentedIn my case, I noticed that the occurrence is system-dependent.
Bug occurs using:
No problems with:
I've tried the patch but it doesn't solve the problem for Ubuntu. Any ideas?
Comment #10
fluke777 commentedHi chrisfive and all.
I know that this thread is dead for some time and this is not specifically related to this bug but nevertheless. I've just run into this behavior on my brand new ubuntu Dapper server. After playing a little bit I have noticed that I don't have trouble searching for user while I am logged in as an administrator. Actually to be able to access site/user/autocomplete a user has to be given authorization to access user accounts, which isn't obvious at the first sight. After I have added this authorization to specific role everything is just fine. So maybe it is worth checking your permissions first. I am running 5.1 HTH anyone
Comment #11
sudhaker commentedThere is no such error, if you grant accesses on following item.
Administer >> User management >> Permissions >> user module >> access user profiles
Cheers,
Comment #12
joachim commentedWell that still sounds like a bug -- why should you need to grant access to profiles for username autocomplete to work?
Comment #13
sudhaker commentedGood point! Auto-complete should work regardless. My bad.
Comment #14
Anonymous (not verified) commentedI just stumbled on the same thing in Drupal 6.1. A simple name lookup shouldn't require user profile access. Perhaps it shouldn't be restricted at all for fault tolerance? Or at least get its own little permission like "lookup user name" or so.
Well after thinking a while about it: isn't it a FAPI bug? FAPI should check authorisation on #autocomplete_path fields before querying them, and avoid the ugly 403. A proper authentication warning could be displayed to tell the admin about missing permissions.
Comment #15
dave reidWill be fixed and backported in #284887: Check for access to autocomplete paths during form building. Marking as duplicate.
Comment #16
dpatte commentedI seem to be having a similiar but tempermental problem.
I am using the most recent 6 core
If I try to change 'Authored by' for some nodes I get errors as soon as I type a character.
'An error ocurred in .../user/autocomplete - no error number and nothing appears in my logs
but the results are tempermental
1) On firefox or IE - Acquia Slate theme - when the error occurs, there is no no dropdown box of choices, or sometimes the bottom of the box is truncated at the the beginning of the next form field, or only has the first of a partial list of avaialable options and no scrollbar.
2) On IE - Garland - no error occurs, but usually the dropdown only has partial results and no scrollbar.
This usually happens for the author field, but also sometimes happens for other user/autocomplete fields, and sometimes for location autocomplete fields.