Thank you for the forum posting. Appreciated.
Some quick notes for you regarding the topic at hand. For as long as I’ve been in charge of the plugin, the plugin hasn’t blocked access to the site as a whole. It only blocked access, in tiered levels, to the BuddyPress areas of the website.
The first level is “read-only”. They can see the areas, but the UI used to actually comment/interact/etc was hidden.
Second level, which is the “private network” option, does not even allow read-only of the site. It limits the user to their BuddyPress profile only, but only when trying to access BuddyPress areas. It would not restrict the user to their BuddyPress profile if they try and access a single post in the blog area.
Hope that clears up some questions and/or confusion, but feel free to ask some more questions, and I’ll answer the best I can.
In my opinion that is not a very good answer. The person that posted this made a real clear example of what they wanted to know.
So please re-read the question.
Is it possible to do what they are asking? Yes or NO? If yes, how can new registrants be approved first before having access to the page?
Thank you
jadams1974,
I stand by my answer, as I explained the settings we offer and how it works in the present form. In order to enact the restrictions, we’re relying on the user being fully created and in the database, and we flag them as not approved right away, until an admin approves them. We utilize user meta to check on the approval status and reject or allow based on that plus the chosen restriction settings. We don’t cover the entire site, just the BuddyPress and some bbPress areas.