Users without "administer nodes" permission are not able to "access" all nodes:

Hi,
Have you checked the access content permission? It must solve the problem

There is no way to help with so little information.

Please give more information about the modules you installed (especially those affecting node access), the configuration of your permissions, etc.

If it only affects your own little corner of the world, it cannot be a "critical bug". There are hundreds of thousand Drupal 6 websites in production today, as far as I can tell, you are the only one affected. Let's qualify this as a support request until we know more.

I agree, it's not just Junro's little corner of the world. I had this issue just yesterday and fixed it with the workaround of installing the Node Access module.

Glenn

I see several access control modules in the list above:

ACL
Domain Access
Nodeaccess
Organic groups

... and I might have missed some (less obvious ones). How can you rule out a configuration issue? If one of those modules is configured to prevent all node access by default, it's certain that no user without the "administer node" permission will be able to access the content.

How can you rule out configuration issue so easily?

More information about how those modules are configured, which ones are enabled, etc. could help.

Damien hits the core issue in #11 -- you have multiple access control modules installed -- and, IIRC, Domain Access requires a patch to core to work (or at least it used to -- I haven't evaluated it in about 3-4 months)--

And add Forum Access to the Access Control modules Damien listed --

I suspect that you have multiple access control mechanisms working on some node types.

Your module list is also pretty lengthy, with a slew of dev, rc, and beta versions -- there are many things that could be causing this, and a core bug is pretty low on the list of possibilities.

I'm not sure if it will help, but I'm having an issue that is similar to what has been talked about here ('press editor' role) and here (User Role permission for content management).

In my case, I have an 'editor' role which I want to act only on Stories. Under /admin/user/permissions, I allow 'editor' to perform the actions create/edit/delete any story.

Now I expect that the editor will be able to perform those actions on any Story via the Content Management dashboard (admin/content/node/overview).

Since editor can only act on Stories, I expect that either

a) the editor will only be able to list Stories (the content type drop menu under 'Show only items where... type is:' will be restricted to the Story type), or
b) the editor will be able to search for and list all content, but the 'edit' operation won't appear on content that isn't of type Story and if they try to perform bulk actions (e.g. delete or publish) on content types they have no permissions over (non-stories) they'll be told that isn't allowed.

That is the expected behavior. The actual behavior I see is that without 'administer nodes' permission, when the editor accesses '/admin/content/node/overview' they are told 'You are not authorized to access this page.'

So my question is - is the actual behavior I'm seeing the 'appropriate' or 'correct' behavior (that is, is the Content Management dashboard only designed to work for users with 'administer nodes')?

In case it helps, I'd like to have something like the 'Content Management View' illustrated at the bottom of this article, that only shows content that the editor is allowed to manage.

Thanks!

This issue is not just one person issue. I am having the same issue.

How do I allow a Role to have access Create Content (with includes editing, deleting, and un/publishing) a specific content type AND allow the Role to have access to the Content Management - Content List view. The Role can see Create Content for the type I have selected. But have no way for Role to easy edit all they Created Content. Would have to go found the page with the content in order to edit. Plus what do you do when you have Content that has a view that does not show the Edit option, now user has no way to edit the content. Also, what if they want to create content early but not published it to later. Other then setting Node module - Administrer nodes to yes. They seems to be not other way to allow Role to set the published or non-published. Then with this access set the Role has access to create and edit all Content by all users, not good.

Also, I agree why force to install other module to manager permission when it should be in the system. Don't we have enough module to install and installing more modules cause more issue, php memory use. Sorry I will stop now, just I am trying to limit number module needed and all the php memory use.

Thanks!

I have this same issue and I can't believe in Drupal 6 that this problem even exists.

I created a user role for my client, and I want him to be able to administer the content types I have allowed him access to without ruining all my hard work because he doesn't know what hes doing... but yet the only way to give him that access is to give him access to every node?? that is ridiculous and this is DEFINITELY a critical issue..

I should not have to install a module to fix this problem.

btw - I do not have any access control modules on this site

The last few posters here have apparently significantly different issues. Please do not reconvert into a bug report unless you have a *specific* bug to report.

I think it's pretty safe to say that this issue has been diluted with cross-posts to the point where it is not particularly useful in addressing the original issue, if indeed there is an "original issue" -

From the various comments in this thread (see #'s 9-15) it's very possible that the problems some people are experiencing are due to configuration issues, or bugs present in contributed modules.

I'm tempted to set this to "won't fix" as the queue has become fairly convoluted with problems arising from different reasons.

@nomonstersinme -- your issue definitely comes from config issues -- users can be given edit rights over different node types -- more importantly, if you are allowing a client with minimal technical skills into your site, you should use something like the Demo module to grab a db snapshot; or, only give the client access to a cloned copy, and keep them away from your dev environment. This protects your work.

i'm pretty positive its not a config issue but maybe you can give me some insight...

i have given this role access to edit based on content types but the administer > content management > content section is not available for that user role unless i select "administer nodes" in permissions. which gives them the ability to edit ANY node regardless of content type and my other permissions. i want my user to have access to publish a particular content type so i need the list view in content.

maybe i read this thread wrong, but i thought that was the issue that people were complaining about. if i'm wrong i apologize. any help is appreciated.

The ability to "edit based on content type" (and I'm assuming that you assigned "edit all" rights to a role at admin/user/permissions) can be accessed for specific nodes when viewing the actual node -- the user will see an "edit" tab.

The page at admin/content/node -- or administer > content management > content -- is (IIRC) only available to people with admin nodes rights.

We generally use the views module (and in some cases, Views Bulk Operations) to present lists of content to subadmins -- it provides a level of granularity that core does not provide.

ah, see my problem is that i'm using a lot of panels and views so the nodes nested in them are not easily accessible unless you go through administer/content management/content

i will make some views to solve this... thanks for your input!

Hi friends... i used the tip given by bonobo some time ago in another thread for this problem... here is a simple solution that worked like chime:

1. After logging in as admin, go to >> admin/content/node-settings
2. Rebuild Node Permissions

Reset your permissions as you want from Admin >> User Management :-) and then say thanks to bonobo...

* Oops sorry, wrong location. It goes to the Simple Access module's issues. *

#24 or bonobo's simple solution doesn't work on D5.

I don't have any other access control modules.

I've tried changing the module's weight in phpMyAdmin.

If I deselect "administer nodes", the node edit page will not show the access groups and its checkboxes. The page shows the the titles: Access Group, View, Edit, Delete.
If I select it, the node edit page will show the access groups and their checkboxes.

LoL ..Thanks a lot, sateeshNVL! This worked like charm!

I have been trying to solve that problem for hours!
An authenticated users were able to post content but as soon as they save the content, I could see "Access Denied". Only the admin could view what was posted.
If you provide "administer nodes" permission for the users, then it works fine, but that is not the goal. As soon as I did "Rebuild Node Permissions" at admin/content/node-settings everything was back to normal.

Thanks once again!

Cheers

I'm having similar problem with Drupal 6.14 and with following nodes installed:
Views, ImageCache, Light, Date, Image, AdvancedHelp, LIghtBox2 6.x-1.9, Wysiwyg 6.x-2.0

I have made a new content type listing products. I have created quite a bit of content with admin. Then I use Views-module to show relevant content to specific roles e.g. Site owner only sees sold products etc... From the table of shown content there is a link to more details of product - the link is to node. Now to problem is that only role(s) with administrative node permission can see the node view - Note that through the View the role had access to see content already,

I tried all tricks mentioned in this thread (and from all the thread that were linked here) e.g. rebuilding permissions etc.. but nothing works. Any ideas to start looking in to more depths of this problem. Help is really appreciated. I have been struggling with this for a while

UPDATE as of 10.12.: I found out that user has access to nodes he has createt, but not anything else (unless you give administrative rights). I tried to figure out how the node_access API works, but not yet with great success. Anyway I was wondering is it normal that node_access table has only one entry:
nid gid realm grant_view grant_update grant_delete
0 0 all 1 0 0

Where are node specific access rights stored? I can't find anything in the DB. And what I checked the node_access(), if you give administrative rights it basicly skips checking rights and maybe that's the reason it works? Has my SQL table been corrupted or what??? And sad is tha at least rebuilding rights does not help at all...

As this seems to be a bit different to original bug report I made a separate one in #656004: Node access rights allowed only with administrative rights - Rebuilding access rights does not help!

Cheers,
Jake

Setting this to "won't fix" as this issue has been essentially taken in countless different directions, and virtually none of these directions have anything to do with the unicorn-esque "core bug" that was described.

Just about every described in this thread sounds like user error/config issues, and the most recent issue (#28) has it's own thread, where it will get its own attention.

I just had the exact same issue: unauthenticated (anonymous users) were not allowed to view freshly created nodes on drupal 6.15. My permissions are all correct, and rebuilding the permissions on /admin/content/node-settings did not work. Then I realized I had unchecked "In moderation queue" in the "Publishing options" section while creating the node. The solution for me was to edit the nodes, check the "In moderation queue" option and save. After approving the modes in the moderation queue, everyone can see them again.

So I believe this to be a modr8 issue, I am running 6.x-1.1.

Thank you, RichieB!

For me, it was the "published" item under publishing options. Checking that option solved the problem.

After i installed several different modules to regulate access of some nodes, i bumped into this same problem, probably because there is compatibility problem between different modules.

After 5 hours of trouble shooting and reading all these threads about the problem, here is how you should fix the problem:

for those who don't have Drupal Tweaks module, drop everything and install it. then do the followings:
1. Extracted and enabled Drupal Tweaks as usual,
2. go to Drupal Tweaks
3. click "operation" tab
4. under "permissions", click "rebuild permissions",

** if you don't want to install drupal tweaks , just find the options on your administration menu that allows you to rebuild permission, it should work the same

good luck to all of you

I also had the same problem and solved it by rebuilding permissions. The page to rebuild permissions is found at /admin/content/node-settings. No extra module needed for that

@sateesh.nvl

Thanks. rebuilding the permissions worked for me. great work.

Rebuild permissions solved problem also for me.

Another solution: I had set-up the Body of a page using the "Full HTML" input type, then handed the site off to the end-user. Attempting to edit the page, they received the "Access Denied" error even though they had full permissions to the content type. Giving them permissions on the "Full HTML" input type did the trick in this case.

Hi,

I have three user roles:
1 - Candidate
2 - Examiner
3 - Admin

Currently I am facing some issues, that is:

1 - Not able list the content(questions and test) in Examiner profile.
2 - One examiner user questions are visible to other examiner user.

Please suggest me, thanks in advance.

Support requests are never major or critical.

Users without "administer nodes" are not able to access admin/content/node page? And we are debating if this is a critical issue or not? And we are debating this if this problem exist or not since millions of drupal site are out there?

Well I challenge you on a clean drupal 6.27 install soon as "administer nodes" turned off, authenticated user are not able to access admin/content/node !!!

And I was not able to solve my issue with nodeaccess nor with content access which is: I want to have a node specific delete permission on a role while I can have content node management (admin/content/node) working for the same user role.

Thanks

#4, #8, #11, and #19 are correct. This is not a bug.
#11, #19 #38 are correct. Support requests are never critical.