BuddyPress.org

You can’t do that in PHP. Well, actually you can – but you will break all the styling, as you will filter our header/footer.php files include. So basically it’s not a good idea.

The best idea – to use a child theme. You can than even switch to that child theme for specific pages on your site. One of the ways to do that: https://premium.wpmudev.org/blog/wordpress-different-themes-for-pages/

Another idea – do some magic with BuddyPress templates. It’s totally possible, but you will quite heavily modify them (that will complicate future maintainability).

Also it would be easier to help you if you provided a URL to your site.

see here:

Using bp_parse_args() to filter BuddyPress template loops

If it doesn’t work in your child theme functions.php, use bp-custom.php

Standalone because bbP is used separetely and not as group forum, which is a popular config when BuddyPress is activated. FYI (in case of):

Installing Group and Sitewide Forums

Create a template over-load of this file:
buddypress\bp-templates\bp-legacy\buddypress\members\single\member-header.php

In the overload, remove the span that shows the last_activity blurb.

They ARE. See https://codex.buddypress.org/activity-embeds/

@tranny,

turn off email notifications
https://buddypress.org/support/topic/turn-off-email-notifictions-in-functions-php/

limit friendship (premium)

BuddyPress Limit Friendship

This is outside scope of BuddyPress support as the login system is core WordPress. You may get better answers in the WordPress forums.

– you can add a condition for logged-in user on the directory template.
– for the menu itself, and specially if it is a wordpress menu like primary, you need to write a function. Here another tutorial for this. It’s similar to the other i’ve mentionned previously, but with more examples (including positionning and conditionnals).

wp_nav_menu()

wp_get_nav_menus()

And you can also open an enhancement ticket if you estimate this should be part of BuddyPress and not only WordPress.

@tranny,

dealing with spammers is a long run work, to not say a never ending work. There is no miraculous plugin or trick to stop them.
And even if you would be a genius coder creator of an extra super original spam shield, you could be sure to became target #1 of all spammers, because in this case, you would represent the absolute challenger of all code breakers !

Back to real life.

Most of updates spam comes directly into the DB. Bots are clever and don’t need to login to do that.
Some spammers are real people, and once they are logged, they do their stuff manually. These people can be isolated, but to do this, you have to find them in the user list. Which is absolutely not easy and time comsumting. And of course, this is not prevention but intervention, after you where spammed.

You could also track IP‘s, but again, this can be helpfull only AFTER you where spammed. But getting ip’s on admin user list is a great way to gain time. Once you have the IP, you can consult many anti spam sites who store any bot and user known to be attackers. And eventually ban them with this plugin.

For now, first thing to do is to clean your user list. Whatever suspect username, like a589xdf or special to BP, Bill UNERHOOD, can be eliminated. The first example use alpha-numeric digits, the second a very well formed first and last name. It’s extremely rare that normal users enter such credentials. In addition to this, you can check their email. Why would you, for example, have members with a polish email (@blogmedykamenty.pl) if you’re in New Zeeland and your site relates about pets ? In this case, you can raisonably doubt about an interest between medicaments and pets ! You can fire such user.

All this may be good and well, but you have also to hardening WP. This means using another table prefix as wp_ at very first. And second, to not use “admin” as user name. Never !
Read also @venutius tutorial

You have to clean out the existing spammers, unfortunately manually. And to avoid upcoming spam.

To calm down the bots – in case you receive dozen of spam daily, close all comments and deactivate notices and messages component in bp settings for 2 or 3 weeks.

Also, in case you’re on a dedicated server, you really need to enforce his security. But this is out of the scope of this forum.

I tested by switching my WordPress locale to da_DK and the dynamic timestamp is loading da.js correctly.

@adjunkten – If you want to help debug, can you add the following line:

var_dump( $locale );

after lines 31 and 42 of this file?
https://buddypress.trac.wordpress.org/browser/tags/2.7.0/src/bp-core/bp-core-cssjs.php?marks=31,42#L22

Your time stamps looks correct, I’m guessing you mean the Danish translation isn’t working correctly?

You can grab the newest Danish Buddypress translation here https://translate.wordpress.org/locale/da/default/wp-plugins/buddypress followed by merging your current buddypress-da_DK.po file in poedit like this http://www.marketpressthemes.com/blog/how-to-merge-two-po-files-using-poedit/, translate the words you needs to translate, save it as both buddypress-da_DK.po and buddypress-da_DK.mo – and reupload it to your server in your language folder.