BuddyPress.org

Ah, just found out that this plugin causes a conflict with BuddyPress Group Extras, so avoid it, by the looks of things it’s unlikely to get fixed anytime soon.

Yes it’s different and ?
And this is how to use what i already suggested

function users_last_activity() {
$user_id = bp_displayed_user_id();
//$activity = bp_get_user_last_activity( $user_id ); // raw date/time
$activity = bp_core_get_last_activity( bp_get_user_last_activity( $user_id ), __('active %s', 'buddypress') ); // ago format like on members directory

	if( bp_is_active( 'activity' ) ) {
	 echo $activity;
	}
}

// testing the result on profile header
add_action( 'bp_profile_header_meta', 'users_last_activity' );

Hi,

all details here:

Participate and Contribute

The fastest way to get in touch with the devs is to use the BudddyPress chanel on Slack.

Clients requiring many things ! Some can be done, some not. It’s to you to explain them that it’s not possible. Or only with a very huge additionnal budget. This argument is mostly the best to opposite to an obtuse “i want this feature”. Diplomacy, diplomacy… 👿

1) You count the number of avatars on the widget ! Or something like this. 😉
2) who’s online refreshes after 5 mn. See https://buddypress.trac.wordpress.org/ticket/3590
3) try with bp_get_user_last_activity()

Also wp-content\plugins\buddypress\bp-members\classes\class-bp-core-whos-online-widget.php

If I leave the registration and activation pages blank I get a warning all the time in the backend.

The warning won’t cause harm but I agree you should be able to dismiss it. You could open a ticket on Trac for the core developers to take a look at?

https://buddypress.trac.wordpress.org/

Hi @dphelun,

– 1) no idea ! It depends of what you know about WP and BP, coding and templating
– 2) see 1…
– 3) in theorie yes. In real life… check the forum… and point 1.

Don’t buy a theme before you tested your project with all plugins and fonctionalities correctly working on a WP+BP default install. Use one of WP’s default theme, ie. Twenty Sixteen or Fifteen. Or even all coming with WP

This tests should be done on a test site (locally or online, but not on a production site)
Default install, because it’s the only waranty for you and the project to work properly in a respecfull environment of WP standarts. Once ok you can jump to a premium theme if you estimate it is worth. That said many free themes are just ideal too.
I would just warn you to avoid frameworks and page builders- specially because BP doesn’t use WP pages like WP does. Focus on the theme itself, and not on plethoric theme functionnalities. Theme is for layout. Plugin is for functionnality.

About Themes
you will find a lot of themes on the net. Most with nice pictures and impressive list of functionnalities and prices. Problem is that this marketing arguments rarely fit with a project. And if you’re unable to customize it, you go towards weird issues and will be lost in no time.

About plugins
Like for themes and of course your technical level.

From what you tell, i would consider WP Job Manager and his (premium) add-on for BuddyPress.
Messaging is included in BuddyPress, even if it is not exactly meant as instant messaging.

But test the message component first as is before going further. And keep in mind that less is more.

– I know nothing about Loco translate as i never used it. And i can’t read chinese, so i can’t help you with this specific translation.

– I never seen a error 500 after modifying a translation.

– The only thing i’m sure (because of the error messages) is that it is Loco who doesn’t find a file or can’t access to it properly.

– Re-check Loco Settings and try another path option… Or maybe use a custom path called MyTranslation and use the plugin only to translate. Once done, deactivate Loco and move the mo file manually to the right folder. By doing this you eliminate the eventual plugin issue and still have a mo file you can use (hopefully).

– Ensure your BP’s po/mo files have correct file extension and use the correct path to file:

/wp-content/languages/plugins/buddypress-zh_CN.mo & buddypress-zh_CN.po

Personnaly, i use poEdit and only on my computer and never directly on a site.

Hi,

you are on the BuddyPress support.
bbpress questions should be asked on bbpress support.
And as you use Loco Translate plugin, and apparently have an issue with it, you have to ask on the LT plugin support.

To get more about chinese translation, help and much more, please read the Polyglots blog.

Hi,

all you have to do is to use a custom translation for BuddyPress !
This can be done with help of this plugin.

Actually, WP uploads automatically all available translation for itself and any of his dependencies: themes and plugins(when exist) accordingly to the site language. Ie. brazilian portugue (pt_BR.mo)

In your case, while using the plugin, WP will remain in portuguese and as you will use buddypress-en_US.mo or buddypress_en_GB.mo as custom translation, anything related to BP will be in english.

Of course, this behave will always be used even AFTER an update of WP or BP and both updated to portuguese.

The avantage of the plugin is that you haven’t to struggle with complicated domain settings and hacks, because he does it for you by using a different path for any custom translation (in your case, BP’s english version). The file is stored in /uploads/wpt-custom-mo-file/buddypress-what_EVER.mo

You simply need to remember to download manually the english BP version.
Translation files can be downloaded here.

Hope to be clear. 😉

Hi Earl,
Two things you can do:

1. Hide admin user from members list. This post has some answers:- https://buddypress.org/support/topic/hide-admin-from-members-and-activity/
2. Change the user_nicename field in users table in database, for the admin user.

I suggest going with the first option.

I have this combination of plugins working on one of my website, it works just fine. in terms of registration, I set buddypress registration page to none and created some custom registration pages for PMP.

As it is working, you can’t expect a fix. 😉 (see #6112) If you think you have found a bug, open a ticket and give any details to recreate the issue: theme name, used plugins, php version.

Have you tried to create an error ? When you’re sure that a notice should appear, and you don’t see it, check first the source of the page (right clik – page source). Sometimes you’ll find it in the code but something avoid it to appear on the screen.