Project

General

Profile

Actions

Feature #495

closed

End groupblog link

Added by Boone Gorges over 13 years ago. Updated about 13 years ago.

Status:
Resolved
Priority name:
Normal
Assignee:
Category name:
BuddyPress (misc)
Target version:
Start date:
2010-12-18
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

Right now there doesn't appear to be a way to change or cancel the blog associated with a group as the group blog. At the very least, there should be a button that lets you end the relationship, so that you can use the blog for another group.

What should happen to group authors at that time? If blog X is associated with group Z, and all members of Z have been given the Author role on X, what should happen to their roles when the X-Z association is broken? Maybe just a message after the decoupling that warns the decoupler (in big letters!) that those members still have access, with a link and instructions on how to remove them manually?

Actions #1

Updated by Matt Gold over 13 years ago

Yikes -- wow. This is a can of worms in a lot of ways. Keeping people as authors on the blog doesn't seem ideal to me, but neither does removing them (what would happen to the post?). If members aren't removed, this could get messy very quickly. Imagine that someone added a blog to a group with 60 members . . . and then ended that relationship before later associating it with a group with 100 members. Suddenly, the blog would have 160 authors, right?

Not sure how to get around this . .. .

Actions #2

Updated by Matt Gold over 13 years ago

Bump. Added a few other members of the team as watchers.

Actions #3

Updated by Boone Gorges over 13 years ago

The situations in which this is a real problem are edge cases at best. Normally if someone is moving from one sensitive group to another they will not reuse a blog. There is always a way for people to manually remove members if necessary, and the Users dashboard panel even has bulk management features. It's not worth sinking a lot of development time into reproducing these features. That's why I suggest leaving the members in their roles and pointing the admin to WP's native interface for user management.

Actions #4

Updated by Matt Gold over 13 years ago

I agree that it's not worth sinking lots of time into this, and you're right that WP's tools provide ways to deal with this. But I do think it may happen more often than you'd think. I guess we'll see.

Actions #5

Updated by Boone Gorges about 13 years ago

  • Status changed from Assigned to Resolved
Actions

Also available in: Atom PDF