Thank you for you help guys!
i installed wordpress and buddypress new. There is still the same issue.
any idea?
Please use the code button when sharing code.
When extending Groups, you should use the BP_Group_Extension.
It’s easy to use and handles creation of nav items.
It’s safe to deactivate BuddyPress, you will lose the BP features but they will come back after you reactivate the plugin, so you can do it quickly to test then reactivate it.
@r-a-y
I haven’t tried that. I contacted WordPress a second time and now they decided to look into it for me, so I am waiting on that.
If I deactivate Buddypress, what will happen to my site? It is a member community full of groups and forums and I am afraid to break it.
Is it safe to just deactivate Buddypress like that?
Should have mentioned that I’m running WordPress 4.9.7 and Buddypress 3.1, along with the BuddyBoss Boss theme 2.4.3.
The code to activate a user can be found here:
https://buddypress.trac.wordpress.org/browser/tags/3.1.0/src/bp-members/screens/activate.php?marks=98#L62
https://buddypress.trac.wordpress.org/browser/tags/3.1.0/src/bp-members/bp-members-functions.php#L1798
It would be great if you are able to set up a fresh install of WordPress and BuddyPress to see if your activation problems are because of some custom code on your site.
How are your users logging in?
What happens if you deactivate BuddyPress? Do login attempts work? If not, it’s not a BuddyPress issue.
About the code that is linked:
https://buddypress.trac.wordpress.org/changeset/11766/trunk/src/bp-templates/bp-legacy/buddypress/members/activate.php
If your theme contains either a /buddypress/members/activate.php or /registration/activate.php file, you replace red lines with green lines. If your theme does not have any of these files, then you don’t need to make any changes.
If you are still running into trouble, change your theme temporarily to see if your theme is the issue.
—-
If you want to roll back to an older version, you can do so on the following page:
https://wordpress.org/plugins/buddypress/advanced/
Under “Previous Versions”, select 2.9.4 and replace the copy on your server with that one.
Hello!
Someone knows if the code still working with the version 3.1.0?
I remember to have used the code from @lenasterg with the version 2.9.4 and was working perfectly but now with a website running the version 3.1.0 the code doesnt redirect the old setting URL to setting/notification anymore.
I am looking for a way to remove the general tab and redirect the setting URL to notifications. I already have a page where users can change their password so have two places where someone can edit the same information is a bit confusing.
—-
MOD EDIT – View the following thread for updated info:
Removing Settings General tab redirect to Other Tab
Wordpress 4.9.7 Buddypress 3.1.0
I am using WP SMTP integrated with SendGrid to send out the automated emails that BuddyPress sends to members as the members interact with my wordpress site (i.e. someone commenting, sending a PM, favoriting, etc.)
When those emails get sent out to yahoo and aol addresses I get an email that says:
This is the mail system at host gateway36.websitewelcome.com.
I’m sorry to have to inform you that your message could not
be delivered to one or more recipients. It’s attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<yolojim@aol.com>: host mx-aol.mail.gm0.yahoodns.net[74.6.141.40] said: 554
Message not allowed – Headers are not RFC compliant[291] (in reply to end
of DATA command)
Reporting-MTA: dns; gateway36.websitewelcome.com
X-Postfix-Queue-ID: 80867400C8426
X-Postfix-Sender: rfc822; torus@drumsbygenre.com
Arrival-Date: Mon, 9 Jul 2018 20:33:42 -0500 (CDT)
Final-Recipient: rfc822; yolojim@aol.com
Original-Recipient: rfc822;yolojim@aol.com
Action: failed
Status: 5.0.0
Remote-MTA: dns; mx-aol.mail.gm0.yahoodns.net
Diagnostic-Code: smtp; 554 Message not allowed – Headers are not RFC
compliant[291]
I also see that the emails are sending duplicate subject lines which I read could be the root of this issue.
1. Does anyone have a solution for this?
2. If the solution is making sure there is only one subject line, does anyone know how to execute this?
Thanks for your time guys 🙂
Check if you’ve set the buddypress members directory page in WP admin – Settings – BuddyPress – Pages – members
@billysgtr @venutius this is really cool news as i need the exact same feature (only authors can send private messages on buddypress) …..how do i go about getting the latest version? is it an official plugin now?
You are using v2.9.1. Your issue is addressed in BuddyPress v3.0.0 as we have stopped activating accounts by direct URL.
Activation now requires a form submission when you are on the activation page.
Actually, that does not work, I must have it wrong. The easiest way is to go to your menu edit page, and select profile in the BuddyPress options, these may be hidden so you will need to go to screen options and select BuddyPress
That’s not a feature that is supported right now. The issue is that bp does not store the activation code for the user, so it can’t look up the activation code and know it’s the right one but has already been activated for that user. I think you would need to raise a feature request on Trac for that.
With bp you can overload the user profile pages and replace their code with your own. The templates are located in the plugins/buddypress/bp-templates directory, either bp-legacy or bp-nouveau depending on your config. in that directory you would look in buddypress/members/single and you will see the various profile templates. You overload these by creating alternative files in themes/my-child-theme/buddypress/members/signle/ etc..
If you have FTP access, you can rename the plugs/buddypress directory to something else, this will stop BuddyPress from loading and that should get you working. If that works you will then need to work out why it failed, but I guess it’s one step at a time.
I think this is related to this bug report:
https://buddypress.trac.wordpress.org/ticket/7923
A number of html outputs were escaped using esc_html() which caused the links to go wrong. Should be fixed in the next update.
It’s not actually checking for the bbPress forum, it’s checking for a forum that no longer exists in BuddyPress, which is why it’s failing.
500 error
You can report issues on Trac at https://buddypress.trac.wordpress.org/
The username and password you use here should work.
BuddyPress can’t do this out of the box but it is very developer friendly. If you are comfortable with PHP and JavaScript you could extend to add this custom functionality.
That function has been deprecated, it simply needs to be deleted, are you sure it’s in BuddyPress/members/…? Typically it’s an overload of this file that is at issue, check with your theme creator to see if they need to update.
Right now I have this:
<form action=”” method=”post” class=”standard-form” id=”activation-form”>
<label for=”key”><?php _e( ‘Activation Key:’, ‘buddypress’ ); ?></label>
<input type=”text” name=”key” id=”key” value=”<?php echo esc_attr( bp_get_current_activation_key() ); ?>” />
and that should be overwritten with:
<form action=”” method=”get” class=”standard-form” id=”activation-form”>
<form action=”” method=”post” class=”standard-form” id=”activation-form”>
<label for=”key”><?php _e( ‘Activation Key:’, ‘buddypress’ ); ?></label>
<input type=”text” name=”key” id=”key” value=”” />
<input type=”text” name=”key” id=”key” value=”<?php echo esc_attr( bp_get_current_activation_key() ); ?>” />
This is in my buddypress/bp-legacy/buddypress/members/activate.php
I’ll assume we should put this in the child theme?
