Hi
Can anyone tell me why when I enter the BuddyPress from WordPress settings it is not showing the Pages tab so I have no way of setting the registration, login pages etc?
Thanks
Matt
with that script on line 155 the function (buttons do work now), thanks
I try to stay in the loop with changes and helping documentation Buddypress as it develops.
Been using it over 14 years on this website, thanks again
Hi @gbordormor22
Here is how you can get involved with documentation:
https://github.com/buddypress/buddypress/tree/master/docs/contributor/documentation
You and everyone are very welcome to contribute.
@erotmil this is a public forum, do not share access to your site. I never ask to log in to a user site, and I’ll never log in to edit a user site. I just deleted the access you shared in your previous reply.
Your custom page is out of BuddyPress scope. The only thing that has changed since 11.4.0 that could possibly interfere imho is the fact BuddyPress used to put its JavaScript and Styles everywhere on your site, including this page. You can try to use the gist the way I commented it to have these JavaScript and Styles back.
Login as
on the website request page try and edit a request,
then to see how it does work, rollback to 11.40. you will see the rollback option in buddypress plugin . let me know what you think
Thanks
I have 3 websites and after the newest plugin update, the entire buddypress system crashed. All pages buddypress related give a fatal error screen. Activity, members page, profile, etc. I reverted back to the old version and it works fine again. I thought it was a plugin conflict but it is happening on multiple sites even fresh ones.
Thanks
Wordpress version: 6.4.2
Buddypress version with fatal error: 12.0.0
Buddypress version that works fine: 11.4.0
Thanks @vapvarun! I installed this plugin and tested the emails. I successfully received the email. I have WP SMTP mail set up as well, but people are still not getting email notifications from our BuddyPress group. Is this a “situation” thing from within BuddyPress? If so, I’m not sure how to create a situational email for group notifications.
@erotmil you can turn WP_DEBUG to false. Deprecated notices need to be addressed, but they are not responsible for the bug.
BP Classic can be activated before or after BuddyPress 12.0.0. In 11.4.0 we suggested to activate it so that the 12.0.0 migration task is short circuited, but it can be done after, it will simply revert the 12.0.0 migration task.
I’ll look at your HTML page asap.
I can indeed help with BuddyPress 12.0 Documentation, if I am guided on how it works.
I can start now, and try to finish by January ending.
Then, it will be easy if the Documentation does not involve me writing PHP Codes.
Regards.
You can easily check if email functionality is working on your website by using a couple of test email plugins available online. https://wordpress.org/plugins/check-email/
If it’s working, email functionality should also be operational. BuddyPress uses the same approach to send emails.
Mathieu, thanks for the comments , I can see there are many effected by the upgrade, I hope its not overwhelming for you. I don’t write php, but of course can copy and paste. I am not missing any buttons, the buttons just don’t work , they still show, they are edit , delete, created I think with forminator. Since there is a functions.php page in my child theme I tried pasting the add_filter code you posted, with BP 12 it didn’t help. I pasted it in the top section “function my theme area, I posted the functions php code in a gist here
I am looking to see how to share a screenshot of the offending page ,.
Hey also I noticed in the buddypress settings page there is a tab marked “Pages” that is new, I have no idea if I am supposed to set those drop downs to pages, but after touching it now I see a message in red “The following active BuddyPress Components do not have associated BuddyPress Pages: Members, Activity, Groups, Activate, Register.” The guy that wrote these custom code child theme pages died about two years ago, I’ve been maintaining this website and really hope I can keep this working , updates can whack it out , but usually it still functions after the update , not this time
@gbordormor22
About documentation: I agree with you. Writing what we need to do is nice. It would be even greater if you could take another step: contribute to it 😅.
We’ve tried to get contributors to help us twice to update https://codex.buddypress.org unfortunately we were not able to get enough people to help us.
For this particular release, we’ve made a big shift and I personally took the time to write docs about the effects for users as I wrote into the announcement post. You can read it here: https://github.com/buddypress/buddypress/blob/master/docs/user/administration/README.md
Problem is: being in the code makes you miss important things for users. The fact we now uses the URLs BP settings tab instead of the WordPress pages we used before to set BP directory slugs and titles does not seem to be too difficult to find to me. I see reading your and some other replies it’s not that easy.
Adding directory links to WP Menus hasn’t changed that much, here’s a direct link to the doc: https://github.com/buddypress/buddypress/blob/master/docs/user/administration/navigations/README.md
@Mathieu Viet
You are correct. It’s my Theme that added it. I’ve reached out to them and they’ve fixed it.
GOING FORWARD
I think BuddyPress 12.0 is quite different.
Things no longer work as we used to know them.
The first culprit is Pages. We don’t know how to get our Pages again. I need to show my Activity Page on my website, but I’ve spent 2 days on it, and still can’t figure it out.
What I think should happen, is that we should have a SubMenu on this BuddyPress website, and call it “BuddyPress 12.0 Guides“.
You can copy everything in BuddyPress Documentation, and paste them inside the BuddyPress 12.0 Docs.
Then your content creator can start modifying the information of these Docs to reflect the BuddyPress 12.0 reality.
Regards.
Hi @priyam1234 about ACF, the thing is we don’t use a UI to edit BP directory pages. As anyway we never used the content of the page post type for BuddyPress content, now we’ve migrated to a buddypress post type we’re not generating the corresponding UI in WP Admin. I’m going to look at it to see how we can integrate ACF with our new way of dealing with the buddypress post type. I just need 2 or 3 days to figure it out.
Hi @erotmil thanks for sharing this code. I don’t see anything particular that would conflict on the server side. Since your issue is about button visibility I wonder if the fact we’re not including BuddyPress template pack styles and scripts everywhere on the site but only in BuddyPress generated pages could be the reason why you’re not seeing the buttons of this custom page. If you already rolled back to 11.4.0 a good way to figure it out is to temporarily add this code into the functions.php of your theme:
remove_action( 'wp_enqueue_scripts', 'bp_enqueue_scripts', 10 );. Note that this code will remove all CSS and JS for BuddyPress, make sure to use it before refreshing your custom page from your browser, once refreshed if your buttons are gone, then we’ve found the issue. Remove immediately after the above code. If you still have BP 12.0 active, you can test adding the following code to see if it’s fixing the issue for your custom page:
add_filter( 'bp_enqueue_assets_in_bp_pages_only', '__return_false' );. If it’s the case you can leave this code, otherwise remove it.
I have a little bit of confusion.
I uploaded a Cover Photo and it is showing on the Member Directory, as you can see here– https://prnt.sc/pmHvi8sO41nd
and also on the Header of the user Profile, as you can see here– https://prnt.sc/px7evM6Ggj0K
1.) Is that the expected behaviour of BuddyPress?
2.) Is there a way to show the Cover Photo on the Single User/ Profile Page, but not show it on the Member Directory?
2b.) Is there any Code Snippet that can be used to achieve that?
Regards.
We are using BuddyPress on our membership site where members primarily chat with other members. However, no one receives email notifications when there is a new comment in the group or when someone is mentioned, so it’s making it difficult to keep members engaged.
Everyone has the “receive email notifications” checked, so not sure what’s going on. Any idea on how to adjust notifications so that members receive an email notification when there is activity within the group?
thank you
can you recommend a wordpress email plugin? that will work directly with buddypress when I press ‘send invitation’
Hi @dangbird
Thanks for your feedback, in version 11.4.0 we’ve (exceptionally) introduced a feature to display notifications only to admins to inform them about the massive change coming into 12.0.0. See https://buddypress.trac.wordpress.org/ticket/9007
This feature we called “Admin notifications” is temporarily overriding the notifications for all admin users as long as one of the admin clicks on the exclamation mark to read the important message we want him to read. This message is about when to activate BP Classic to preserve backwards compatibility required by a specific config (BP Plugins not updated for the last 4 months, the deprecated BP Default standalone theme activated or the need to still use BP Legacy widgets).
It may be the reason explaining what you saw with the Reign theme. It should disappear as soon as you read the Admin notification. Let me know if it helped you fix (or not) the issue with 12.0 for you.
Hi @jane-blonde
As we informed into an Admin notification after the 11.4.0 upgrade and at each 12.0.0 pre-releases. So it’s not an issue.
We’ve moved Legacy widgets into the BP Classic back compatibility add-on. Since version 9.0.0 we’ve transformed these legacy widgets as block widgets.
BP Classic
Hi @priyam1234
I guess you found how to get back to « classic » pages for BuddyPress directories (installing and activating BP Classic). That’s the way you will find also back your need to use ACF with it.
About your second reply I’m not sure to understand what you mean about the functionality you’d like to use in BuddyPress Classic and that is only available in Modern BuddyPress. If it’s the community visibility feature, I confirm you need to « go Modern » with the BP Rewrites API to enjoy it.
@claudiovillagra Thanks for your feedback, I’m sorry you experienced trouble during the upgrade of your specific configuration, it’s difficult to be more useful to you as your description of the problem is very limited. I must admit we’ve hesitated about this release name « Nonno » but we were sure our community members was so friendly, constructive & contributive we wouldn’t get this kind of ironic remarks.
Hi @gyrus
Sorry to read about this issue.
We’ve built BP Classic a back compatibility Add-on, maybe you can try activating it to see if it solves the issue:
BP Classic
If not, I’ve explained into this reply how to rollback to 11.4.0 (you’ll need BP Classic anyway)
BuddyPress 12.0.0
> if you want to rollback, activate BP Classic (to get the regular directory pages back into your regular WordPress pages), then deactivate BuddyPress and BP Classic. You’ll need to manually reset the « DB Version » to the one of you version, see https://codex.buddypress.org/releases/. For instance for version 11.4.0, into the wp_options table the _bp_db_version option should be 13408. Only then download and activate a previous BuddyPress version (11.4.0).
I’ve just woken up to find an auto-update to BP 12 has completely broken groups functionality on a client site. E.g. the main groups page is now post type ‘buddypress’ instead of ‘page’, so it’s no longer in the main nav. Lots of others breakages.
I need to roll back to the previous version. Presumably this involves doing more than rolling the plugin itself back, as 12 seems to have made loads of changes to the DB without consent. Please advise.
Hi, I just woke up to find that one of our major client sites has auto-updated to BuddyPress 12 and this has completely broken groups functionality, which is a major part of the site. How can I quickly roll back to the previous version? It looks like more than just rolling back the plugin itself, it seems to have done loads of things to the data without my consent.
