Your task can be accomplished, if you can write BP code.
Sounds like you will need to hire a developer.
You can create a listing here.
Instead of custom roles, you may want your developer to create member types.
Greetings,
The BuddyPress “Log Out” link is not working for me. I’m running BuddyPress 2.7.2 I didn’t upgrade to .3 yet because I didn’t see that this issue was addressed in the release notes. Anyway, I’ve tried TwentyFifteen and disabling all plugins. I’ve tried a different hosting account and the situation is the same: If I add the BuddyPress “Log Out” option to any of my menus, it supplies an encoded url… not the base part of the url, just the query string part as seen here:
http://example.com/phase2/wp-login.php?action=logout&redirect_to=http%3A%2F%2Fexample.com%2Fwordpress%2Flibrary%2F&_wpnonce=0ab7353131
All other instances of the logout link (like the one in wp admin or if I use <?php wp_logout(); ?> to generate one) all work fine.
Could you point me to the BuddyPress code that generating the menu point? Or otherwise point me in the right direction?
Thanks,
Alec
There isn’t a filter for that text but you can use the buddypress textdomain to add a translation.
Customizing Labels, Messages, and URLs
I set up another new domain. New fresh install never installed latest WordPress and then installed Buddypress fresh install with no other plugins and got the same error. This one might beat me.
Hi,
you can do this yourself or use a TOS plugin. Read here for details:
Terms & Conditions Checkbox
i wasn’t saying buddypress was not working
i said that with my configuration there seems to be a problem…
There isn’t an official API for BuddyPress. Development on API starting early January
@cofindrs,
BuddyPress doesn’t handle likes. That’s 3rd party plugin territory.
If Super Socializer has a notification option for BP users who doesn’t work, the solution is on the plugin author side.
If you think you can get a BP notification because somebody liked a post with help of Super Socializer, and there is no BP specific option in the plugin, i guess it is not possible.
Would be great to see more details about your statement: (Heateor) say that it is an issue in BP. Can you share a link to the discussion ?
Did you asked yourself for this issue on their support ? Your name doesn’t appear.
Awesome, thanks Dan 😉
I also got some CSS – one of the Avada Support guys (Muhammad I think) sent it over to me – needed a few tweaks, but also that now seems to have done the trick with me – if it helps any, great –
@media all and (max-width: 768px) {
#buddypress #register-page form#signup_form .register-section{
width: 100%;
}
}
#buddypress .standard-form #basic-details-section input[type="password"],
#buddypress .standard-form #blog-details-section input#signup_blog_url,
#buddypress .standard-form #basic-details-section input#signup_username,
#buddypress .standard-form #profile-details-section input#field_1
{
width: 100%;
}
The only minor bug-bear with me now is the Recaptcha overflowing, but I can live with that.
For tonight 😉
Thanks again Dan 😉
Hi @darrenllrgmailcom, @adjunkten,
i had the same issue with a custom theme: fields didn’t wrap properly on small screens…
To solve it, i simply copied the concerned form rules from Twenty Sixteen into my child theme css and all went OK after that.
The 2016 rules of the register page:
#buddypress #signup_form.standard-form #profile-details-section,
#buddypress #signup_form.standard-form #basic-details-section,
#buddypress #signup_form.standard-form #blog-details-section {
float: none;
width: 100%;
}
@media screen and (min-width: 38.75em) {
#buddypress #signup_form.standard-form #profile-details-section,
#buddypress #signup_form.standard-form #basic-details-section,
#buddypress #signup_form.standard-form #blog-details-section {
width: 48%;
}
}
@media screen and (min-width: 38.75em) {
#buddypress #signup_form.standard-form #profile-details-section {
float: right;
}
#buddypress #signup_form.standard-form #basic-details-section {
float: left;
}
}
Hi,
do you mean this plugin ? If it is the case, you have to ask the author directly.
Or if you only want to add some comment to a content you share, you can use this plugin. It is outdated but still working (i use it without trouble since years).
Depends where you need that and what you exactly want as result. You can hardcode something into the child theme template or use some CSS trick like this one.
Or maybe you need something like this ?
That said, be default, when you mention a user within a blog post or any update, a class name is automatically added: “bp-suggestions-mention”.
When you mention a user in a bbPress topic, there is no class name. But that’s lazy bbPress mentioning, not BuddyPress. If so, ask for this on their support.
it could be possible that your host plan doesn’t allow you to use BP.
it could be possible that you shouldn’t use php 7.1, as BP is not completely ready to use this latest php version.
To get sure, create a php info file and upload it at the site root (same level as wordpress)
Once uploaded, go to your-site/phpinfo.php. There you will see all information i asked you about your install. Check them and report them here please.
If you have an access to a php config via your host admin interface, go there and try to set it to php 5.6 or 7 instead of 7.1
Yes, it is not recommended to use 3rd partys automated WP installation tools. It is also not recommended to use page builders. Such tools are rarely updated, correctly maintained and often bugy… For 1.5$/mounth you can’t expect the creme de la creme, even if talented marketers try to suggest you the opposite.
Using the debug mode I get this message when activating BP:
Fatal error: Uncaught Error: [] operator not supported for strings in /customers/3/8/5/athleeto.com/httpd.www/social/wp-content/plugins/buddypress/bp-activity/classes/class-bp-activity-component.php:281 Stack trace: #0 /customers/3/8/5/athleeto.com/httpd.www/social/wp-includes/class-wp-hook.php(298): BP_Activity_Component->setup_admin_bar(”) #1 /customers/3/8/5/athleeto.com/httpd.www/social/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters(NULL, Array) #2 /customers/3/8/5/athleeto.com/httpd.www/social/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #3 /customers/3/8/5/athleeto.com/httpd.www/social/wp-content/plugins/buddypress/bp-core/bp-core-dependency.php(143): do_action(‘bp_setup_admin_…’) #4 /customers/3/8/5/athleeto.com/httpd.www/social/wp-includes/class-wp-hook.php(298): bp_setup_admin_bar(Object(WP_Admin_Bar)) #5 /customers/3/8/5/athleeto.com/httpd.www/social/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters(NULL, Array) #6 /customers/3/8/5/athleeto.com/httpd.www/social/wp-includes/plugi in /customers/3/8/5/athleeto.com/httpd.www/social/wp-content/plugins/buddypress/bp-activity/classes/class-bp-activity-component.php on line 281
Just jumping back in on this one.
I’ve been developing a large & complex WP site (60+ CPTs using Pods & BP) for the past few months on PHP 7.1. I ran all PHP 7.1 RCs and so far the only issues I’ve seen are related to BP. I’m now at the point where I’ve had to disable BP to continue development on PHP 7.1 (I need nullable types and void returns from PHP 7.1) and ignore any BP features I have on my roadmap until it’s stable (I hope soon 🙂 )
I can’t report any issues with WP-core and PHP 7.1 that I’ve witnessed.
No trying to say that BP is crappy 🙂 – just a hint that the issue may be more likely to be on BP side (especially since it seems that BBPress had a similar issue which they’ve already fixed – see my link in previous post).
The other issue I’m seeing on PHP 7.1 seems to be related to enabling Opcache and BP – https://buddypress.trac.wordpress.org/ticket/7361
Hope that’s helpful 🙂
Okay. The story is that PHP 7.1 is supported by WordPress 4.7 (or newer). Likewise, BuddyPress will need at least that version, too.
We’re currently tracking some unit test failures in PHP 7.1 (see the very bottom of https://travis-ci.org/buddypress/BuddyPress), but we’ve not figured out if they are our bugs, or some bug in WordPress core. Likewise, this do_action issue might be a regression WordPress should fix instead of us (if we’re getting caught by this, I bet many other plugins are, too).
At any rate, I’m going to try to fix the unit tests once I get a PHP 7.1 box set up (hopefully this week), and then I’ll test the basics of BuddyPress, and see what other issues crop up, and fix or report them as necessary.
I think I’d wait a month or two to use PHP 7.1 with WordPress and BuddyPress in the wild, to be honest.
install BuddyPress and only activate the Profile component.
Here the complete list of functions containing threat_id in their name:
http://hookr.io/plugins/buddypress/#index=g&search=thread_id
When I Install Buddypress then goto Dashboard > Appearance > Customize the URL I posted above is in my address bar and I’m at a White screen… nothing loads.
Confused as heck…
Hi,
please give more details… what kind of post ? Blog, update, forum….
By the way, BP doesn’t handle blog posts.
Read documentation about emails here:
emails: https://codex.buddypress.org/emails/
custom emails: https://codex.buddypress.org/emails/custom-emails/
I asked a bit too soon… A little more searching and I found your explanation here. Setting the default component seems to have done the trick. Thanks for the code samples!
Sorry, i don’t act privately on user’s site.
If you’re unable to solve your issue, hire somebody who can help you on BP Job Board.
Have you tried deactivating all plugins apart from BuddyPress and using the 2016 theme? Does it work then?
