[@boonebgorges Keymaster 15 years, 6 months ago]

Hm. Try installing http://teleogistic.net/code/buddypress/bp-group-management/ and see if you can get to the group that way.

[@boonebgorges Keymaster 15 years, 6 months ago]

Unfortunately, from the BP end, the only way you can do this is to give users super admin privileges. This will improve in future versions of BP, but for now that’s how it works.

You might be able to finagle something on the Dashboard side. I believe that WP also requires you to be a Super Admin to spam users, but there are custom role plugins for WP (I think https://wordpress.org/extend/plugins/role-scoper/ will do it, but others can correct me) that will let you, say, allow Editors to mark users as spam, or to create a new role for that purpose. They’ll have to do it from the Dashboard, but it should work.

[@boonebgorges Keymaster 15 years, 6 months ago]

Where are you trying to create new members? On the Dashboard? Are you sure that the user is not actually being created?

[@boonebgorges Keymaster 15 years, 6 months ago]

As long as you are logged in as the site admin account, you should be able to access the group admin area, where you can delete the group.

[@boonebgorges Keymaster 15 years, 6 months ago]

@nit3watch Thanks for the message, and thanks for sharing the theme. I can’t wait to check it out.

[@boonebgorges Keymaster 15 years, 6 months ago]

It’s a bit unintuitive, but forum activity items happen in bp-groups.php groups_new_group_forum_post() and groups_new_group_forum_topic(). (It’s because all forum posting happens through groups.)

I haven’t seen this particular text encoding issue before. What language are you posting in?

[@boonebgorges Keymaster 15 years, 6 months ago]

WP has a function add_query_arg() that works for this purpose. See https://codex.wordpress.org/Function_Reference/add_query_arg

You might also be able to save a bit of time (or at least make your code a bit shorter) by using paginate_links() https://codex.wordpress.org/Function_Reference/paginate_links

[@boonebgorges Keymaster 15 years, 6 months ago]

It’s not entirely clear how you would integrate this into BuddyPress itself, since every installation will have different “links” between profile fields. What kind of interface would be used to allow site admins to dictate such dependencies? If anyone is interested in providing a patch, or building a plugin, it might be worth looking at something like Drupal to see if they’ve implemented similarly dependent metadata fields, and how they’ve done it.

[@boonebgorges Keymaster 15 years, 6 months ago]

It’s not so much an “issue” as it is a feature of the way things work in BP. The activity action (“James posted a new forum topic…”) is saved directly to the database; it is translatable at the time of creation, but after that it is a literal string in the database and cannot be translated. This may be changed in the future, but for now, there’s not a straightforward way to fix this. (You could build a filter to do the replacement on a language-by-language basis)

[@boonebgorges Keymaster 15 years, 6 months ago]

@chouf1 – Can you tell me where there are javascript messages that are not being translated? All javascript in BuddyPress is supposed to be localized (though it does use a different technique from __() and _e()); anything untranslated is probably a bug.

[@boonebgorges Keymaster 15 years, 6 months ago]

To hide something from non-logged-in users, surround it in is_user_logged_in() checks, like so

if ( is_user_logged_in() ) {
\ stuff that only logged in users should see
}

[@boonebgorges Keymaster 15 years, 6 months ago]

I’ll bring the marshmallows!

[@boonebgorges Keymaster 15 years, 6 months ago]

BP 1.3 *is* coming – it will not be another nine months. But we have hit some tricky bits, and the core development team has not had an infinite amount of time to volunteer to pushing BP 1.3 along. If you are a developer (or even a savvy user who can test patches or verify bugs), and if you have an interest in seeing 1.3 come along sooner rather than later, head over to http://trac.buddypress.org and start sifting through this report in particular: https://trac.buddypress.org/report/11 The more contributions from the community, the faster things will move along (and the more love and friendship we well all have for each other, <img src="smileys/heart.gif" width="" height="" alt="<3" title=" kumbayah <img src="smileys/heart.gif" width="" height="" alt="<3" title=")!

[@boonebgorges Keymaster 15 years, 6 months ago]

Possibly related: https://trac.buddypress.org/ticket/2642

Are you by chance making some sort of change (either manually or through a plugin) to the user_nicename or user_login fields? Or are you using spaces in your usernames?

[@boonebgorges Keymaster 15 years, 6 months ago]

That definitely should not happen. Are you running any other BP-related plugins that might be causing a conflict?

[@boonebgorges Keymaster 15 years, 6 months ago]

Forum-specific notifications are not, at the moment, part of BuddyPress’s core functionality (for better or for worse).

@johnjamesjacoby has promised an upgrade of buddypress.org soon. Maybe one of the things we can hope for is that he’ll install something like the BuddyPress Group Email Subscription plugin, so that individuals can subscribe to group/forum emails.

Until then, you’ll have to check manually

[@boonebgorges Keymaster 15 years, 7 months ago]

Sweet!

[@boonebgorges Keymaster 15 years, 7 months ago]

Probably the most efficient way is to do something like this (not beautiful to put in a template file, but functional and lean):

`

Occupation:

`

[@boonebgorges Keymaster 15 years, 7 months ago]

Adding bp_adminbar_notifications_menu() in your header will probably work (as long as it’s nested inside of a `

` element), but you will need to modify the styles. You can go in one of two directions.

One, you can try to bring over the styles from bp-default/_inc/css/adminbar.css. You can import that entire stylesheet into your child theme with this line at the top of your child theme’s style.css:
`@`import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );
(See https://codex.buddypress.org/theme-development/building-a-buddypress-child-theme/ for more info on BP child themes.) The downside of doing this is that, depending on your theme and the element in which you’re trying to nest the notifications menu, you’re going to have a really hard time getting it to look good with your theme.

The other method is to skip bp_adminbar_notifications_menu() altogether. Instead, copy the entirety of that function from bp-core/bp-core-adminbar.php into functions.php of you child theme. After you’ve copied it, change the name of the copied function (to something like wwday3_adminbar_notifications_menu() – it doesn’t matter, you just have to avoid duplicate function names). Then – and here’s what will make your life easier – change the markup, and in particular the CSS selectors (classes and ids) being produced by the function, so that it matches the CSS selectors in the existing dropdown menus you’re trying to integrate with. Then, in header.php of your child theme (or wherever you’re currently trying to call bp_adminbar_notifications_menu()), make sure to call this new function instead.

[@boonebgorges Keymaster 15 years, 7 months ago]

Ha ha. http://teleogistic.net/donate/ if you *really* want to buy me a beer

[@boonebgorges Keymaster 15 years, 7 months ago]

The function that is used to send emails is called wp_mail(), and it’s defined in wp-includes/pluggable.php. You might have a look there to begin with, and maybe even replace the version of the function in that file with a fresh version from a newly-downloaded copy of WP, if you suspect that some things have been changed.

Another thing to keep in mind is that wp_mail() is pluggable, which means that plugins can add their own version of the function, which will be used instead of the one in wp-includes/pluggable.php. If you’ve got shell access to your server, you can see whether this is happening with the following command, run from your wp-content directory:
`grep -nR ‘function wp_mail’ ./`

If this turns up any results, then that might be a good place to look for wp_mail hanky panky.

[@boonebgorges Keymaster 15 years, 7 months ago]

Very strange. The fact that you’re having problems with the email notification of blog comments shows that this is not a problem with BuddyPress, but is some combination of your server, WordPress, and possibly Yahoo Mail.

Have you tried reading the problematic mail through another method? POP3 or IMAP? Or maybe the same email sent to another provider like Gmail? At least that could rule out the mail client.

[@boonebgorges Keymaster 15 years, 7 months ago]

Actually, I just looked at the code, and the comment there is correct. The entire function is wrapped in a function_exists check, which means that you could simply put your own version of bp_dtheme_blog_comments() in your child theme’s functions.php, and it would override the one in bp-default (no changes to comments.php necessary). The way that you’ve done it will continue to work just fine, of course.

[@boonebgorges Keymaster 15 years, 7 months ago]

You’re right it could be better commented, but in BP’s defense, this is a core WP functionality, and part of just about every modern theme https://codex.wordpress.org/Template_Tags/wp_list_comments

[@boonebgorges Keymaster 15 years, 7 months ago]

Awesome, so glad it worked!