By vacilando on

I have a weird access denied 403 problem on one of my sites. See http://www.sententiae.org/ Only happens with anonymous access, and only for one content type (page). I'm a seasoned user but here I have no clue.. nodeaccess is off, taxonomy access is off, anonymous are allowed to see nodes, does not depend whether cache is off or on... any ideas, anybody? On D5.2.

⋅ Categories: Drupal 5.x

Comments

yelvington’s picture

yelvington commented

Open your admin/user/access page and SAVE it without changing anything. If the problem goes away, you've stumbled across this mysterious bug. My site periodically denies anonymous access to blog entries, and despite upgrades and turning on/off various contrib modules I have not found the cause. I suspect the problem is triggered by heavy load and out-of-memory conditions, but I cannot figure out how it works, as the node access table does not appear to be buggered up.

vacilando’s picture

vacilando commented

Thanks, but that did not resolve the issue. This is very worrying..

I am particularly intrigued why just one content type is affected..

—
Vacilando services | blog @vacilandois

Quint’s picture

Quint commented

what's your default page set to? Is it a 'view' or something that anon doesn't have rights to?

I looked at your site. ...org/node works.

vacilando’s picture

vacilando commented

It's set to 'welcome' which is an alias for http://www.sententiae.org/node/130424 ... but trying this link on its own gives the same error!

The content type for 'welcome' is plain old 'page' to which anons get access simply by checking their box in access control for node module at 'access content' ... there's nothing else, right?

I tried to re-save this page as well; no improvement.

The only 'unusual' thing about this page is that it has allowed php content. But I don't see why would that lead to 403 error...

Gosh, what can there be that makes Drupal think that anon does not have access to this page?

Incredible is that there is another content type 'page', also with php content in it, that gets displayed to the anon! http://www.sententiae.org/lastorname

—
Vacilando services | blog @vacilandois

Quint’s picture

Quint commented

create another page like that one
see if that works as the default page
then create an alias for the page and make that the default and see if that works

is the page 'published'?

you might have duplicate names or something else.

geojaz’s picture

geojaz commented

What does your PHP code do? Is there any chance that you're playing with $user or anything else that might muck it up?

Or am I misunderstanding and you just allow PHP code in the page but this one doesn't have any... Would you mind pasting your code if there is any?

vacilando’s picture

vacilando commented

Thanks to Pavan Keshavamurthy and Cog Rusty's idea here ... Probably Nodeaccess module, which I had switched off, left some traces that caused this, but rebuild permissions at /admin/content/node-settings helped instantly. Wow!

Tomas

—
Vacilando services | blog @vacilandois

stubb’s picture

stubb commented

I was having exactly the same problem. I tried some access control modules (also nodeaccess) and when disabled them anonymous users couldn't see my page. I couldn't have imagined there is this magic "Rebuild permissions" button if I haven't read this post. However it solved my problem so thx!

sennesaelium’s picture

sennesaelium commented

can I hug and kis you? This was the solution to mp problem, thx!!

freatida’s picture

freatida commented

Had the same problem, fixed by resetting permissions.
My problem was probably caused by disabling Nodeaccess too.
Thanks!