Here’s everything I have marked as 4.3.0 still, https://github.com/WebDevStudios/BuddyPress-Registration-Options/milestone/5
For completed tasks intended for 4.3.0, https://github.com/WebDevStudios/BuddyPress-Registration-Options/milestone/5?closed=1
If you feel adventurous, this branch holds 4.3.0 at the present state: https://github.com/WebDevStudios/BuddyPress-Registration-Options/tree/4.3.0
Completed changelog at present time:
* Added: New hook in pending member “additional data” section for displaying custom data about user.
* Added: Support for BuddyPress notifications of new user, checkbox setting to enable or disable it.
* Added: BPRO menu items to BuddyPress Member Admin Bar for administrators.
* Added: prevention of activity stream posting about new member until member is approved.
* Added: Filter in wp_redirect urls for non-logged in users.
* Added: Email notification and default message setting for pending users upon activation.
* Added: Before and after save hooks for general settings.
* Added: Filter on IP address before saving to user meta.
* Fixed: Hardened user display in pending member list if no Full Name value provided.
* Fixed: Mark user as not spam, upon approval, in BuddyPress core’s user management page.
* Fixed: Prevention of working in non-main site sites for Multisite.
* Fixed: internationalization issues with singular/plural “members” admin notice.
* Updated: internationalization strings for default messages.
Thread Starter
Earl_D
(@earl_d)
Thanks fo the response and the plugin. It is a core component to my site. The one component other than BP itself I would have a hard time running without. Many cool completed features in the branch some I could put to use now. I may check it out any potholes I should be aware off.
On the current 4.3 branch it says
‘set BuddyPress Groups or Blogs/Sites new members can join on the registration page.
Will there be an option to assign all new users to a group upon registration. Also could that idea to be extended to provide an auto freind option to have admin sasoned as friend to every approved member.
Thanks again
Regarding the README.md contents, that’s admittedly from 4 years ago, and the functionality/purpose of the plugin has evolved away from that over the course of time. It’s not something that I have planned at the moment.
Some time before I stepped in as primary dev, plugin’s purpose got changed and reduced down to what it is now. Not sure if I want to try and re-expand at all, or continue to focus on access prevention until approved.
Thread Starter
Earl_D
(@earl_d)
Understood I just saw that and was surprised since I didn’t see it in the current functionally. Was it there buried somewhere or in upcoming version I would have been able to reduce my plugin use considerably to just this one. But I get what you are doing and it works great. Will still check out the test version.
Thanks again.
