Using 6.14 and newest Views. There's been a lot of discussion on similar topics. I've noticed that using a simple directory listing I get this issue, expect for admins. I do have access to the /modules directory, but I am not a programmer, more like a "configurer".

This is a new site so it does not have a large user base. An authenticated user picks a number of taxonomies in 5 vocabulary groups and most can be multiple choice. For example, vocabularies can be: Industries, Geography, Functions, etc. and the user can pick multiple Industries, Geographies and Functions taxonomies within those vocabularies. Let's say they pick 3 of each. When we get a simple directory listing, the count is correct, but clicking on the taxonomy results in that user being displayed 9 times. For example if one Industry was Chemicals, one would first click on Industry to get a list of possible Industries and then the count for each industry type would be listed. If one was to click on Chemicals then this use would be displayed 9 times even though they only chose Chemicals one time. BUT, if I go in as user1 or under a separate administrator username, everything is fine. I'm guessing something with permission choices is wrong. I have not touched the Views module to create any special Views yet.

Modules related to permissions that may be at fault are: directory, forum_access, menu_access, node_access, tac_lite, taxonomy_role, and views.

We ultimately want different user types to be able to access different menus and nodes/pages, but that will be another topic. For now we are trying to get this piece working right. Since it works right for admins it seems like there is some kind of setting/selection that is wrong for authenticated users. Any insight would be helpful.

TIA,
Tom

Comments

fsg’s picture

Time heals all wounds? Or, if one waits long enough, one will figure it out for themselves?

I have a number of modules so I knew it would take some time to check this. I focused on those that should be related to the problem as noted in the original post.

I figured out the issue was in the User Permission for the Node Module. By selecting the checkbox for "administer nodes", this problem is resolved. I am concerned that this allows other users to edit someone else's nodes.

Posting so others with the same setting issue can have solace.

Tom