Column not found: 1054 Unknown column 'node.entity_id' after rebuilding permission [#1770504]

Hi i get the following error on login page(create a new account), maybe more pages bu not sure yet.

I have LoginToboggan 7.x-1.3
It happens after activating
Organic groups access control 7.x-2.0-beta1+19-dev and also with +18-dev
and after rebuilding permission as being told to do.

That mean i cannot accept any new users.

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'node.entity_id' in 'where clause': SELECT node.nid AS entity_id, node.vid AS revision_id, node.type AS bundle, :entity_type AS entity_type FROM {node} node WHERE (node.nid = :db_condition_placeholder_0) AND(( ( EXISTS (SELECT na.nid AS nid FROM {node_access} na WHERE (( (na.gid = :db_condition_placeholder_1) AND (na.realm = :db_condition_placeholder_2) ))AND (na.grant_view >= :db_condition_placeholder_3) AND (node.entity_id = na.nid) )) AND (node.entity_type = :db_condition_placeholder_4) )OR (node.entity_type <> :db_condition_placeholder_5) ); Array ( [:db_condition_placeholder_0] => -1 [:db_condition_placeholder_1] => 0 [:db_condition_placeholder_2] => all [:db_condition_placeholder_3] => 1 [:db_condition_placeholder_4] => node [:db_condition_placeholder_5] => node [:entity_type] => node ) in EntityFieldQuery->execute() (line 1144 of /.../public_html/includes/entity.inc).

Comment	File	Size	Author
#3	og_error.PNG	127.65 KB	AlfTheCat

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

amitaibu

Hebrew

Israel

CreditAttribution: amitaibu commented 2 September 2012 at 20:14

Priority:	Major	» Normal
Issue tags:	-OG, -login

Please try on a clean installation.

Comment #2

tommyvyo CreditAttribution: tommyvyo commented 18 October 2012 at 15:12

I just ran into this error on a clean installation.

I had og and og_forum_d7 installed.

The only OG modules enabled were og, og_ui, and og_forum_d7. Visiting /user or /forum resulted in the error being thrown.

Enabling og_access and clearing my cache solved the error.

Comment #3

AlfTheCat CreditAttribution: AlfTheCat commented 28 December 2012 at 07:12

Version:	7.x-2.x-dev	» 7.x-2.0-beta3
Priority:	Normal	» Critical

File	Size
og_error.PNG	127.65 KB

Same issue here, on clean install. Except in my case og_access was already enabled.
The error appeared after I had logged out of the site. And off course, I couldn't log in again for this error prevented that.

Luckily, I use Aegir and Drush and was able to disable OG from the command line:

drush pm-disable og
The following extensions will be disabled: og, og_access, og_context, og_ui, og_register, profile2_og_access
Do you really want to continue? (y/n): y
og was disabled successfully.                                        [ok]
og_access was disabled successfully.                                 [ok]
og_context was disabled successfully.                                [ok]
og_register was disabled successfully.                               [ok]
og_ui was disabled successfully.                                     [ok]
profile2_og_access was disabled successfully.                        [ok]
Content permissions have been rebuilt.

...which brought my site back. The output above details the og modules I had enabled. The initial screen presented on login is attached.

I'm marking this as critical, for users that do not have the Drush option, could lose access to their website entirely. Also changing the version, for I encountered this in beta3 of OG.

Comment #4

amitaibu

Hebrew

Israel

CreditAttribution: amitaibu commented 28 December 2012 at 21:05

Priority:

Critical

» Normal

@AlfTheCat ,
I'll need more info on how to reproduce.

Comment #5

AlfTheCat CreditAttribution: AlfTheCat commented 2 January 2013 at 03:06

Hi Amitaibu,

I just enabled the modules from the output above. I then eventually logged out of the site, without really doing any configurations to OG settings. When I came back to the site, the error was showing and I was unable to log back in.

It's a fresh Drupal 7.18 install but with many contributed modules. So I can't really see if it is caused by a specific module that was conflicting. Worth mentioning is that I have Profile2 enabled and the latest Ctools dev version.

I will revisit this off course, for the site will depend on OG. If I have more specific info I will post back.

Kind regards!

Comment #6

Strutsagget CreditAttribution: Strutsagget commented 4 January 2013 at 16:01

I got it working with disabling the module with drush, clearing caches and then enabling them again and rebuilding permissions.

Comment #7

swapnilp CreditAttribution: swapnilp commented 9 January 2013 at 07:49

I was facing similar problem and my drupal website was throwing same SQL error.
#3 solved my problem.
1. I disabled OG and OG dependent modules as suggested in #3.
2. I have to uninstall all the disabled modules.
3. I again enabled all this modules sequentially.

And it worked for me.

Thanks to all guys who supported in posting the solution.

Comment #8

cadiz11 CreditAttribution: cadiz11 commented 13 February 2013 at 09:16

I think I may find something. The problem is Organic groups access control. If there is no group and rebuild permission, it will occur. So after installing OG, you may need add some content types with group first. Then rebuild permission will work well. Once it happens, you can disable OG access control, then add content types with group, after that able the module again. I hope it may help.

Comment #9

Owen Barton CreditAttribution: Owen Barton commented 19 March 2013 at 04:39

I can reproduce what is described in #8 (with an existing site, haven't tried a clean install yet) - (1) enabling og_access then (2) adding content types then (3) rebuilding node access triggers the error. Flipping (1) and (2) seems to prevent it.

Comment #10

JayShoe CreditAttribution: JayShoe commented 24 June 2013 at 03:54

This bug still exists. I just experienced it with my OG installation as well. I'm waiting for my host to use drush to fix it... Hopefully they can do so for me.

Comment #11

manumad40 CreditAttribution: manumad40 commented 6 February 2015 at 03:51

Issue summary:

View changes

It seems that it has to do whith the "Entity reference" module.

Please, see: issue #2245827.

Comment #12

sam-elayyoub CreditAttribution: sam-elayyoub as a volunteer commented 13 June 2019 at 22:59

I had this issue after debugging it, I solved it by going to admin/config/group/fields it's all about group module, then try to add the group to your main content types, then try again and it would work with you

in general, the main issue comes because of the group module, group fields access and organic group

Comment #13

cirrus3d CreditAttribution: cirrus3d commented 2 May 2019 at 09:06

Any updates or good solution / patch for this would be great. It just happened to me on a site with og, entityreference and several other modules. Uninstalling og would be destructive for my site since I have several content types with lots of content that depend on them. Just disabling and enabling these modules and rebuilding permissions does not work for me.