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

About @lmstearn’s issue, I’ll work on it from this GH issue: https://github.com/buddypress/bp-classic/issues/34

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

I’m sorry @legiosmoke I can’t reproduce this issue, everything works fine on my side. Have you tried deactivating completely BuddyPress then BP Classic to see it this was fixing the issue?

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

@priyam1234

This will be fixed in next minor version (12.1.0). The tool to reset slugs will now delete buddypress post types that are not used for directory pages. See: https://buddypress.trac.wordpress.org/changeset/13680

For now you can look into your database {wp_table_prefix}options table the value of the option name 'bp-pages' to know the buddypress post type’s IDs that are used to display directories.

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

Hi sorry to read about this issue. bbPress is not ready for BuddyPress 12.0. You need to activate BP Classic:

BP Classic

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

So 😅. Thanks for sharing the error log. To me, deprecation notices cannot be the source of your troubles. For bbPress you need BP Classic as it’s not ready for BP 12.0.0. I submitted a patch to their Trac env. but it has not been committed yet.

Even if BP Classic is active, your links are logging you out?

There’s only 2 way to get this behavior, the links are containing the logout URL, or some code is redirecting the page after logging you out.

Next step would be to rollback to 11.4 to see if the bug has disappeared. But if it’s the case I’d be surprised.

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

I’m sorry, I’m too afraid to break things: I never do that.

I wonder if it could be a malformed link

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

Ouch, it will probably generate a fatal, but maybe we’ll get more information to trace which plugin is using this deprecated function.

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

This last one is more helpful. Are you sure BP Classic is active? Because if active BuddyPress shouldn’t add this depreciation notice.

What happens if you add this code to your wp-config.php?
define( 'BP_IGNORE_DEPRECATED', true );

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

I believe you’re looking in the wrong direction: if clicking on Notifications or Messages from the top right admin panel is logging you out, it’s not a WP Nav Menu.

Have you tried clicking on these links being in WP Admin?

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

@fasirathore

It was not logging you out with version 11.4.0 of BuddyPress?

Can you rollback to 11.4.0 keeping BP Classic active to see if that solves the issue?

Elementor’s reply is amazing, considering the price you pay for support & the fact we can’t test on our side because it’s a premium plugin and they can test on their side as BuddyPress is free. If it was out of their scope, Elementor wouldn’t conflict with BuddyPress…

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

Awesome, thanks a lot for your feedback 👌

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

@cheesy2k

Slug constants were deprecated in version 1.5 of BuddyPress (more than 10 years ago). We decided to remove them from BuddyPress 12.0.0 as it’s now very easy to customize slugs.

Your error is interesting, if you look at it, you’ll see the theme kleo now generates this error while it wasn’t when BP Classic wasn’t active. It means kleo is not ready for BuddyPress 12.0.0 because it wasn’t loading his specific code as it was trying to do so too early (BuddyPress objects are defined once the WP_Query is parsed in 12.0.0, while it was a bit after init previously).

So, I advise you to contact kleo so that they update their outdated theme.
In the meantime, you can get rid of this error adding this to your wp-config.php file:

define( 'BP_NOTIFICATIONS_SLUG', 'notifications' );

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

Hi @cheesy2k

Sorry to read about this issue. It’s difficult to figure it out. We made an important change in 12.0.0 & although we communicated a lot there might be some third party BP plugins not ready yet for 12.0.0. That’s why we anticipated building this backcompat addon:

BP Classic

If you haven’t tried to activate it, I advise you to do so to see if that fixes the issue.

I also advise you to check your server error log file as it might contain some infos about what’s going wrong.

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

Ok, I understand you don’t want to take the time to fix the issue. It’s really difficult to understand each other. Sorry to read my help is so annoying. If the table is not called wp_posts, it’s probably due to the custom table prefix you defined into your wp_config.php file. The code I’ve shared is a filter, there’s no way for it to fail, but you managed to! I don’t know how you pasted it. You don’t seem to read what I’m advising you to do and you don’t reply in an understandable way. If you don’t want to fix the issue, I advise you to look into this support reply to see how to roll back to 11.4.0: https://buddypress.org/support/topic/buddypress-12-0-0/page/4/#post-332388

I won’t annoy you anymore.

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

Here’s a way to disable BuddyPress signup feature:

function disable_bp_signups() {
	add_filter( 'bp_get_signup_allowed', '__return_false' );
	remove_filter( 'register_url', 'bp_get_signup_page' );
	remove_action( 'bp_init', 'bp_core_wpsignup_redirect' );
	remove_filter( 'wp_signup_location', 'bp_blogs_creation_location' );
	remove_filter( 'wpmu_signup_user_notification', 'bp_core_activation_signup_user_notification', 1 );
}
add_action( 'bp_include', 'disable_bp_signups' );

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

Here’s a way to disable BuddyPress signup feature:

function disable_bp_signups() {
	add_filter( 'bp_get_signup_allowed', '__return_false' );
	remove_filter( 'register_url', 'bp_get_signup_page' );
	remove_action( 'bp_init', 'bp_core_wpsignup_redirect' );
	remove_filter( 'wp_signup_location', 'bp_blogs_creation_location' );
	remove_filter( 'wpmu_signup_user_notification', 'bp_core_activation_signup_user_notification', 1 );
}
add_action( 'bp_include', 'disable_bp_signups' );

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

Have you tried to temporarily add this code to the functions.php of your active theme?

remove_filter( 'wp_unique_post_slug', 'bp_core_set_unique_directory_page_slug', 10, 6 );

And then did you go to the URLs tab of the BuddyPress settings and try to customize slugs again?

If so, using your tool to administrate your site’s database (eg: PHPMyAdmin), can you run this query:

SELECT id, post_type FROM wp_posts WHERE post_name LIKE "members%"

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

So you’re using BP version 12.0 on a regular site (not a multisite config), you activated, then deactivated BP Classic because it was no more needed. And now when you go into the URLs tab of the BuddyPress settings and tries to customize slugs, it adds a -2 suffix.

Is it happening when these slugs are default BuddyPress ones only (eg: activity, members) or is it happening even with these slugs: ‘activites’, ‘membres’ for example?

If it’s only happening with BuddyPress default slugs: check there are no regular WordPress pages using the BP slugs.

Then try to use the Reset Slugs BuddyPress tools from the WP Admin tools menu.

If it didn’t fixed the issue, try to temporarily add this code to the functions.php of your active theme:
remove_filter( 'wp_unique_post_slug', 'bp_core_set_unique_directory_page_slug', 10, 6 );

Go to the URLs tab of the BuddyPress settings and try to customize slugs again.

Then remove the custom code you added to the functions.php of your active theme.

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

Hi,

I just tested and I wasn’t able to reproduce, sorry. I don’t think it’s a BuddyPress problem. Have you tried to temporarily deactivate all plugins except BuddyPress to see if the issue was still there?

If so, maybe you can try to activate the BP Classic backwards compatibility plugin in case there’s a 3rd party BP plugin playing into this area.

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

@perchenet

Something similar was reported earlier about the deprecation notice. I believe it’s due to a custom code or a theme:

See: https://buddypress.org/support/topic/buddypress-12-0-0/#post-332208
Which seems to help the reporter to fix it: https://buddypress.org/support/topic/buddypress-12-0-0/#post-332211

About the main site being very slow, that’s weird. But I’ll check BP Classic with your specific config. You can try to see if only activating BP Classic on the subsite is making main site faster.

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

For your info, I’ve started your config tests and I found a bug with slug customization:
https://buddypress.trac.wordpress.org/ticket/9048

So I confirm there’s an issue. I’m working on it.

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

Hi @fasirathore

Thanks for your feedback, are you using BP version 12.0.0?
Can you check your error log file to see if something was traced in it?
What’s your WordPress set up ? Multisite or not ? If Multisite is BuddyPress activated on the network ?

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

Hi @jaroslawistok

Sorry to read about it. Can you tell me a bit more about your config?
– regular or Multisite WordPress ?
– if Multisite how BuddyPress is activated ? Network widely, on the main site or on a subsite ?
– If activated network widely, are you using the constant to set the BP root site to be a subsite instead of main one?

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

Thanks a lot

1. So there’s an issue with this specific config in BuddyPress. The repair tool, as run from the network admin where site ID is 1 is not checking the right BP root site. I’ll work on it asap. To be honest: we’ve tested a lot of configs, but I believe not the specific case where the BP root site is not the same than the network one. Sorry about it.

2. It looks like the fatal error is generated by the « onecommunity » theme. Moreover this theme or some 3rd party plugin(s) is(are) not ready for BP 12.0.0. I believe you need to activate the BP Classic Add-on network widely – like BuddyPress. (but let’s keep on debugging doing step 3 before 🙏)

3. Can you run this query:
SELECT id, post_type FROM wp_posts WHERE post_name LIKE "activity%" I feel the migrate routine wasn’t checking for the right site ID.

4. Once you activated BP Classic, go to the Permalink setting of site 4 and simply save the permalink structure without changing the selected structure.

I need some time to fix this specific config for 12.0.0. I think it will be ok for the beginning of next year.

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

@perchenet

Thanks for your feedback. Can you trace the critical error you got in your error log file?

Can you also run this select query to see the list of entries using the activity post name for example:
SELECT id, post_type FROM wp_{site_id}_posts WHERE post_name LIKE "activity%"

I’d be curious to know the result of it.