Hi,

Here's another bug that I've been having.

Organic Groups has a submodule called "OG Access Control". When it is enabled those scoops which are chosen to be part of a Group, will appear twice in the Drigg listings (popular/upcoming) to those users who are members of that group.

This is how to reproduce this:
Drupal 5.7
Drigg 1.36
OG 7.3 enabled and configured as usual
OG Access Control 7.3 enabled

in the OG Access Control settings:
[check] Visibility chosen by author/editor using a checkbox on the posting form. Checkbox defaults to Public.
[check] Group administrator chooses whether her group homepage and audience are private or not. Defaults to public.

Create a usual group.
Create a usual user.

Sign in as that user and join that new group. Then submit a new scoop.

When you create a new scoop, check Public (checked by default) and choose one of the groups that you are a member of.

Then go to the Upcoming section as a user who is a member of that group, and you will see that the scoop teaser is listed twice.

Comments

mercmobily’s picture

Hi,

Is this a Drigg bug? Or is this an Organic Group bug?
I have never used nor installed organic group. And I fear that the Organic Group maintainers have never install Drigg.

What do we do now?

Merc.

mercmobily’s picture

Status: Active » Closed (duplicate)

Hi,

Ah, thank goodness somebody actually knows Drupal out there.

Duplicate of #324070: SELECT * FROM {node} violates db_rewrite_sql()

Merc.

drupalina’s picture

Hi Merc,
I don't think this is an OG bug, because I run another site that I built in 2007, where OG is very prominent feature with all sorts of OG-related modules. This problem does not occur with any of the listings of any node types there (brogs, stories, biblio etc).

I have tested many OG related modules, but this type of duplicate appearance is the first time that I see it.

I hope that the other problem, that you linked to, is related to this one as well, and will resolve his one once that's resolved.

I think that this is important to resolve, because OG is a very prominent part of Drupal and many users widely use it on their sites. So it's important to make Drigg work smothly with OG. Also OG provides a way for mini-communities and interest-groups to be set-up, thus sharing Drigg Scoops between people who might be interested in the same kind of thing.

If you incorporate a solution to this problem in a dev version, I'd be happy to test it for you on my live site.

mercmobily’s picture

Hi,

It's not an OG bug. It's a Drigg bug, which violates an *undocumented* constraints in Drupal core.

Please follow the other bug. This is a duplicate.

Merc.

drupalina’s picture

Thanks Merc.
Yes, I'll follow that. Keeping fingers crossed...