BuddyPress.org

Thanks for your tests (and your wishes) @alersn 👌

I’ll try to explain what’s happening in your case and I believe it also concerns most people using a plugin that is managing Group or Member types. First, I had to handle a similar case for a plugin I’ve build to manage Member Types years ago.

These kind of plugins had to make a choice about how to ensure type properties persistency, because when BuddyPress introduced the feature only registering Types using custom code was possible. For instance, I chose a regular WordPress option. BP Create Group Type chose to use a Custom Post Type. So most Group Type properties like the one to show checkboxes into the Group create screen are saved as post metas.

In 7.0.0, as BP Types are custom taxonomies, we decided to use term metas to store these properties. This means, properties are not saved at the same place, that’s why you’re experiencing this issue.

I agree it’s not great for user experience to have 2 group types menu into the admin and have 2 different ways to manage Type properties: it’s confusing. Ideally, these kind of plugins should alternatively:
a. disable Group Types menu generated by BuddyPress.
b. use a specific upgrade routine when the plugin is used with BuddyPress 7.0.0.

I chose b. for my plugin 😉 because I believe it’s important to enjoy the improvements brought by BuddyPress. It’s standardizing how Type properties are saved, and it will avoid users to be stuck with a BP Plugin (that might have dropped its support) in the long term.

If BuddyPress plugin developers are interested about how I’ve migrated the Member Types properties my plugin was using so it now uses the BuddyPress way, here’s a gist about it:

https://gist.github.com/imath/df65b7c856fbd02024a84c7ecc016090

Best wishes to you too 🎉