Having upgraded to 6.x-3.5 I am getting 'Node object data incomplete -- have you enabled the Node Tools submodule?' warnings appearing on my pages. (Can't give a url as on internal dev system.)

I don't have the Node Tools submodule enabled and would need to install smart tabs to do so as it's a dependency.

As Node Tools isn't listed a dependency (I believe) might the message indicate I've a problem I need to get to the bottom of (any ideas?) or might it just be that with this latest version I should be enabling Node Tools and the message should go away with nothing to worry about? In which case should it be optional?

Searching the internet I found less than a handful of sites showing this warning - none in English - and no other references to the warning.

Thanks,
Nick

Comments

nickrice’s picture

nickrice commented

Here's an example of the message in the wild (towards the top of the page in a yellow box, if not fixed yet):

http://www.rpgmenace.com.br/?q=content/projetos-da-galeria

(That site has nothing to do with me.)

nickrice’s picture

nickrice commented
Status: Active » Closed (fixed)

OK I've enabled all the bits and bobs and the message has gone away.

Reading the notes on the 6.x-3.5 release it looks to me as if that's the right thing to do and that it doesn't mean there's an underlying problem. Should have read everything properly first.

So closing this.

rdeboer’s picture

rdeboer
Location Melbourne
commented

Module Grants depends only on Node Tools, but not on Smart tabs (although Module Grants Monitor does).
I suspect you uncompressed the latest .tar.gz over the top of the existing install, but then forgot to go to Site building >> Modules to activate the changes by pressing "Save configuration".
See how you go with that in the future.

robbertnl’s picture

robbertnl commented

Same issue, i had the node tools submodule enabled. I always get this message when a user is not allowed to view the page.
I am using Node revisioning and Content Access as well. I noticed that the error message is generated in Revisioning as well, so i think its related to Revisioning in combination with Content Access

rdeboer’s picture

rdeboer
Location Melbourne
commented
Version: 6.x-3.5 » 6.x-3.6
Status: Closed (fixed) » Active

Weird... Thanks for reporting and suggesting a potential culprit.

robbertnl’s picture

robbertnl commented

It's not a show stopper, I am just hiding the warning message now. The revisioning module line 653:

if (!isset($node->num_revisions) || !isset($node->is_current)) {
    drupal_set_message('Node object data incomplete -- have you enabled the     Node Tools submodule?', 'warning', FALSE);
}

The node object is null and causes the warning message. I guess that the node object is null because the user doesn't have access to it (as defined in Content Access).

rdeboer’s picture

rdeboer
Location Melbourne
commented
Status: Active » Closed (cannot reproduce)

Can't reproduce. Please reopen or log a new issue if the problem rears its ugly head again.

johnpitcairn’s picture

johnpitcairn commented

I'm having the same issue now. The Node Tools error message appears for anonymous users viewing unpublished nodes.

Module Grants is set to OR permissions (but AND produces the same error)
Revisioning module is enabled, with default configuration.
Most Revisioning access callbacks are overridden via a custom module.
Content Permissions is enabled, all fields are viewable for anonymous users.
No other access control modules are enabled.

Disabling the custom module and flushing menu cache has no effect.
Disabling Content Permissions has no effect.
Rebuilding access permissions has no effect.
Disabling the Revisioning module fixes the error.

halrichman’s picture

halrichman commented

I am getting this same problem. Not sure about reproducing it because I do not know what is causing it. But our site is currently experiencing the problem. Any insight would be appreciated.

Cheers,
Hal :)

rukaya’s picture

rukaya commented

I'm getting this message as well, but I think I only started getting it when I had imported a bunch of users from active directory and then messed around a bit removing them and putting them back a few times (testing). I think it might be something to do with some bad data in the users table, but that's just a hunch. The error message has occurred a few times now but I can't see any patterns which would lead me to the cause.

Warning messages:
* warning: Cannot modify header information - headers already sent by (output started at \includes\database.mysqli.inc:135) in \includes\common.inc on line 148.
* user warning: Table '.\sanbi\users' is marked as crashed and should be repaired query: SELECT n.nid, n.type, n.language, n.uid, n.status, n.created, n.changed, n.comment, n.promote, n.moderate, n.sticky, n.tnid, n.translate, r.vid, r.uid AS revision_uid, r.title, r.body, r.teaser, r.log, r.timestamp AS revision_timestamp, r.format, u.name, u.picture, u.data FROM node n INNER JOIN users u ON u.uid = n.uid INNER JOIN node_revisions r ON r.nid = n.nid AND r.vid = 243 WHERE n.nid = 74 in \modules\node\node.module on line 752.
* warning: Cannot modify header information - headers already sent by (output started at \includes\database.mysqli.inc:135) in \includes\common.inc on line 148.
* user warning: Table '.\sanbi\users' is marked as crashed and should be repaired query: SELECT * FROM users u WHERE uid = 0 in \modules\user\user.module on line 169.

Other message:
Node object data incomplete -- have you enabled the Node Tools submodule?

And then upon refresh another warning message (with the user now logged out):
user warning: Table '.\users' is marked as crashed and should be repaired query: SELECT * FROM users u WHERE uid = 0 in \modules\user\user.module on line 169.

John Carbone’s picture

John Carbone commented

Same error here. I imported a fresh database and got it once, as an anonymous user, refreshed the page and it doesn't appear again. I don't know if that helps anyone or not.

emarchak’s picture

emarchak commented

I'm consistently getting this error, and have Node Tools enabled. Consider this a subscribe/will post if solved.

devsuresh2005’s picture

devsuresh2005 commented

Resolved!

Make sure your tables are not crashed. I got this error in my local environment, after debugging I found 'node_revisions' got crashed, Once I restored this issue got resolved.

Not sure this post is active or closed but this may help somebody.

Thanks.