Community site is broken

OG was never enabled, and the dblog entry shows the path with openatrium-1.0-build-2011.09.23-production so it is probably caused by some not announced upgrade performed yesterday.

I submitted the form at http://community.aegirproject.org/features (without any changes) and then cleared caches and now also permissions are broken - every page gives "You are not authorized to access this page", which is absolutely weird.

I believe that some (all?) Features were not properly saved/reverted on upgrade, and now it is broken completely after I simply submitted the form at /features trying to confirm that OG shouldn't be used/enabled. Doh.

+1
Getting 'Access denied' on all pages except 'My account'

I restored from a backup. Everything appears to be back to normal. I'll test a little further, but would appreciate confirmation.

The site is not migrated back to the working version, it is still openatrium-1.0-build-2011.09.23-production, and to break it again it is enough to submit the form at /features again. And Organic Groups are in fact enabled while all Features with many not saved/reverted, probably broken statuses.

AFAICT, the platform on which it used to exist has been deleted. I'll have to investigate, and rebuild it if necessary.

When I restored the backup, I confirmed that Atrium Groups and OG were disabled (though they are indeed now enabled). This is how the site was delivered from DevSeed, and is extremely unusual, as Atrium Groups is a dependency of the base Atrium feature. For the time-being, we should not be reverting features on this site, as there are lots of such customizations that have themselves not been exported into features, and so are easily lost.

fyi: https://community.openatrium.com/issues/node/3535

Alright, I believe the problem was caused by Atrium Groups insisting on being enabled, seeing as how it's a dependency of the Atrium feature. However, when DevSeed handed off the site to us, it had Atrium Groups disabled, and everything worked pretty much as usual

So, I've removed the depedency on Atrium Groups from Atrium... and it looks like it worked, but could use more testing

Good :)

btw, the modified version of the atrium feature is in the site's modules folder, and so should follow across platform migrations. However, since this is the feature that glues together the rest of Open Atrium, I expect there'll be changes to it with future versions. All it took was commenting out the dependency, though, so it should be a quick fix, should we need to update the atrium feature.

It turns out there was already a call to hook_system_info_alter() in community.module, so I just added:

  if ($object->name == 'atrium') {
    $index = array_keys($info['dependencies'],'atrium_groups');
    unset($info['dependencies'][$index['0']]);
  }

... and removed the hacked version of the atrium feature.

Thanks for the tip Steven.