Enabling node access is disabling ability to edit nodes [#439942]

Hello,

Hello, one of the last steps on a site I am working on was to create node permissions so I installed the node access module, granted the appropriate rights etc. While I was happy to see that it worked in blocking or allowing specified nodes, I cannot edit any content on my site while this module is active. When I click on "Edit" from the node, page, book, story, blog etc it just goes to a white screen. In my admin section I receive this error:

"warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'node_page_edit' was given in /home2/joeycatz/public_html/includes/menu.inc on line 348."

If I turn off the node access module it immediately allows me to edit the nodes. Please help.

Comments

Comment #1

Sole Assassin CreditAttribution: Sole Assassin commented 21 April 2009 at 13:25

Status:

Closed (won't fix)

» Active

Comment #2

JDonofrio CreditAttribution: JDonofrio commented 21 April 2009 at 20:44

Samething here. When I upgrade to 6.x-1.4, I start getting a bunch of these errros:

warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'node_page_edit' was given

When I downgrade back to 6.x-1.3 and flush all caches I can once again edit existing nodes.

Comment #3

emptyvoid CreditAttribution: emptyvoid commented 21 April 2009 at 21:22

Assigned:

Unassigned

» emptyvoid

Quite troubling.. the update was tested on three different configurations and it worked just fine.

I have confirmed the problem as I just installed it on a new slice host server and I too am seeing the issues.. I will work on it ASAP

Comment #4

Sole Assassin CreditAttribution: Sole Assassin commented 21 April 2009 at 21:25

Thank you very much I am quite confused I tried to troubleshoot it to no avail. Thanks for your efforts void.

Comment #5

emptyvoid CreditAttribution: emptyvoid commented 22 April 2009 at 05:31

For now I would recommend using the 6.x-1.3 release until I can track down the conflict.. it appears to affect newer releases of Drupal and is directly related to the "fix" I included for core file paths.. (sigh) this has caused an never ending pain in my back.. :P

List of older releases here: http://drupal.org/node/413602/release

Comment #6

emptyvoid CreditAttribution: emptyvoid commented 22 April 2009 at 17:10

Version:

6.x-1.4

» 6.x-1.5

Yep issue was confirmed, the last release 1.4 was a total bust. When testing I forgot to clear all cache and the changes weren't reflected in my test environment.. Shame on me, I will make sure this doesn't happen again.

Released 1.5, this is more of reversion instead of a new release.

Comment #7

Sole Assassin CreditAttribution: Sole Assassin commented 23 April 2009 at 03:20

I have tried both the previous rev that you suggested and 1.5 and I am getting this error after now:

Fatal error: require_once() [function.require]: Failed opening required 'sites/all/modules/node_access/../../../modules/node/node.pages.inc' (include_path='.:/usr/lib/php') in /home2/mysitename/public_html/includes/menu.inc on line 346

Any ideas?

I can't seem to have any luck with this.