@sbrajesh Perfect! Thank you – this is a very important feature to support the user experience on our site. (FYI, In WP when I click on details for this plugin I receive a gateway error.)
@prashantvatsh in a quick check I see that Jetpack is likely the problem. I have turned off allowing WP users to login with another account. In the users list, there is a jetpack symbol that alerts me that a couple others in our group may have been logging in this way which means missing information in our membership directory that would have otherwise been collected at registration (ex. name). Thanks for your assistance and I hope this resolves it!
@prashantvatsh Loco translate appeared to work on my own testing with a typical new account registration and activation, but the snippet of code did not prevent someone from bypassing account activation if using another WordPress account to login. The tester mentioned logging in with the other account (apparently no registration required in this case) and seeing a jet pack process accept them. I am not sure jet pack had anything to do with this and wonder if you have other suggestions. I hope to test in real-time later today to better know what is happening.
@prashantvatsh Thanks very much. I am not a programmer so have a simple question – in which file does this code go, and where in there? Am I correct in thinking this will require all registration requests to be activated manually by me? Since my post I have learned that someone was able to bypass activation and join the site by using an existing WP account at login. Is there a way to remove that option or will this code be best?
Can you provide more context about how to find the text that uses the Loco Translate plugin, and how this plugin relates to the dynamic BuddyPress registration text? I appreciate your help. Thanks.
@shanebp Thanks for your tip. Will BP Simple Private plugin allow me to make non-BuddyPress pages private, for example, an existing content page that is not part of BuddyPress?
