That's the message I get when I try to enable Meetings Feature. I am using OA 1.0-beta8 (24 Aug 2010 build). Not a very informative message to see what's up, so any ideas?

CommentFileSizeAuthor
#8 meetings-conflict-subscribe-content-938706-8.patch1.83 KBAnonymous (not verified)

Comments

Anonymous’s picture

Anonymous (not verified) commented

Are you positive that you don't have the meetings feature installed twice?

Hmmm. This is curious. I won't be able to get around to debugging this in the immediate future, but I am open to further debugging help and (especially) a patch.

charos’s picture

charos commented
Priority: Normal » Minor

I'll make a fresh install of OA with only Meeting as contrib feature and will report back to you!

intu.cz’s picture

intu.cz commented
Issue tags: +conflict, +features, +OpenAtrium, +meetings

I confirm I had a similar experience, ended up restoring from a backup.

Anonymous’s picture

Anonymous (not verified) commented

intu.cz - Which version of Meetings did your backup take you back to?

charos’s picture

charos commented

Same thing with fresh OA. Will try previous versions of the module to determine whether it's because of the latest OA build or because of the latest Meeting build.

tutumlum’s picture

tutumlum commented

Subscribing...

charos’s picture

charos commented

Tried previous alpha3 with same results.

Anonymous’s picture

Anonymous (not verified) commented
StatusFileSize
new meetings-conflict-subscribe-content-938706-8.patch1.83 KB

Same problem here. The conflict is because it's defining the 'subscribe to content' permission and atrium is as well. It works OK if you just remove references to this as per attached patch, but that's probably not the answer in the long term.

Crom’s picture

Crom commented

looks like there could be something similar going on with the latest release of Acquia commons. When activating the same beta version I get a conflict notification in the features config pages saying that "Meetings conflicts with: commons_notifications. Both features define the 'subscribe to content' permission.

HumanTex’s picture

HumanTex commented

Same issues w/Commons as in #9, but with Meetings 6.x-1.x-dev installed instead of a beta.

Yura’s picture

Yura commented

OA-1.0 has similar situation. It's referencing "subscribe other users" and "subscribe to content" permissions.

mike365’s picture

mike365 commented

Still having this problem, was there any solution?