By jissou on

Hi,

I'm running Drupal actually 4.7.6.
few months ago I ran 4.6.11 Drupal Version and I created few nodes with a powerfull user.
Now few month later (after an upgrade for security reasons) with the same powerfull user, I can't not any more acces these nodes.
Only the administrator account can edit this pages.
I can't see the edit tab" on this page and when I access a page through the content menu I've got a denied error in logs.

I searched few hours in all menu and administer section ton uderstand and correct this.
Did I miss something.

Sorry if the question seems trivial.

⋅ Categories: Drupal 4.7.x

Comments

geodaniel’s picture

geodaniel commented

Not sure why this should change, but it sounds like it may be related to filters (input formats). Check in the administration section that the user role you are using has the correct input formats assigned to them. If a person tries to edit a node that is set to use, for example, PHP input format but that user role isn't allowed to use PHP as an input format, then they will get the access denied message (and not see the edit tab).

Hope that helps?

jissou’s picture

jissou commented

Thank you very much geodaniel.
All works fine now.
An incorrect input format was the cause of the problem.
I change the defaut imput format to filtered html and I recovered immediatly the edit tab in all my pages.
Regards.

rgs’s picture

rgs
he/him
commented

this is still relevant today...just added a role? missing the edit button? make sure your new role has the appropriate input format permissions!

Lowell’s picture

Lowell commented

you may have added a module that adjusted the role or node permissions thus causing this problem.

To give this user role access to these nodes...first look through the user access settings

next, (this is just an idea that I like to use on my sites, back yours up first)
install the node_access module and view the Grant Settings for that node from the admin account
from there you can directly modify that nodes access permission settings

another approach is to browse the database node_access table and make adjustments there (experienced users only)

gluck