BuddyPress.org

@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

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.

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 @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).

Thanks for confirming it fixed the issue and for your feedback.

I am sorry to read 50% of these third party plugins are not ready for 12.0.0. As I’ve said a bit earlier, we’ve tried our best to raise most 3rd party plugin authors attention about the important change we’ve introduced in 12.0.0:
– we extended our beta period to 4 months
– we documented the changes.
– we’ve built a backwards compatibility Add-on
– we’ve added a new feature to display Admin notifications in version 11.4.0.

I think I fixed it.

I enqueued /wp-content/plugins/buddypress/bp-templates/bp-nouveau/css/buddypress.min.css manually in functions.php

@westmdresearch

Sure, here’s the list organized by the BuddyPress version when there were deprecated:

https://github.com/buddypress/buddypress/tree/master/src/bp-core/deprecated

Hi @koka777

I’ve just checked about bp_core_retain_legacy_widgets(). It’s not used by BuddyPress or BP Classic. I guess another plugin, a theme or some custom code is using it. To fix the issue:

1. if you’re the author of the custom code, you can replace it with:
function_exists( 'bp_classic_retain_legacy_widgets' ) && bp_classic_retain_legacy_widgets();
2. otherwise you can report to the plugin/theme author this issue.

Hi @anonymz

Thanks for your feedback, as we don’t use this function (see https://github.com/search?q=repo%3Abuddypress%2Fbuddypress+str_starts_with&type=code ), It’s probably a plugin or a theme hooking to a BuddyPress filter or action.

Do you have the full error trace ?

@westmdresearch & @fraughtithrouble

I believe there can be errors when a plugin/theme has not been updated since the last 2 versions of BuddyPress, we only load by default deprecated functions back to 2 previous versions. I suggest you to use 2 constants in your wp-config.php file:

– define( 'BP_LOAD_DEPRECATED', true ); this will load all deprecated functions (from version 12.0 back to version 1.2)
– Errors should become deprecation notices. Errors/notices should never be output on front-end, so if some errors are output on front-end, I advise you to also use define( 'WP_DEBUG_DISPLAY', false );

@fraughtithrouble 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).

@westmdresearch I’m sorry to read about all these troubles, we took all possible precautions to avoid it on our side: beta period was extended to 4/5 months, we documented the changes, we’ve built a backcompat plugin, unfortunately we cannot test and fix all free or premium plugins, this part remains their responsibility.

@varadkk if I understand well you need to get the link to your BuddyPress directories or to the registration page.

For these pages, it should always be https://yoursite.url/$slug_value where the $slug_value is the value of the slug input.

You can alternatively use the BuddyPress Directory menu or logged out member menu items if you use a regular theme, see https://github.com/buddypress/buddypress/blob/master/docs/user/administration/navigations/README.md