BuddyPress.org

The link just goes to the page that it is on.
That’s what this does: bp_core_redirect( wp_get_referer() ) in bp_send_private_bzzt()

So a 404 indicates some other problem that I can’t diagnose, unless…

Did you try putting the code in bp-custom.php, per the instructions, instead of functions.php ?

You have to roll your own.
I got thru it awhile back with help from @r-a-y

https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/send-private-static-message/

https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/create-group-only-by-admin/

Our other site, wpebooks.com looks pretty simple & clean to me. We don’t use all the BP features and have private groups for support.

Whereas I can well imagine what prompts such an article, I’m not sure it’s apposite, The snippet ” I can only be honest and say not much has changed for almost a year” is a little unfair and a surprising comment to make really, a fair bit has changed over the last year and lets not forget A/ how complicated this kind of app is and B/ that there are only three core commiters to the svn trunk.

Of course I don’t want to judge Bowe’s post given I can only read a small section of it, I will however tend to agree that there has been a slow up in plugin development and perhaps the plugins authors have exhausted their honeymoon period with BP and are not able to devote so much time to it.

For the record I will point out once more just how much work is involved in coding and testing/debugging plugins and constructing themes- for those that are not aware – it’s a huge amount of time and we must not forget that this is an open source project despite WP’s involvement and all the work that is done is given freely all the long hours are given with little expectation of any return apart from the gratitude of the community – yes it’s true that some coders do manage to monetize their work too an extent but they are a small fraction of those that have contributed their work -. The pace of the project is governed strictly by the time that people are prepared or are able to put in, allied to that fact we have a situation where we have simply three core coders doing 90% of the work, these three all have paid jobs and are not able to commit to full time ( it’s surprising how much time is given though! ) on the project, understandably.

What I would wag my finger at and offer a generalised admonishment to is the wider community for it’s lack of direct involvement at any level. An open source project is carried by it’s community they drive it along and sadly I see very little participation from them, there are those that are pretty active in using BP have experience and knowledge yet are seldom seen on this site. There are many levels at which people can help, checking patches out and reporting back ( if one has a localhost dev environment ) reporting bugs to the trac system, adding to the codex which could really do with some tlc, many ways of contributing and at various skill levels we do not all have to be of the caliber of Boone, Paul or JJJ to help out and push things forward. ( oh and I consider myself one of those that could be helping more fwiw, time and pressure of earning a scant living though )

I have always been one who was vocal – at least early last year – when changes did need to be effected and things seemed to be in slight turmoil or turpitude, some of those changes came to be some didn’t , there are still many things that could be improved with this project and hopefully they might happen with time as for pushing for those things a lot has been said publicly and privately and there is little point going over old ground.

Thanks @nahummadrid, my SWT blog is ‘already’ private and since my SWT blog is also my main site that little trick makes no difference to what appears on the activity stream (which of course is also on the main site).

I can only assume most BP sites are not also running SWT otherwise there would be more debate (and potential solutions) availabe to help.

@doctordr You could make your SWT blog private or try this plugin https://buddypress.org/community/groups/buddypress-block-activity-stream-types/ I remember there is a way to block specific blog IDs from appearing in the activity stream but the plugin developer is no longer keeping up with this plugin and it appears his site is offline. there may be instances of the fix around here on the forums though.

I’m having this same problem but for all users, not just with special characters in their names. Any other suggestions? Thanks.

Hello , thanks for sharing it , does it display all images included the private one’s ?

glad to see that this got answered.

Don’t put the guilt on us, we are not obligated to help you on anything, this is a free forum, and your lucky your getting free support.

Second, the supposed of “problem” you are speaking of is not a bug or error at all with buddypress. Obviously, the Subject Line is Required, and the message can’t be sent without a subject. I’m sure there is a workaround I suppose if you don’t like it, but it will require some searching.

It’s hard to remove a post and let you see the response, so I’m closing this one. Please refrain from posting any further about this, it’s beginning to look like spam (this is the third post that I’m aware of, in the last few days). Heck, the title of this thread is the sort of thing Google’s going to pick up on, which I know is your intention.

In terms of people selling or advertising premium BuddyPress services on this site, there’s a balance between promoting your plugin in situations such as responding to a relevant topic, i.e. “how can I do x?” and you reply, “my premium plugin z can do that for you!” (which is okay), and outright advertising or spamming (which isn’t). Announcing a new premium plugin or theme is fine, but posting an announcement or advert each week isn’t — that’s spam.

Blatant advertising or spamming is not allowed; BuddyPress.org community support is about community support, it is not a free-for-all marketplace. This isn’t the place for that type of thing.

Specifically regarding your site, there are extra considerations. You appear to be re-selling GPL’d plugins and themes[1] (I have only taken a quick look at your site). As long as you had purchased these GPL’d themes or plugins originally, then you can turn around and give that theme or plugin to anybody you want. The GPL is about redistribution. My understanding is that this viewpoint is entirely correct.

However, I think you’re missing the big picture. It may not be illegal, but I don’t think it’s ethical. The authors of those works which you are profiting from worked hard to create something. By re-selling their works, I believe you are disrespecting those authors and the larger community. To me, it’s as simple as this: if this sort of behaviour discourages even one individual from creating a new BuddyPress plugin or a BuddyPress theme, because they’d like to try to make some money from it, then the community has been harmed by having one less choice.

I feel this threads falls between an announcement of a service and an advertisement for that service, considering your repeated posts, with debatable ethics. I apologise on behalf of our moderator team; we should have got in contact with you after your first post, and we’re sorry that it seemed we were picking on your posts. However, you could have posted another topic and asked what happened to your previous posts; we would have seen it.

I am paul@byotos.com if you would like to discuss further in private, or you’re welcome to start a new topic and start a discussion about the ethics of re-selling GPL plugins/themes, but maybe that sort of discussion would go best on the wordpress.org forums, rather than here, as it would be seen by a larger audience of WordPress plugin and theme authors (relevant, of course, because your site appears to have WP and BP-specific themes listed).

[1] This assumes that everything in those plugins/themes is covered by the GPL, such as images or any other files, as opposed to just the PHP source.

To prevent spam, the fonctionnality you want to use is not avaible. You can see tthe function in bp-messages-templatetags.php:522

Anyway you can add a button, which opens the send message page, but you need to add manually the user name.

Open from your_child_theme/groups/single/members.php
and add the function ` ` in the place you want.

You can also learn to your user to use the profile page of their contact to send them a private massage.
The number of click to do this is the same i think.

It’s your choice

Ok – so you’re going to your profile’s private message, compose; what type of search term do you enter in the name field? Do you get any autocompletion results (an AJAX script ought to be running)? Does the search term match up to a particular user?

Just trying to understand where it’s falling out. BuddyPress private messaging doesn’t use email addresses.

The private messaging doesn’t use the email addresses directly. I spent a bunch of hours this last weekend fixing problems with the private messaging system in certain situations involving differences between the user’s log in, and user nickname fields, and when the compat mode constant is set (I assume you have set this in your wp-config.php if you are logging in with email addresses — can you confirm?

Try adding `define( ‘BP_ENABLE_USERNAME_COMPATIBILITY_MODE’, true );` to your wp-config.php or bp-custom.php file.

Well that’s why I asked. Right now the logic tranlates to this:

“If this topic is not mine, or the user is not logged in, don’t show a link.”

You want it to say:

“If this post is mine, or the user is not logged in, don’t show a link.”

Here’s your new code:

`function bp_forum_send_private_message_link() {
echo bp_forum_get_send_private_message_link();
}
function bp_forum_get_send_private_message_link() {
global $bp, $topic_template;

if ( bp_get_the_topic_post_is_mine() || !is_user_logged_in() )
return false;

return apply_filters( ‘bp_forum_get_send_private_message_link’, wp_nonce_url( $bp->loggedin_user->domain . $bp->messages->slug . ‘/compose/?r=’ . bp_core_get_username( $topic_template->post->poster_id, $topic_template->post->poster_nicename, $topic_template->post->poster_login ) ) );
}`