Hello,

I have TAC set up and working well on a website. However, I'm noticing some differences in what appears when an anonymous user tries to view controlled content.

Example 1: http://www.svenskaskolanwashingtondc.org/node/132
(Here, anonymous user sees "You are not authorized to access this page.")

Example 2: http://www.svenskaskolanwashingtondc.org/en/forum
(In this case, anonymous viewer just sees a blank page)

Example 3: http://www.svenskaskolanwashingtondc.org/medlemssektion
(This is a taxonomy, and the anonymous user sees "There are currently no posts in this category.")

I'm wondering why there are 3 different messages/results for these cases, and if there is any way to make it consistent. Because it's "members only" content, ideally I'd like each of the above examples to say something like "Access denied. Please log in to view SSFC members content." (or something like that). Otherwise, the first example's message would be fine as well.

Thanks for any advice,

Jim

Comments

jarea’s picture

jarea commented

I was consistently getting a correct 403 page display whenever an anonymous user hit an unauthorized page, but now it is loading the page (taxonomy/term/) with no content and now access denied/403 message. I really need to display the 403 message because it instructs the user to log in to see the expected content.

I have looked everywhere and cannot find any leads on this one.

I will also note that when TAC limits display of content, it does not throw a 403 error to the error logs either. Also, for non TAC generated access violations, 403 page shows up fine and a 403 error is added to the log.

jarea’s picture

jarea commented

Jim,

To your specific questions, is it possible that access for example 2 is controlled by TAC and example 1 is controlled by user permissions. If the answer is yes, then you have the same problem as me. Drupal access control is working correctly and TAC is blocking the content but not throwing a 403 error flag.

As for example 3 - is there content there?

xjm’s picture

xjm
she/her
Primary language English
commented
Category: support » bug
Status: Active » Closed (duplicate)

I believe this is caused by the same bug as in #311649: "Page Not Found" error for all non-accessible term pages; marking duplicate.