Uninstalling organic groups

Not so critical

Upgrading to OG 5.5 did not solve the problem. New content is not able to be viewed by unauthenticated browsers, contrary to the access permissions applied to the content. (This is with OG turned OFF)

Now with OG applied in Modules, I get an error when going to my views (whether logged in or not):

Fatal error: Call to undefined function: arg() in /home/thepulse/public_html/sites/all/modules/og/og.module on line 214

With OG turned off, new content is not viewable by unauthenticated people.

I'm thinking this may be a Drupal 5.6 issue. I have to roll back, and try to get this sorted out on a test server.

I think the problem is likely that I did not do this (found in the Organic Groups configuration):

-----
Access Control:

Before disabling this module, use the button below to restore default permissions.
Organic groups access control is currently enabled.
-----

One forgets about these things after a long time.

HOWEVER,

I did this and it did not work.

I clicked on the button and thus disabled access control.

I then went to modules and deactivated OG (rollback to 5.x-3.1 right now)

I created a blog post (one of the content types og could target)

I logged off, but could not see the post.

More to come...

Looks like the issue was node access permissions cache:

To do this, go to Home > Administer > Content management > Post settings and click "Rebuild permissions".

http://drupal.org/node/171100

Uninstalling Organic Groups
uninstall og

So, this is what I ended up doing:

Deleted my (one and only) group

/admin/og/og --> disable access control

/admin/build/modules --> disable og

/admin/content/node-settings --> rebuild access status

/admin/content/types --> deleted group content type

/admin/build/views --> deleted group views

Go to MyPHPAdmin: and drop: `og`, `og_ancestry`, `og_uid`, `og_uid_global`;

Remove og from sites/all/modules

And now I'm happy and will be doing this on my live site.

changed version, category and assigned.

Simply rebuilt permission wouldn't cut it.

I still want the OG module, Should I follow your steps and reinstall OG?
Ouchhh ... deleting exiting groups? any less destructive way?

Omitted content type is still "access denied" for anonymous user!

It's not an OG Access issue, rather it is a Domain Strict that forces users to be assigned to a domain in order to view content on that domain.

First, it changes the default Domain Access behavior. This module
makes the grants given to a user specific to the domains that the user
is registered to see. Normally, all users are granted the same permission
to view content. In the case of Domain Strict, individual users can
only see content on domains that they belong to, or content that is
assigned to 'all affiliates'.

Second, it shows module developers how to alter the behavior of
the Domain Access module by using the API. In this case, we only
use the function hook_domaingrants() to change the default module
behavior.

Automatically closed -- issue fixed for two weeks with no activity.