I'm ready to cry here... I thought I had tested this module a while back and *thought* that is was working.

It is imperatively critical for my business that specific content is not available between customers (authenicated users) and business customers (3 different role types between selective plans)

I guess I just took it for granted that this module worked as I had more issues with book and event populating multiple outputs of same pieces of content because of implementation of this module. But for all node types: page, blog, book page, event, story, forum topic, survey... it does not work for roles other than anonymous/authenicated roles base on core system

I'll log into users who are specific to which content they are able to view and they each and ever one can see it all.

I went to http://cvs.drupal.org to see if any new updates or changes between cvs/4.5 made a difference. I applied and uploaded all downloads from there and all produced for me the same results - full viewability to all content for all users. Admin/settings show that this module is enabled and fully working.

The only thing portion of this I see doing its job is where anonymous users come into play. THEN the content is hidden appropriately!

Is it something I'm doing?

Comments

Torenware’s picture

Torenware commented

I'd be curious how this works out. I've been debugging a problem Events List Mulitple Times For Anonymous User, and it looks like it's a flavor of this issue reported here.

I have some SQL as generated that may shed light on the problem. Check out the link above.

Regards,
Rob
Torenware Networks

ankur’s picture

ankur commented

Refreshing for investigation during 4.5 -> 4.6 port.
-Ankur

ankur’s picture

ankur commented

Hey Torenware,

I checked out the SQL at the link you posted above and noticed 2 things:

The block query (and any query whose intention is to list nodes) is supposed to do a SELECT DISTINCT(n.nid) when being used with table node_access. This is a problem with the queries in the event module for 4.5.

The event.module for 4.6 is NOT a port of the event module for 4.5, but a completely new event module that will have an database upgrade path to port old event data into the new event system. My advice is to see if this problem still occurs with the new event module.

Also, the new query rewriting functions in Drupal 4.6 (if called, as they should be for certain types of queries) insert the DISTINCT() into the query for the programmer. So, any queries that are written for the purpose of listing nodes should automatically make sure that the DISTINCT() shows up in the query, meaning that every nid (node ID) will be returned only once.

-Ankur