This appears to me to be a problem with Organic Groups and the way it handles permissions, but I am not in any way a coder and don't understand the deeper issues of Drupal and content access. So I am reporting it here in case there is a potential fix in UC (as well I reported it to OG, where a similar problem already was listed for Domain Access, but not UC)

Anyway, this is also a heads up for other users who can't track down why their anonymous users suddenly can't see the catalog.

With OG installed, anonymous users ceased to be able to see the catalog view at uc_catalog. Changing permissions for users and for OG makes no difference at all. Changing access permissions in the view itself makes no difference. Rebuilding permissions and clearing caches makes no difference. The only way to get anonymous viewers able to see the catalog again is to uninstall OG and then rebuild permissions.

Comments

longwave’s picture

longwave
he/him
Primary language English
Location UK
commented
Status: Active » Closed (won't fix)

Not sure what Ubercart can do about this if it's an OG issue. Feel free to reopen with more information if someone can track down the cause and it does turn out to be an Ubercart problem.

shadowmihai’s picture

shadowmihai commented

It appears to be an issue with *any* (or at least many) module that rewrites access permissions, such as Taxonomy Access Control, OG, Simple Access, etc., so I think there must be something that UC can take into account... I have had to completely disable all those modules for the catalog to appear to anonymous users. I understand what you are saying, but as a non-coder I don't know if I should *not* report it here...

longwave’s picture

longwave
he/him
Primary language English
Location UK
commented

See also #1189098: Catalog taxonomy terms issue with node access modules

RogueM’s picture

RogueM commented

shadowmihai, I'm not sure you saw my post on the ubercart forum, but you should be able to resolve your issue with TAC (lite). At least it worked for me... I would agree with longwave that this is likely not something UB should try to solve.

I have posted myself an issue in the ACL module issue section, which I think is where the underlying problem lies, if nothing else in term of documenting the module (API) net result in respect to control access, without specific module addressing the potential pitfalls.

This is my (probably badly argumented) feature request to that team:

http://drupal.org/node/1189144