I have a form that uses a view with an autocomplete search field. When I search it works as expected and shows my users when I select from the autocomplete. If I click on the find button with an empty query, it shows this 

Access forbidden!

You don't have permission to access the requested object. It is either read-protected or not readable by the server.

If you think this is a server error, please contact the webmaster.
Error 403
localhost
06/10/09 12:19:05
Apache/2.2.9 (Win32) DAV/2 mod_ssl/2.2.9 OpenSSL/0.9.8i mod_autoindex_color PHP/5.2.6

Comments

danielb’s picture

danielb commented

A bug with the views queries (in another issue) may be leading to this problem - but I've never seen this exact error. Might be worth googling to see if there is any info you can find. Chances are it is the bung query causing this.

gmclelland’s picture

gmclelland commented

you can also see this behavior if you click on one of the finder results and view the node then use the browser's back button to go back to the finder page and you will see the error.

I'm running XAMPP on Vista.

Not sure this helps, but a least it's documented.

danielb’s picture

danielb commented
Status: Active » Postponed (maintainer needs more info)

Do you still have this problem with beta2? I can't get a 403 in any situation like you described. Have you tried this with any other forms such as the built in search module?

gmclelland’s picture

gmclelland commented

Unfortunately, I still have this problem. It happens only on the user finder and views finder. Both of which are involving users. Could the realname module or content profile module have any affect on this? The node finder works fine. Regular Search Module searches fine.

Hope that helps,

-Glenn

gmclelland’s picture

gmclelland commented

FYI... It's not the realname module. I tested on a different site that doesn't use the realname module.

danielb’s picture

danielb commented
Component: Miscellaneous » Finder Views
danielb’s picture

danielb commented

I was wondering if the change I made in beta3 has made this problem go away by proxy?

gmclelland’s picture

gmclelland commented

No, I still have the same problem with beta3.

danielb’s picture

danielb commented

OK I'm sorry about this. Hopefully someone with the same problem as you might be able to shed some more light on it or supply a patch, as I cannot figure it out.

murokoma’s picture

murokoma commented

Hi there,

don't know if it was the exact same issue, but I also got 403 (popup) messages als a "test-user" when using AHAH search.
I then disabled AHAH and got "no access" errors; this lead me to the idea that I probably didn't set "access" permissions for regular users.

And - yepp, that was the case.

After I changed "view" permissions for the finder modlule in admin/user/permissions (well, it's basically called "use" not "view", but anyway), everything works fine.

Hope it helps.

Best regards,
Robert

danielb’s picture

danielb commented

thanks murokoma

danielb’s picture

danielb commented

gmclelland - did you have any luck with this? Did murokoma's post shed any light?

gmclelland’s picture

gmclelland commented

I was testing as an admin user(which should have all permissions) when this happened. I was orginally using XAMPP but recently switched to WAMP, but the problem still didn't go away.

The best thing I could do to prevent the problem was to set the field to required so that a user could simply enter a empty string to show all the search results, but that doesn't prevent the user from clicking their "back" button and getting the 403 error message.

danielb’s picture

danielb commented

You may have to turn the 'hide url args' option on - it's possible your host is spazzing over the way i've done empty field bits in the url - I just can't think of another way to do them.

TaPes’s picture

TaPes commented
Version: 6.x-1.0-beta1 » 6.x-1.5
Status: Postponed (maintainer needs more info) » Active

hi,
i have the same problem.
i use a "views finder" with two "autocomplete elements".
when one of the fields has an empty query, i get the "Access forbidden!" - Error

danielb’s picture

danielb commented
Status: Active » Postponed (maintainer needs more info)

'me too' != new info

TaPes’s picture

TaPes commented
Status: Postponed (maintainer needs more info) » Fixed

ok i found a solution.
you have to use the option "Hide URL arguments on results page".

danielb’s picture

danielb commented
Status: Fixed » Postponed (maintainer needs more info)

stop doing that!!
It is easy to avoid the issue with the url args option, but it doesn't help you if you actually want url args.
I don't know the solution here, but perhaps somebody else does.

danielb’s picture

danielb commented
Status: Postponed (maintainer needs more info) » Fixed

There is now an option to change what the 'empty' value in the URL is. This should be sufficient to work around the problem if your server doesn't like the default.

Status: Fixed » Closed (fixed)

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