[angrywarrior]

You need to tweak the code for both create.php and group-settings.php @skyb
I try to post details more when I have time.

[angrywarrior]

Guys @ I’ll try to post a solution when I find time for it. I do have the code for it. It’s a bit old but should still work.

[angrywarrior]

@imath reporting in this person or bot(?)

@lucydevid = Spammer

See the post above..

[angrywarrior]

Thank you @djpaul.

However after reading and reviewing the threads you linked I cannot see anyone of you guys mentioning “user data pseudonymisation” which is required by the GDPR, while encryption is not. Encryption of the DB data is just highly recommended by EU GDPR regulation.

[angrywarrior]

How about Pseudonymisation and encryption of user data in BuddyPress?

As I understand this must also be achieved under the GRPR directive.

(And yes thank you @buddyboss for your initivite, it is step in the right direction).

[angrywarrior]

Hi @dcavins

Thanks for your reply.

Actually the private forums do show up in that list too when you make updates in them.
Is there any way you could turn the whole shabang off so no updates are shown in the root forum?

kind regards
AngryWarrior

[angrywarrior]

Right thanks @derrickhall.

So is there any Buddypresss admin/dev that could jump in and help out with how to disable that?

It´s really a privacy concern and issue because groups are somewhat a private entity and updates should stay inside the groups themselves and not be spammed in the general forums update stream.

Thanks!

[angrywarrior]

Thanks @dcavins for your advise, but that is not a option for us a we run a new public service so it is open for anyone to join and create.

However we have found a solution which is editing the admin.php and removing the code part that displays this option in the groups settings.

I will stop probably 99% of all users and left is only very advanced users that would craft such URL I guess?

On a sidenote:
I think it would be good if you guys that are part of the BuddyPress Team would consider adding an option in BP back-end setting to be able to enable/disable groups types eg. hidden groups and maybe private to give people more control? Well at least hidden groups.

Thanks!

Kind regards
AngryWarrior.

[angrywarrior]

Thanks for that link!

However i seen it and the code is pretty old – over 5 years.
So I’m looking for if there is better more updated/current code.

Also what i forgot to say was that if applicable then completely disable hidden groups for users, but for admin/super admin maybe allow it for use of internal staffing purposes. There could be a benefit in that configuration for administrative company tasks.

Thanks!

Kind regards
AngryWarrior.

[angrywarrior]

Sorry for my extremely slow reply @leog371 and thank you so much for the help!

i wish you a wonderful day. 🙂

Kind regards
AngryWarrior.

[angrywarrior]

Right, thank you @leog371! 🙂

[angrywarrior]

Thanks guys, so where/which file would you apply this code?
In the create.php file?

[angrywarrior]

I’m still having issues with this. Not one single person here that has an idea what could be wrong?

[angrywarrior]

Omg that is so awesome, @danbp you are a genius! 🙂

That really worked!!

Thank you so much, that saved me like a big bunch of time..

[angrywarrior]

Thank you @henrywright!

I was hoping there was a more simple solution, but obviously there isn’t, so it’s time then to get the hands dirty.. 😉

Have a great day!

[angrywarrior]

Thanks!

[angrywarrior]

Nevermind – I have found a solution.

Thanks anyway!

[angrywarrior]

I’m still having this isssue.
Anyone got a clue to what could be wrong and how to fix this?

Thanks!

[angrywarrior]

I do wish to have it running network activated and It also becomes network activated when I do it.

But I cannot figure out why it is generating these error where it claims that buddypress pages are missing, when they are not. As described before everything looks good on the buddypress website itself, it on the other websites in the network that this error pops up and claims that pages are missing.

[angrywarrior]

That constant tells the WP installation not to load depreciated BP code as it unnecessary to load invalid code, which makes logical sense.

It has no effect on the rest of the install. I is not part of the issue I am describing above as the issue persist without the constant.

Thanks for your comment and thought about it though!

[angrywarrior]

Thanks for the reply Danp!

Well the WordPress installation is running as a wordPress multi-site and the I have setup BuddyPress as of the manual you mentioned above.

/* BuddyPress */
define ( 'BP_ENABLE_MULTIBLOG', true );
define ( 'BP_ROOT_BLOG', 5 );
define ( 'BP_IGNORE_DEPRECATED', true );

But I’m not sure what is wrong..

[angrywarrior]

Isn’t there anyone here on the buddy press forums that knows about this issue?

I t would really be nice to get some help or point in the right direction on how to solve this issue..

Anything is very appreciated..

Thanks a lot in advance!!!

[angrywarrior]

If you allow your site admins to control the privacy settings, then they will also have a separate admin menu in their control panel too.. Otherwise you control from your super admin what is allowed or not..

[angrywarrior]

You set the permissions levels for each site owner/level in it.

See the screen shot below:

This is the default settings which you configure in the network super admin on your multi site.

(Right click the image and open it in a new tab to se it in full size)

[angrywarrior]

Take a look at this:

https://premium.wpmudev.org/project/sitewide-privacy-options-for-wordpress-mu/
Its a premium plugin though, but it will do the trick. I’m using it myself with success.