CUNY Academic Commons

This is due to an incompatibility between the way that our Group for Group Admins auto-add feature works, and the new group-membership caching layer introduced in BP 2.6. Briefly: when creating a new group, the creator's membership ID cache was being invalidated; then the GFGA tool was running, and populated the cache before the creator's membership in the new group had been saved into the database. As such, the user's membership cache did not contain the just-created group. I've fixed this by moving the GFGA population routine until after new memberships are saved to the DB: https://github.com/cuny-academic-commons/cac/commit/4174cb85813da6b042aa981b8a8141ea7a944147