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

Oh sorry @perchenet

I just figured out, BP is network activated but you’re overriding the root site ID do that’s a subsiste. I’ll test this config asap.

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

Bonjour David (@perchenet),

Merci pour ton merci ☺️.

I’ll do the rest in English in case someone faces the same issue 😉.

Depending on whether you activated the BP Classic backwards compatibility Add-on, BP Directories can be a regular WP page (BP Classic & BP < 12.0.0) or use a specific post type BuddyPress (BP 12.0.0 & up without BP Classic). So to find into the wp_{site_id}_posts table the directory slug, you need to look at the post_name field.

About slug conflict management what I’ve added into 12.0.0 is to make sure a buddypress post type’s post_name doesn’t conflicts with one the existing page post type’s one because it’s immediately after the domain (I’d rather use a intermediate slug but that’s not the way BP was built in the first place…). If you get a -3 suffix it should mean you have 3 other entries like activity, activity-1 and activity-2. If you’re not using BP Classic or if you activated it after upgrading to 12.0.0 it can be caused by a migrating task wrongly played more than once.

What I would do in your case: go into the BP Repair tools and if available use the « Reset slugs » one. If you don’t see this repair tool it means you’re using BP Classic.
If the reset tool didn’t change anything or if BP Classic is active, I would check into the wp_{site_id}_option the value of the bp-pages option name, it’s a serialized array keyed by component name and containing the post IDs that are associated with a BP Directory. Thanks to this post IDs, I would only keep the corresponding post type and delete the other ones (or change the others post_name values).

I’d be interested to reproduce the steps you did to face this situation. Was BP Classic activated on the same site that BuddyPress is activated on before the 12.0.0 upgrade? Was it activated after? Or maybe you haven’t activated it?

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

Hi @priyam1234

Cool, thanks for your feedback.

I was about to point you to the update they did 21 hours ago: https://plugins.trac.wordpress.org/changeset/3013040

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

Maybe it’s due to this bug we’ll be fixing in 12.1.0

Can you test adding the following code to see if it’s fixing the issue into the functions.php file of your active theme for example:

add_filter( 'bp_enqueue_assets_in_bp_pages_only', '__return_false' );

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

Hi,

I advise you to download and activate the BP Classic backwards compatibility Add-on for 3rd party plugins not ready yet for version 12.0.0 of BuddyPress (bbPress is not currently ready for it, see: https://bbpress.trac.wordpress.org/ticket/3576)

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

Hi @alyssashift

I’m sorry but we cannot provide help for this fork of BuddyPress, please contact the buddyboss support instead.

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

Hi,

Have you tried to download and activate the BP Classic backwards compatibility Add-on?

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

Hi @awol

Thanks for your initiative, a possible way to find it is to download your /wp-content directory and use a code/text editor like vscode and use their “Search in directory” feature.

Hi @priyam1234

Really happy you found the way to fixing your issues 👍.

Hi @cristan17

Sorry to read about the issues you’re facing.

The first thing I would do if I were you would be to make sure errors are not logged on front-end but only into your error log file: you can define WP_DEBUG_DISPLAY to false into your wp-config.php to do so, see: https://wordpress.org/documentation/article/debugging-in-wordpress/#wp_debug_display

Then, there’s a good chance these errors are deprecated notices which means the 3rd party BuddyPress plugins or theme have not updated their code to be ready for 12.0.0. We anticipated this case building the BP Classic backwards compatibility Add-on. If you haven’t activated this Add-on with BuddyPress 12.0.0, you can try to do so to see if it fixes your issues.

If you want to roll back once you updated BuddyPress, you’ll need the BP Classic Add-on to first find back your BuddyPress pages. Then deactivate BuddyPress and all other BuddyPress plugins except BP Classic. BP Classic will make sure you have your BuddyPress pages will stay in place. Then only deactivate BP Classic. Remove the wp-content/plugins/buddypress folder of your site. Before installing version 11.4.0, make sure to edit manually the BuddyPress db version option for the one of version 11.4.0. Into the wp_options table the _bp_db_version option value needs to be 13408.

Here’s the download link for 11.4.0:
https://downloads.wordpress.org/plugin/buddypress.11.4.0.zip

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

Now I’ve read the other topic you posted into, I know you are using WordPress Multisite.

My question about viewing the registration page being disconnected might seem a bit obvious but I wanted to check if you were using or not the Site invitation feature of BuddyPress which uses our signup page although global registration are disabled.

But I guess registration is on since you’re using a specific plugin.

Using BuddyPress < 12.0.0, once you removed the registration page, were you getting a notice to do the page association ?

I believe reading your post we should probably stop assuming you want BuddyPress to manage registration to your site, so I’ll work on a way to only do so if the admin opts in.

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

Let’s discuss about your issue in this topic https://buddypress.org/support/topic/how-to-delete-register-page/ @bermudastream 🙏

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

Hi @bermudastream can you give more details about your config:

– WordPress Multisite or regular ?
– In the site health information tab, what are the values of:
– WordPress > registration
– BuddyPress > URL parser

– being disconnected, what do you see when you go to this registration page ?

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

Hi @erotmil thanks a lot for your help 👍.

Hi @mattobiwan1982 there’s probably a plugin for this, what we do about the community visibility in 12.0.0 is only available thanks to our new BP Rewrites API.

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

Hi @claudiovillagra

Is « BuddyPress Birthdays » a GamiPress add-on ? Or what is the plugin generating this feature ?

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

Hi @priyam1234

Well we are not using Post IDs to decide what content should be displayed but URI globals that can be accessed through these functions : https://github.com/buddypress/buddypress/blob/master/docs/developer/functions/uri-globals.md

The post ID is reset to 0 when you reach a BuddyPress page to avoid PHP notices. There’s a new way to get this ID though adding an action to this hook https://github.com/buddypress/buddypress/blob/master/src/bp-core/classes/class-bp-component.php#L1260 (the query parameter has a queried_object_id property ($query->queried_object_id) where you’ll get this ID.

The code I shared with you is adding a new WP Admin Menu « BuddyPress directories ». Thanks to it you’ll get the list of directory pages similarly to regular WordPress pages and you’ll be able to reach the edit part of these pages. As the buddypress post type doesn’t support the editor, this page will only show the directory title. I believe from what I know of ACF it should be enough for this plugin to generate its metabox.

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

Sure, you’re welcome 👌

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

@jaymzwayne 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 » for the one of 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).

Here’s the download link for 11.4.0:
https://downloads.wordpress.org/plugin/buddypress.11.4.0.zip

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

Hi @shemakeswebsites,

12.0.0 brings URL slugs customization, that’s a big improvement to have meaningful URLs for non English communities.

These communities are using different words for things like Activity, groups etc.. They can do so thanks to the l10n feature of WordPress. So a good way to reach your goal is to use a custom translation file. And I believe it’s the best way to do so, because the page title or labels won’t be enough to really reword all places where we use groups.

You can try to put your custom translation file into wp-content/languages/buddypress/buddypress-xx_XX.mo replacing the xx_XX with your locale maybe it’s even working with en_US.

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

Hi @ingenxcomputers

If you are using BuddyPress version 12.0 and up, you can customize the title and the URL of these pages from the URLs tab of the BuddyPress settings: https://github.com/buddypress/buddypress/blob/master/docs/user/administration/settings/urls.md

If you need to include these pages into a WP Nav menu, please have look to:
https://github.com/buddypress/buddypress/blob/master/docs/user/administration/navigations/README.md

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

Great @cdb44 👍 I’m happy you found the fix. About our plan on maintaining BP Classic: we haven’t discussed about it yet. I’d say as long as other BP plugins will need it.

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

Awesome! Many thanks for your feedback, it’s great Youzify fixed it 👍

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

Hi @priyam1234

You can use bp_get_directory_title( $component_id ) eg: bp_get_directory_title( 'activity' ).

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

@cb44

This is weird because if you activated BP Classic the undefined function your error log is reporting is included into BP Classic:
https://github.com/buddypress/bp-classic/blob/8e8ec62d07e1033a78922aa76a4699669fda31f8/inc/core/functions.php#L557

So it shouldn’t error. I’ll test bbPress again.

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

@hengstigal Reading your error it looks like the BP Groups component is not active. Moreover I also see that your plugin Grimlock BuddyPress is not ready for version 12.0.0 of BuddyPress. I advise you to activate BP Classic : it’s the backwards compatibility plugin we’ve built on purpose for such a situation:

BP Classic

@cdb44 bbPress needs the same backwards compatibility plugin ^^. Please activate it. Moreover it looks like you’ve disabled deprecated functions loading probably using the BP_IGNORE_DEPRECATED constant into your wp-config.php file or elsewhere.

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

Je t’en prie Bruno. Content que le problème soit résolu, merci de ta confirmation 👍.

Cordialement,
Mathieu

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

I’ve replied here: https://buddypress.org/support/topic/buddypress-12-0-0/page/4/#post-332340