BuddyPress.org

@louisarthur – Thanks for sending me credentials. I’ve logged into your site to have a look.

As you note in your email, there’s no href attribute on these links. It’s not clear to me how this would be the case, but I can give you a starting point for looking into it yourself. Briefly, the buttons will be built without an href if the button constructing function passes an empty link_href parameter to the BP_Button class. The functions used in the two cases are different:

Message public: https://buddypress.trac.wordpress.org/browser/tags/2.9.2/src/bp-activity/bp-activity-template.php?marks=3090#L3079

Message privé: https://buddypress.trac.wordpress.org/browser/tags/2.9.2/src/bp-messages/bp-messages-template.php?marks=1362#L1360

The logic in each case is different, but since neither is showing up, I’m guessing that one of two things is happening:

1. One of the conditional checks shared between them is failing for some reason: bp_is_my_profile(), is_user_logged_in().

2. Something on your installation – perhaps your theme but probably a plugin (since you said Twenty Seventeen was exhibiting the problem as well) – is filtering both ‘bp_get_send_private_message_link’ and ‘bp_get_send_public_message_link’, and then incorrect returning empty strings.

To test idea #2, you might try – if you can – searching through your codebase for those filter names.

Hi @chhayaparikh1963 – Thanks for the post!

I agree that the ability to post from the front end would be a good improvement for BuddyPress. It’s a bit complex to think about how it might be developed for BP itself, since it’s likely that many BP sites will want the feature implemented in different ways: limiting permissions to specific kinds of users, linking groups to sites within a multisite network, specific taxonomies for posts created from particular front-end contexts, etc. That being said, it’s something that’s long been on the radar of the BP development team. A recent ticket that outlines the issue is https://buddypress.trac.wordpress.org/ticket/6736

In the meantime, I know you said you have checked out all the third-party plugins, but I will say informally that I’ve had pretty good luck with BuddyForms. https://themekraft.com/buddyforms/

I wholly agree with the sentiments of the guy who posted this.

I think bbPress and BuddyPress are, frankly, appalling offerings to ordinary WordPress users.

They may well be excellent tools for developers, but they are the most user-unfriendly bits of software I have encountered in WordPress. Indeed, they make me wonder whether WordPress is for users anymore, rather than professional developers.

It simply should not be this complex, and dismally supported, to have a forum on WordPress.

I agree wholly with the view that there should be a premium paid-for service with a solution aimed at WordPress users – that is people who create editorial and run a site. Not the professional developers, who can look after themselves.

It does not surprise me that outfits like Wix are growing given this direction of WordPress. If it is for developers only – who hone their marketable skills doing this stuff – then fine.

For an ordinary user, who is not totally useless on WordPress, I have found this BBPress / BuddyPress combination utterly toxic and a waste of time.

WordPress has a built-in function for getting the number posts published by a user:
https://codex.wordpress.org/Function_Reference/count_user_posts

If you’ve been able to figure out how to display profile data, use the same approach here, and you should be in good shape.

This is probably a server configuration problem. This simple plugin can help you figure out if your WP installation can send emails:

Check Email

Alternatively, the emails may be being sent, but ending up in your users’ spam folders.

Ajax calls need access to wp-admin.
You’ve blocked it so the ajax calls will not work.
And you see that in the areas you’ve mentioned.

You’ll need to add this conditional to your whitelist check:
wp_doing_ajax

Something like: if ( ! is_admin() && wp_doing_ajax ()) {

Hi @VentureCore-

It seems like you can make avatars work remotely. Check bp_core_fetch_avatar() for some filter opportunities. https://buddypress.trac.wordpress.org/browser/tags/2.9.2/src/bp-core/bp-core-avatars.php#L98

I’ve not done what you’re trying to do, but it seems that the filter points bp_core_avatar_folder_url, bp_core_avatar_folder_dir could be useful, but there’s a filter on the final result at bp_core_fetch_avatar for the “html” output version and bp_core_fetch_avatar_url for just the url.

Cover images should actually be easier to manage. Take a look in https://buddypress.trac.wordpress.org/browser/tags/2.9.2/src/bp-core/bp-core-attachments.php#L28

Alternatively, you could filter the other plugin to ignore avatar and cover image requests. Lots of ways to solve this, I’d bet.

What about using a custom member front page? Then you’d have total flexibility:
Custom Front Pages for your users profiles

Otherwise, I think you could conditionally filter bp_displayed_user_get_front_template to specify members/single/activity.php for self and friends and members/single/profile.php for non-friends. See this function:
https://buddypress.trac.wordpress.org/browser/tags/2.9.2/src/bp-members/bp-members-template.php#L1397

Ha. Yes, this is an old and annoying issue in WordPress and WP plugins.

That said, we have done extensive work in the past to ensure that quotes are stripped where necessary throughout various interfaces. If you can share more detail about exactly where you’re seeing the slashed content, we may be able to help figure out where things are going amiss. For example, you say that you’re seeing this in the activity feed. But in what context? Is it when you type something directly into the “What’s new” box, or when something is syndicated from elsewhere on the site? Are you seeing the slashes when you refresh the page, or only when the content is returned from the database?

Hi @mycraze – It sounds as something is failing to load the jquery-cookie script. BP attempts to do it in the function bp_core_register_common_scripts(): https://buddypress.trac.wordpress.org/browser/tags/2.9.2/src/bp-core/bp-core-cssjs.php?marks=54#L18

The first thing to check is to see whether the page is attempting to load the script in the first place. View the source of the page, and look for a tag that looks something like this, in the document head:

<script type='text/javascript' src='http://example.com/plugins/buddypress/src/bp-core/js/vendor/jquery-cookie.js?ver=2.9.2'></script>

If you *do* see this, but are still having the problem, try the following:

* Load the script URL directly in a new tab. Does it load?
* Open the Network tab of your browser’s developer tools. Is the browser unable to access the file for some reason? Perhaps a 404 or some other error?

If you do *not* see the script tag, then it’s a server-side issue. My guess, in this case, is that you are using a third-party theme that loads the bp-legacy JS file without also properly declaring the dependencies. To verify, switch to a default WP theme (like Twenty Sixteen) to see if the problem clears itself up. If this is the problem, you may want to talk to your theme author, or share the relevant code from the theme (probably looks like wp_enqueue_script...) and we may be able to help you correct it. In the meantime, you may be able to work around this problem by manually enqueing the cookie script in your functions.php file. Something like:

add_action( 'wp_enqueue_scripts', function() {
    wp_enqueue_script( 'bp-jquery-cookie', buddypress()->plugin_url . 'bp-core/js/vendor/jquery-cookie.min.js', array( 'jquery' ) );
} );

Hi @redcompolitica – I’ve built multi-page registration processes for clients in the past, but unfortunately, it’s not very easy to do – BP’s registration system is not built in such a way as to make it easy.

If your main goal is to make registration less overwhelming, you might consider moving some or most of your registration fields out of the “Base” group. This will mean that they don’t show up during the registration process, and users will have to fill them in by editing their profile after signing in.

If your goal is to have *conditional* registration steps – where, for example, step 2 depends on a specific value provided in step 1 – then I’m afraid it’d have to be custom-built. Much of the work could be done with a custom theme template members/register.php and by modifying the way that registration data is saved and validated https://buddypress.trac.wordpress.org/browser/tags/2.9.2/src/bp-members/bp-members-screens.php?marks=113#L72

Some Trac tickets that are somewhat related that you might want to follow:
https://buddypress.trac.wordpress.org/ticket/1842
https://buddypress.trac.wordpress.org/ticket/4278

Good luck with your project!

Hi,

just for your information, we’ve created a plugin which remove the password confirmation in the registration form:
https://wordpress.org/plugins/nopassconfirm/

Test it and tell us if that works fine for you!

Olivier

No sure if this was others’ experience, but for me the description duplication does not happen when tested with a WordPress theme. I just submitted a request to SeventhQueen regarding this, while using their “Kleo” theme.

BuddyPress uses a theme compatibility layer, meaning it uses its own templates that are designed to drop into any theme. You can overload all kinds of template parts for BuddyPress:

Template Hierarchy

However, there are plugins (I’ve not tested) that you could maybe get to work if you have two themes in mind: https://wordpress.org/plugins/jonradio-multiple-themes/

Best,

-David

This is sort of a big WordPress question that lots of people would like to change, but it’s not that easy. You could try using the plugin Theme My Login, which would need to be applied carefully, as it overlaps with BP a bit. https://wordpress.org/plugins/theme-my-login/ (I have no idea if this is a good plan, you’ll just have to try it.)

The black bar across the top is a WordPress per-user preference “Show Toolbar when viewing site”. There are many resources on the web about how to disable it/change the behavior:
https://www.google.com/search?q=wordpress+disable+toolbar+for+subscribers

You can save extra things manually on the bp_core_signup_user hook:
https://buddypress.trac.wordpress.org/browser/tags/2.9.1/src/bp-members/bp-members-functions.php#L1900

But I imagine that the simpler answer would be to use Profile Fields. If you add profile fields to the base group, then they appear on the registration form and are saved at signup. https://codex.buddypress.org/administrator-guide/extended-profiles/

Best,

-David

Hi moefahmy,

Just registered my first WordPress.org account since over hundreds of sites I’ve built in the past, hehe. I’m facing exact the same issue as you have. I seriously thought that BuddyPress would support features like this. In the wp-admin > Groups > Single Group, there’s even an option that says: ‘Who can invite others to this group?’, WHY is this option available but not ‘Which usertype can post to this group? e.g. Administrators, Moderators, Subscribers etc.’.

Is there a plugin that anyone in this community is aware of which handles above feature? I really need a feature to assign posting permissions to users or userlevels…

Hey! I am using the plugin: BuddyPress Docs. You can create Wikis and upload docs inside the groups.
https://wordpress.org/plugins/buddypress-docs/

“Part wiki, part document editing, part shared dropbox, “

It is working, but I would be interested too if there is a better solution..

Hi @paksunny-

#1 can be accomplished by adding this code to you bp-custom.php file (or wherever you keep your customizations): https://gist.github.com/dcavins/c65f3856dd6ed5be37eef115ab09405a

#2 Try this plugin: https://wordpress.org/plugins/buddypress-private-message-for-friends-only/

-David

It sounds like you need to change/update your permalink structure for your WordPress installation. Visit wp-admin > Settings > Permalinks to update.

-David

follow these instructions for a free way : https://www.en.suaralo.com/allow-user-wordpress-frontend-post/