4.2.0 Beta

Got some issues with the plugin maybe im not understanding it correct, but users get an activation link, and no message when they click it, but they never get the e-mail about they need to be approved? how the heck do i fix this? i just want them to get an email about them needing to be approved, and no activation link.

Ellse this plugin dont make sence to me ??

They have gotten the activation link, and been able to use it, for as long as I’ve known the plugin exists. However, they can’t access the BuddyPress areas, even after they’ve activated. That takes approval by the administrators to access. I don’t believe they are getting emails at the moment about the fact that they are pending, I’d need to check and see if we should implement that. They should be getting emails when they’re approved or denied though.

Hi there,

Got a major issue, v4.2 simply does not work at all when buddypress is not installed on blog_id 1, but on blog 2 for example. Found out in line 264 of admin.php you simply hardcoded blog_id==1 so the menuitem will be shown only in case you have BuddyPress activated on blog 1.
Instead of hardcoding blog 1 you could perhaps check if BP is active like that: if ( function_exists( ‘buddypress’ ) ).

I have a WP3.9.1 multisite with WP multi network plugin activated. Network 1 has site A which is open for the public and has no Buddypress at all. Network 2 has site B that is a closed social site for a small group of people with BP installed.

I really would need the functionality of your plugin but it simply does not work in my setup. Tried to modify line 264 of admin.php to blog_id==2 and activated BP even on blog 1. This way i could reach https://www.site_B/admin.php?page=bp_registration_options. Could opt for user approval. When a user registers on site B than he/she will be prompted that the admin will have to approve their account, but on the back-end the number of member requests stays 0, so there is no way to approve the new user.

Can you just fix it on github?

In V4.1.3 with the same modifications i can approve the new user in the back-end, so i can get one step further. However some notification emails will not get sent in V4.1.3 as other people stated as well.

Hi summoner.

My biggest question for you is if this is a one owner site that is using multiple subsites to separate out content as necessary, or is it it different sites with different administrators?

The reason is because WordPress, by design, doesn’t allow subsite admins to manage users. So the only way I can think of for you getting around that is the sole/few super admins that are doing stuff within each subsite as necessary.

Regarding the blog ID checking, I just checked the history of the file, and the ID check was in place before I stepped in as primary developer for the plugin. I believe it was added intentionally because of the user administration restriction mentioned above. So we can’t claim it as a bug, just an inconvenience for the current need at hand. Reading through the rest of your replies above, those issues you’re seeing would make sense within the subsite.

I have it in the GitHub issues, if I recall right, that I’m trying to find a way to temporarily allow the subsite admins the ability to manage users, but I don’t have a solution figured out yet. Once I do, I would definitely want to remove that restriction.

Hi Michael,

To answer your biggest question: yes the whole network will be administered by me as the only super admin.

Some more details to understand me better:
There is a public site https://www.searchprofessionals.com which is open to the public and has bbPress forums activated but without BP. People can search for professionals on it and ask questions on the forum. But nothing more. Users of this site can not log in on the second site.

Then as second site there is https://www.professionals.searchprofessionals.com which is a closed social site of the professionals. They have BP and bbPress as well and they can even log in with their credentials on the first site to answer question of the public.

I’m still mulling over it but I am considering at least offering a filter for that spot for the occasional cases like this. My thoughts are apply the filter and store the returned site ID result to a variable, verify that that site ID is a valid available one in the MS setup, and if it is, pass that in, otherwise fallback to the current original value.

I’m aiming to get some more work done on the plugin today to help address beta feedback since I posted that, so we’ll see what comes of it. I do want to get this out the door soon and off my plate for the time being ??

https://github.com/WebDevStudios/BuddyPress-Registration-Options/commit/e38480aba8296ac9bed59215aa473f17728b6c67

If you are willing and have a dev copy of the site available, I’d love some help getting this tested.
Download: https://github.com/WebDevStudios/BuddyPress-Registration-Options/archive/alpha-revamp.zip