Since I upgraded to core 6.14, OG tracker suddenly started to show double nodes. This affects non-admin users and only node under OG (og access)
Selecting the "distinct" option under og tracker view helped but there is a performance pentaly. I didn't have this penalty when using core 6.12 (I went from 6.12-6.14)

It seems this seems to be related to this issue #284392: db_rewrite_sql causing issues with DISTINCT

CommentFileSizeAuthor
#20 db_rewrite_and_tests-D6.patch5.18 KBzchandler

Comments

moshe weitzman’s picture

The fix is going to come from core, i hope. Nothing OG can do here.

ajayg’s picture

I just opened this here so OG users are aware of this.

brisath’s picture

Does anyone know if the latest Dev versions of Drupal core resolve this problem?

ajayg’s picture

As of today nope. There is a patch discussed here #284392: db_rewrite_sql causing issues with DISTINCT . When it is ready in core, it will solve the problem.

brisath’s picture

I'm still watching the discussion linked in #4. I haven't seen any addition of the discussed patch to core yet. Are we sure that is the issue that will solve this OG double post problem in views? In other words, there is no solution but to wait until it goes into at least a dev version of Drupal core (since I am not patch literate nor do I want to risk a patch right now)?

mathieuhelie’s picture

Doubling occurs in all OG views, as well as custom views where group nodes are mixed with other content types (only group nodes appear twice).

Does not occur for users with administrator privileges.

Bernardine’s picture

Subscribing

Hunabku’s picture

Subscribing

glen201’s picture

Ug, I've never seen a point release of core break so much as 6.14. Getting a little trigger happy with 6.x in the face of the 7.x release, I presume. I'm staying away, and I turned off the Update Status updates so I don't get bothered with being out of date. :)

dugh’s picture

subscribe

Pongolyn’s picture

subscribing

mrosas’s picture

subscribing

MatthijsG’s picture

subscribe!

moshe weitzman’s picture

Status: Active » Closed (duplicate)
Blue’s picture

I have the same problem in OG 2.0

bricef’s picture

Hello,

I applied the patch #257 from http://drupal.org/node/284392 and i still have a problem. When i add a node to one my organic groups i can see this message :

Duplicate entry '304' for key 1 query: INSERT INTO og_access_post (nid, og_public) VALUES (304, 0) in /var/www/html/trunk/includes/common.inc on line 3468.

brisath’s picture

Does core upgrade to 6.15 resolve anything, or do I need to keep holding back? I'm following http://drupal.org/node/284392 but not sure if I missed something in regard to OG and the double post problems.

tetty’s picture

subscribing

brisath’s picture

So is this the dev version that finally allows me to upgrade Drupal and avoid this OG double posting issue?

http://drupal.org/node/97368

I saw it was committed in the discussion linked from #14 above.

zchandler’s picture

StatusFileSize
new5.18 KB

I followed ajayg and moshe's advice on which thread to watch, and the fix to the node-doubling problem is in that queue. The bug is not OG, its any node access module + core (after 6.13).

Patch by mathieu is available here:
http://drupal.org/node/284392#comment-2254932
(attached below for your convenience)

confirmed here:
http://drupal.org/node/284392#comment-2264916

confirmed w/OG specifics here:
http://drupal.org/node/284392#comment-2265998

which I can confirm in my own site:
Drupal 6.15
OG 6.x-2.0
Views 6.x-2.8

When following the instructions on applying the patch (to core), note the non-standard -p1 flag (-p0 won't work).

zchandler’s picture

henrijs.seso’s picture

subscribe. patch #20 didnt help.

ajayg’s picture

Drupal 6.16 has all the required patches and should fix this issue. I haven't tried yet. If you have, please write it here your observation.

stacysimpson’s picture

Subscribing

brisath’s picture

I've upgraded to 6.16 and can verify the nodes are not showing twice in OG. I haven't run into any problems at this point.

tugis’s picture

The reason for the duplicates is a Node Access issue. If we have just one "View" grant per user, we won't see duplicates. I mean, if we are admin of a group, we receive a view grant from "og_admin" and "og_subscriber" realms and we can also receive the view grant from "og_public" if the group is public. So, I was facing the same issue and what I did was hacking the code of "og_access.module" so I just give 1 view grant per user. This solved the duplicates.