[@anonymized-6594935 Inactive 2 years, 10 months ago]

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.

[@anonymized-6594935 Inactive 2 years, 10 months ago]

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

[@anonymized-6594935 Inactive 2 years, 10 months ago]

Hi @gyrus

Do you confirm BP Classic fixed your issue?

[@anonymized-6594935 Inactive 2 years, 10 months ago]

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.

[@anonymized-6594935 Inactive 2 years, 10 months ago]

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

[@anonymized-6594935 Inactive 2 years, 10 months ago]

Hi @lordmatt, another way to fix it is to use this filter:

add_filter( 'bp_enqueue_assets_in_bp_pages_only', 'return_false' );

See: https://bpdevel.wordpress.com/2023/11/18/bp-template-pack-javascript-and-style-assets-are-now-only-loaded-into-the-community-area-of-your-site/

[@anonymized-6594935 Inactive 2 years, 10 months ago]

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.

[@anonymized-6594935 Inactive 2 years, 10 months ago]

@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

[@anonymized-6594935 Inactive 2 years, 10 months ago]

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.

[@anonymized-6594935 Inactive 2 years, 10 months ago]

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 ?

[@anonymized-6594935 Inactive 2 years, 10 months ago]

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

[@anonymized-6594935 Inactive 2 years, 10 months ago]

@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

[@anonymized-6594935 Inactive 2 years, 10 months ago]

See: https://buddypress.org/support/topic/buddypress-12-0-0/#post-332192

[@anonymized-6594935 Inactive 2 years, 10 months ago]

Hi @shahriar83

Sorry to read about it, we never had such errors during our tests, can you give us some more details about it? Eg: the last lines of your error_log file ?

[@anonymized-6594935 Inactive 2 years, 10 months ago]

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 ?

[@anonymized-6594935 Inactive 2 years, 10 months ago]

Thanks for this new information, this notice shouldn’t be shown then. I’m going to look at it more deeply asap. I’ll keep you updated.

[@anonymized-6594935 Inactive 2 years, 10 months ago]

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.

[@anonymized-6594935 Inactive 2 years, 10 months ago]

Hi @robin-w

You’re right, thanks for reminding me about it. Just commented to reply to your question on the bbPress Trac ticket.

[@anonymized-6594935 Inactive 2 years, 11 months ago]

Hi @jgasba

If it’s bbPress pagination, my first guess would be it’s a bbPress issue. Have you tried BuddyPress 12.0.0-beta4 & latest bbPress patched with the patch I’ve attached to this ticket https://bbpress.trac.wordpress.org/ticket/3576 ?

[@anonymized-6594935 Inactive 2 years, 11 months ago]

@africanfoods Let’s discuss about it in another topic, this one is dedicated to testing BuddyPress 12.0 and BP Classic. Just imagine how you would feel if someone would interrupt a discussion you’re having about a topic with something that is not directly related to it.

Please open a new topic, describe your configuration in it: WordPress version, BuddyPress version, PHP version, name of your theme, name of the active BP Template Pack, list of active plugin names as well as active BP Components, whether there is a bp-custom.php file into your plugins directory or any other file into a mu-plugins directory, etc. We’ve sticked this topic to the forum to help you and others have a reply to their troubles, follow these steps, then ask for support. I can’t help you with so few information.

[@anonymized-6594935 Inactive 2 years, 11 months ago]

Well a regular theme shouldn’t include a templates/index.html file as it’s a Block Theme specificity. I won’t disable Block Themes support because a regular theme is not using the right template names, so you should apply @gingerbooch’s fix.

[@anonymized-6594935 Inactive 2 years, 11 months ago]

@gingerbooch sure, it’s scheduled to December 6.

[@anonymized-6594935 Inactive 2 years, 11 months ago]

Hi @gingerbooch

Thanks for your reply and fix. This check is probably due to the fact we introduced Block Themes support since BP version 10.0.

@africanfoods This support topic is about our next major version 12.0.0: please let’s try to post support issues at right places, if your issue is not related to beta testing 12.0, use another support topic.
Thanks in advance for your understanding.

[@anonymized-6594935 Inactive 2 years, 11 months ago]

Just checked, regular users can see their own profile as well as other user profiles no matter what is the selected value for the Community visibility setting.

[@anonymized-6594935 Inactive 2 years, 11 months ago]

Thanks a lot @teeboy4real for your reply.

Initial problem was caused by the hide_new_member_activities_from_unlogged_users filter callback when Post comments are synced with Activity comments about the correponding Post activity.

I have a patch ready and it will soon be fixed.