I've been trying to deal with a node/edit access problem for a good while now - I don't know why I haven't figured this out sooner, or whether this is mentioned in the Drupal handbooks, but I'll publish my findings in the hope that other users don't get stuck with the same problem.

The problems I've been having have been when I've created content during the building stages of a Drupal site. I'll create a page with Lorem Ipsum text as a holding page, with the intention of granting the clients access to edit the text at a later date. When it comes to the client logging in to change the content, they often don't have an option to edit the node, even though I've given them an admin role with permissions to edit nodes of that type.

I've previously resorted to using third-party module fixes (such as node_privacy_by_role, et al) to correct this problem, but figured that it must be something very basic that I was doing wrong. I now know what it is - I'd created the original nodes in HTML, changing the node formatting filter accordingly (to HTML formatted) when submitting the post, but I hadn't given the admin role permission to create HTML formatted nodes themselves. This means that, regardless of their permission to edit certain node types, the node's HTML format meant that admin roles were denied editing access.

The simple fix was to edit the input format settings of the HTML filter (?q=admin/filters) to allow admin roles to be able to create HTML formatted nodes. After logging in with a test admin account, I found that the option to edit the pages appeared.

I hope this helps anyone else with the same problem - it's a simple one, but not immediately obvious.

Comments

nisguy’s picture

I thought I was going mad!

dww’s picture

this kind of forum post perfectly illustrates the kind of confusion that comes about because access to input filters are permissions in every sense, but are not actually stored and treated that way using the usual permission UI. see http://drupal.org/node/11218#comment-172217

cheers,
-derek

___________________
3281d Consulting

dww’s picture

the issue where i started the discussion about my proposal to turn access to filters into real permissions was getting too crowded, so i started a new one: http://drupal.org/node/110242

___________________
3281d Consulting

ja_ro_no’s picture

THANK YOU THANK YOU THANK YOU. I was pulling my hair out as well and was trying all sorts of crazy things to make this work.

Cheers!

schirchl’s picture

When I go to create a new page, I can no longer change the input format, attach a file, or look at menu settings. On existing pages, I can't edit properly.

My web developers began building my site with HTML then switched to PhP.

I've read over this thread and have tried changed admin settings for input format and access control, but I can't find a setting that fixes the problem.

Any suggestions?

Lisa Schirch

wayfarer_boy’s picture

I'm guessing here, but by the sounds of it the site was probably not originally installed and configured by yourself - ie, there are a group of users or a user in a higher role than yourself. They will control and grant access throughout the site, so you need to contact them and get them to grant your user role access to the missing features.

Jax’s picture

I was having the same issue in 4.7. I became even more boggled when I noticed that when you go to the "admin/node" page you do see the 'edit' links. Clicking on it goes to unauthorized so this is actually a bug. I'll have to check if this still happens on 5.x.

virtualdrupal’s picture

Thanks

agnez’s picture

thanks !! (this drove me mad, too)

elwild’s picture

Right now the module Node Breadcrumb will also break the ability to access the node/edit option.

willhowlett’s picture

Thanks so much for posting this advice!

yang_yi_cn’s picture

i have this problem too, thanks for posting the solution

johnny-j-hernandez’s picture

So I was having a problem with the node edit permissions for an "editor" role where editors were unable to edit certain nodes but could edit other nodes of the same type. I went through any number of modules that promised custom control of node access with no results. I've sense chucked all the node access modules and just set the "administer filters" permissions for my editor role and everything works.

PHEW!

-johnny;j

HydroZ’s picture

Thank you soo much for sharing this information.
It drove me crazy and wasted about 10 hours of my life time.

akanik’s picture

Ahhhhhhh. Thank you so much.

RowboTony’s picture

Thanks! This is still coming back to bite me in the rear on Drupal 7 all these years later. Thanks for the tip!