BuddyPress.org

In your above code you’ve used author_avatar to update so you’d just use that again to retrieve.

You can use get_user_meta() for that.

Great to hear that @tonydjukic

Just to point out, I seem to have got @johnjamesjacoby‘s username wrong in my comment above. He seems to be @jjj everywhere else, just not on this forum 🙂

all i want to know is how the avatar are set in the user meta

Is this related to the datebox stuff, or separate?

In that case, I think your code should be working. The problem is most probably elsewhere.

Have you checked in the db to make sure the profile data has been set? The issue could be how you’re displaying it at the front-end.

The Template Tag Reference will help you here. You can do things like the following inside your function to determine the type of page that is being accessed:

if ( bp_is_groups() ) {
// This is the groups page.
}

if ( is_buddypress() ) {
// This is a BuddyPress screen.
}

What did you get when you used var_dump()?

Even though the plugin hasn’t been updated for 2+ years, it’s built by @jjj (BuddyPress project lead who knows BuddyPress inside out) so it will be well-written. If you do spot anything, open a support ticket on the plugin’s forum.

How are you getting $user_id? You should show us all of your code. My advice is to dump stuff to check where you’re going wrong. For example:

var_dump( $user_id );
var_dump( $randDate );

Closing as a duplicate

Hey @alessandrat

Welcome to the BuddyPress forum!

1. Have two separate front ends for different user types (with differently configured profiles), appearances, and accesses.

Yes. This can be done with either a plugin (try searching the Plugin Directory) or coded through the Member Types feature introduced in version 2.2.

2. Have a place where…

[Read more]

$handle is simply a name you give your script. I chose my-custom-js but feel free to use any string you like. custom-script or maelga-js are both suitable alternatives.

You could create a .js file in your child theme which you could use for all of your custom JavaScript. You’d then enqueue it with the following code (which goes into your child theme’s functions.php):

function my_enqueue_scripts() {
wp_enqueue_script( 'my-custom-js', get_stylesheet_directory() . '/js/script.js', array(), '1.0.0', true…[Read more]

Only for components that have a directory. Also, you will need to do that for the “register” and “activate” pages (this is all done via Settings > BuddyPress > Pages).

You could use the setTimeout() JavaScript method for that:

function delay() {
id = window.setTimeout(rm, 500);
}
function rm() {
// Remove the notice from the DOM.
var e = document.getElementById("id_of_the_notice");
e.parentElement.removeChild(e);
}

Note:

500 (milliseconds) can be changed.
id_of_the_notice must be changed

In the area titled Directories, only 3 components are shown. The opportunity exists to assign Pages to those 3. But what about the other 6 components I chose?

Not all components have directories. Take friends for example, that component doesn’t have a directory. However, members, groups and activity do.

Of course, sorry. Glad you figured it out 🙂

$ud is a WP_User object of the person who is receiving the message. So:

function filter_private_message_email_body( $email_content, $sender_name, $subject, $content, $message_link, $settings_link, $ud ) {

$email_content = sprintf( __(
'Dear %1$s,
%2$s sent you a new message:
Subject:…[Read more]

@startershut

You should ask on the plugin’s support forum. Also, something that might be of interest to you, there’s a new invitations API in progress. See #6210.