If you need a practice area and a live area then just create some ‘practice’ groups. You can also create two installs one for development and training and one to go live with. I’ve done that sort of thing with a new accounting system/point of sale system for a company.
I don’t think it’s a good idea to ‘clone’ the groups component. At the lowest level they both write to the same set of tables. You wouldn’t really be doing much except changing what the ‘practice’ area says on the screen to the users.
@Jimcipriani
Okay, I read your request differently.
<>I need 2 groups of Groups: Practice Groups and Offices</>
By this, do you mean that your client has employees that fall into what they term practice groups? Such as, lawyers or doctors who are “in practice”. If so, then how many practice groups and how many offices do they have?
The best way to do this would be to disallow the creation of groups by anyone except the site admin or a few, select group admins–for lack of a better term. Then the group admins would create all the necessary Practice Groups and Offices groups, making them public or private as needed.
Since it seems that you are simply dealing with nomenclature, it is overkill to create a new component with the exact same functionality but with a different slug name.
I think what he means is; he needs to have two different types of groups:
1. Offices
2. Practices
(Not Practice/Test Groups)
Kind of like how on some social networks, you have; User Profiles, Musician Profiles, etc. But of course for groups rather than profiles.
This is something I myself would like to know how to achieve.
You should do that using group metas
i planned, but only planned, to develop a group-type plugin (you could do that with bpdev-groups-extra) where when users create a new group can select the group type without cloning a component.
Why that if i can clone a group component?
Because if the bp groups component has bugs, or will be changed with new features, you’ve to clone the component again..
You should do that using group metas
i planned, but only planned, to develop a group-type plugin (you could do that with bpdev-groups-extra) where when users create a new group can select the group type without cloning a component.
Why that if i can clone a group component?
Because if the bp groups component has bugs, or will be changed with new features, you’ve to clone the component again..
Should be possible to put some hooks and filters in place that add a new field (Group Type) to the group creation and then filter Group class returns based upon need for group type everywhere else.
I’m not saying I”m tackling this, just saying it’s possible.
Yep, you can do that with bpdev-groups-extra for now
Yep, you can do that with bpdev-groups-extra for now
