BuddyPress.org

yatesa01: I see from this other topic, it’s the Astra theme. I’m looking at it.

Here’s the ticket about the BP Blocks regression: https://buddypress.trac.wordpress.org/ticket/9037

Hi @mattobiwan1982

The Pages tab of the BuddyPress settings has been replaced by the URLs one where you can customize all BP URLs slugs. Directories, registration/activate pages are now managed ged from there. See:
https://github.com/buddypress/buddypress/blob/master/docs/user/administration/settings/urls.md

If you need to add some of these pages to your WordPress menus, I advise you to read:
https://github.com/buddypress/buddypress/blob/master/docs/user/administration/navigations/README.md

@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 @erotmil Sorry to read about this issue, I’m not sure to understand what the custom code is doing. As you’re talking about widgets I guess it may contain some <?php dynamic_sidebar( 'name_widget_zone' ); ?>. Have you checked your error_log to see if there were some errors? About BP Classic, it contains the BP Legacy widgets, they are automatically loaded if you’re not using the Block Widgets editor, the function you mentioned was used to do this check, I believe you don’t need to care about it in your case. If your custom code is viewable from a Github Gist for example, I can look at it to see if I can find an explanation to your issue.

@claudiovillagra I understand your frustration. If I often talk about BP Classic when replying to support requests about the 12.0.0 upgrade that’s because it’s the Add-on we’ve built to “neutralize” the 12.0.0 change BP Plugins might not be ready with (even if we’ve been working on 12.0.0 and communicating about it for almost a year…). I thought Woffice was a plugin but find out it was a premium theme. Unfortunately I can’t look at their code to understand the issue. If you haven’t try BP Classic, what I would do in your case would be to put up a staging site to replicate your production site and give 12.0.0 some other tests, try BP Classic and if issues are not solved with it, try to identify the issue checking the error_log file or using define( 'WP_DEBUG', true ).

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 @westmdresearch

Thanks a lot for your feedback 😍. I’m happy to read you succeeded in troubleshooting issues on your side. We always try to imagine what could go wrong when we update our code but at the same time, we need to go forward. This release is very important as we’ve tried to explain as much as we could, it’s a starting point: fully complying with WordPress way of parsing requests will help us on various fields in the future. We know it’s a massive change and I feel sorry to read there are cases we were not able to anticipate: but we strongly believe it’s a needed change for the better of our next community features.

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

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

Hi @varadkk

The new way to customize URLs or directory titles is happening in Settings > BuddyPress then click on the URLs tab. More info about it here: https://github.com/buddypress/buddypress/blob/master/docs/user/administration/settings/urls.md

If for some reason (compatibility with a 3rd party BP plugin) you need to get this page back, you can use the BP Classic add-on.

@weathermadness with so few information I guess something is wrong with a potential third party BP plugin, have you activated the BP Classic plugin ?

Hi,

It’s a deprecation notice. According to it you are still using BP Legacy Widgets. These widgets were moved into our Backwards compatibility Add-on « BP Classic »:

BP Classic

You can find them back downloading and activating this Add-on.