BuddyPress.org

If I understand properly, you need conditional profile fields. Try BuddyDev’s Conditional Profile Fields for BuddyPress.

Conditional Profile Fields for BuddyPress

Ah, interesting.

1. If you’ve got access (through the mysql command line tool, or through PHPMyAdmin, check the character set and collation https://makandracards.com/makandra/2531-show-the-character-set-and-the-collation-of-your-mysql-tables There may be something funny going on there.

2. Do you have the same problem with other content? Can you…[Read more]

It’s not possible to use a regular BP profile field to keep track of data changes over time. BP doesn’t keep records of old profile field values – it only stores the most recent one.

There are a number of ways you could accomplish it. If you had the technical know-how, you could build a tool that hooks into XProfile and syncs user-entered data to…[Read more]

Be sure you’re looking at the View All tab.

Some things to check:

1. Check the timestamps at Dashboard > Activity. Are they off as well?

2. Are in timezone UTC-5 (US Eastern)? Just so we have a better understanding of what’s going on.

3. You say the “server time” is “set correctly”. Can you say more about what this means?

4. Are timestamps for WP content (like posts and comments)…[Read more]

I have the same problem.
Look in the right column of my register page

When I change to Twenty Seventeen the duplicates disappear, though. Do you see this as well, @aubreyw?

I use a child theme of GeneratePress. How can I correct this duplicate issue in my theme?

You can pass user IDs into bp_has_members() like this:


$custom_ids = my_custom_ids( 'country', 'usa' );
$has_members_args = array(
'include' => $custom_ids,
);
if ( bp_has_members() ) {
...
}


@grimbot – When you swapped out the header.php file for the original, did it fix the AJAX problem you’ve described here? It’s likely that it’s unrelated, but worth checking.

> Perhaps something with the .httaccess files?

Unlikely – mods to the .htaccess file might prevent the call from going through in the first place. This AJAX call is…[Read more]

BuddyPress’s Register page is a special kind of page that cannot be edited via the Dashboard. That’s why it’s blank when you view it in the normal way.

To add additional fields to the registration process, go to Dashboard > Users > Profile Fields. Add one for Address and one for Phone Number. Make them required and/or private, if you’d like. As…[Read more]

Can you share a screenshot? (Upload to https://postimg.org/ and share the URL to the screenshot.) Seeing how the fields are rendered may give a hint as to why this is happening.

It may also be worth switching to the Twenty Sixteen theme momentarily (or some other WP default theme) to see if it solves the problem. If so, you can narrow it down to…[Read more]

If you’re able, search your codebase for the string. It *must* be there somewhere. If you have SSH access:


$ grep -nR "Please upload your profile photo to start using this site" wp-content/plugins


Repeat for mu-plugins and themes.

When you add BuddyPress’s Register item to your nav menu, it will only show up for logged-out users. If you’d like it to show for *all* users, remove the BuddyPress item, and instead find Register under Pages and add it from there. https://i.imgur.com/Ny7Wj1L.png

the word from me and my tech team:

“it’s either Bill Gates or gremlins”

• i do not have this setting set anywhere.
• i do not have plugins installed that would cause such functionality.

the only plugin i have that has the word “force” in it is “force regenerate thumbnails,” which was quite useful…

i deactivated it just now…

My suggestion was to try another plugin. That’s a relatively low-risk proposal 🙂

For the record, I understand the frustration – piecing together many different plugins and tools, written by many different people, can sometimes have unpredictable results.

Very odd. It sounds like, when you initially installed BP (or activated the Groups component), it didn’t properly install the database tables. I have not seen that happen before, but I’m glad that toggling the component resolved it.