BuddyPress.org

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%"

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.

Thnak you again!
I wrote to the Theme creator giving him your solution. I hope he could update his theme.

BP Classic is only activated on the network (at the top level, not on the sub-site level).

I’am afraid that my main site being very slow is due to… the multisite option.
Thank you again!

Thank you Mathieu

Critical error:

Notice: La fonction map_meta_cap a été appelée de façon incorrecte. Le type de publication buddypress n’est pas enregistré. Il n’est donc pas possible de vérifier de manière fiable que la permission « edit_post » correspond à ce type de publication. Veuillez lire Débogage dans WordPress (en) pour plus d’informations. (Ce message a été ajouté à la version 4.4.0.) in /var/alternc/html/d/davduf/www/auposte.fr/wp-includes/functions.php on line 6031

Deprecated: La fonction bp_core_get_user_domain est obsolète depuis la version 12.0.0 ! Utilisez bp_members_get_user_url() à la place. in /var/alternc/html/d/davduf/www/auposte.fr/wp-includes/functions.php on line 6031

Deprecated: La fonction bp_core_get_user_domain est obsolète depuis la version 12.0.0 ! Utilisez bp_members_get_user_url() à la place. in /var/alternc/html/d/davduf/www/auposte.fr/wp-includes/functions.php on line 6031

Warning: require(/var/alternc/html/d/davduf/www/auposte.fr/wp-content/themes/onecommunity/inc/typography.php): failed to open stream: No such file or directory in /var/alternc/html/d/davduf/www/auposte.fr/wp-content/themes/newsblock/inc/filters.php on line 205

Fatal error: require(): Failed opening required '/var/alternc/html/d/davduf/www/auposte.fr/wp-content/themes/onecommunity/inc/typography.php' (include_path='/var/alternc/html/d/davduf/www/auposte.fr/wp-content/plugins/kirki/:/var/alternc/html/d/davduf/www/auposte.fr/wp-content/plugins/kirki/core:.:/usr/share/php') in /var/alternc/html/d/davduf/www/auposte.fr/wp-content/themes/newsblock/inc/filters.php on line 205
Il y a eu une erreur critique sur ce site.

The Query:

SELECT id, post_type FROM wp_4_posts WHERE post_name LIKE "activity%";
+----+-----------+
| id | post_type |
+----+-----------+
| 88 | page      |
+----+-----------+

To enable users to view other profiles on BuddyPress:

1. **Install and Activate BuddyPress:**
Make sure you have installed and activated the BuddyPress plugin on your WordPress site.

2. **Check Privacy Settings:**
Ensure that users’ profile privacy settings allow their profiles to be viewed by others. Users can control this setting in their profile settings.

3. **Activate Extended Profiles:**
Enable the “Extended Profiles” component in the BuddyPress settings to allow additional fields and information on user profiles.

4. **Verify Theme Compatibility:**
Confirm that your WordPress theme is compatible with BuddyPress to ensure proper display of profile information.

5. **Check User Roles:**
Verify that users attempting to view profiles have the necessary capabilities. By default, registered users should be able to view other registered users’ profiles.

6. **Use BuddyPress Widgets/Shortcodes:**
Utilize BuddyPress widgets and shortcodes to display member directories and user lists. Refer to the BuddyPress documentation for guidance on implementing these features.

7. **Review BuddyPress Documentation:**
Consult the official BuddyPress documentation for any specific settings or features related to profile viewing.

By following these steps, you should enable users to view other profiles seamlessly on your BuddyPress-enabled WordPress site.

Hello, I’m facing another issue. I am unable to set the location of “Better Messages” to “Show in BuddyPress profile.” I encountered a severe error. I’ve also tested it on the default theme, where I only activated BuddyPress and the Better Messages plugin. I’ve successfully set the Better Messages location to work with other pages. Please assist as soon as possible; it’s urgent.

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' );

if it also helps to know the work around is i have youzify when i deactivate that then some of the problem goes away that is a plugin i paid for and it works great gives me alot of features that i dont want to loose when i have to mess with the themes side of things or buddypress i have to turn off youzify when done turn it back on is there a way i can go back to the 11 release of budddy press

If you’re looking to add a background image and personalize the ‘Sign Up’ page further, you can use custom CSS. Here’s a simple example to get you started:

css
Copy code
#signup-form {
background-image: url(‘your-image.jpg’);
background-size: cover;
background-position: center;
background-repeat: no-repeat;
padding: 24px;
}
Replace ‘your-image.jpg’ with the URL of the image you’d like to use. You can customize the padding, background size, position, and other properties to suit your preferences.

To implement this:

Access your platform’s customization or theme settings.
Look for an option to add custom CSS.
Paste the provided code snippet.
Save your changes.
This should apply the background image to the ‘Sign Up’ page as per your specifications. If you have any questions or need further assistance, feel free to reach out.

Well, I had BP Classic activated event before updating to BP 12…

About the BP_IGNORE_DEPRECATED, I’m not quite sure, it’s not in my wp_config.php, at the oposite, I added BP_LOAD_DEPRECATED as mentioned earlier in this post. I’ll have a closer look as it may come with our WAF or our theme.

How long do you plan to maintain BP Classic ?

Yes, it is possible to create a cricket scoring web application using WordPress. While WordPress is traditionally used for content management and blogging, it can be extended to build various types of web applications, including a cricket scoring application.

Here are the steps you can take to create a basic cricket scoring web application on WordPress:

1. Choose a WordPress Theme:
– Select a WordPress theme that suits your requirements or use a sports-oriented theme. There are many themes available that can be customized to fit the design and functionality you need.

2. Install and Configure WordPress:
– Set up WordPress on your server and configure it according to your needs. You can use popular hosting providers like Bluehost, SiteGround, or others to host your WordPress site.

3. Install Relevant Plugins:
– Use WordPress plugins to add specific functionality to your site. For a cricket scoring application, you might need plugins that handle sports scoring or booking systems. Some popular WordPress plugins for sports include SportsPress, Team Rosters, and Booking Calendar.

4. Customize and Design:
– Customize the appearance of your site using the WordPress Customizer or a page builder plugin. Ensure that the design aligns with the branding and requirements of the cricket ground owner.

5. Implement Cricket Scoring Features:
– Depending on the complexity of the scoring system you want, you may need to customize or extend existing plugins or develop custom features. This may involve custom post types, taxonomies, and fields to handle match details, scores, and other relevant information.

6. Ground Availability:
– Implement a booking or reservation system to display the availability of the cricket ground. You can use booking plugins or customize them based on your specific needs.

7. Real-time Score Updates:
– For real-time score updates, consider integrating a live scoring API or implement a solution that allows the input of scores during a live match.

8. User Management:
– Implement user roles and permissions to manage who can update scores, edit content, and perform other administrative tasks.

9. Responsive Design:
– Ensure that your web application has a responsive design so that users can access and interact with it on various devices, including smartphones and tablets.

10. Testing and Security:
– Test your application thoroughly to identify and fix any bugs or issues. Also, prioritize the security of the application, especially if it involves user data or sensitive information.

Keep in mind that while WordPress can be a powerful tool for web development, more complex functionalities may require a combination of existing plugins and custom development. If the requirements become highly specialized, you might also consider consulting with a web developer or agency to ensure the successful implementation of your cricket scoring web application. Also you can see this cricket schedule website for reference.

Hello Mathieu,

we are using BuddyPress in conjonction with BBPress.

We get this error :

Fatal error: Uncaught Error: Call to undefined function bp_core_get_user_domain() in /path/wp-content/plugins/bbpress/includes/extend/buddypress/members.php:229 Stack trace:
#0 /path/wp-content/plugins/bbpress/includes/extend/buddypress/members.php(100): BBP_BuddyPress_Members->get_profile_url(1)
#1 /path/wp-includes/class-wp-hook.php(324): BBP_BuddyPress_Members->get_user_profile_url(1)
#2 /path/wp-includes/plugin.php(205): WP_Hook->apply_filters(1, Array)
#3 /path/wp-content/plugins/bbpress/includes/core/abstraction.php(471): apply_filters(‘bbp_pre_get_use…’, 1)
#4 /path/wp-content/plugins/bbpress/includes/users/template.php(560): bbp_maybe_intercept(‘bbp_pre_get_use…’, Array)
#5 /path/wp-content/plugins/bbpress/includes/replies/template.php(1280): bbp_get_user_profile_url(1)
#6 /path/wp-content/plugins/bbpress/includes/replies/template.php(1189): bbp_get_reply_author_url(775)
#7 /path/wp-content/plugins/bbpress/includes/users/template.php(2019): bbp_get_reply_author_link(Array)
#8 /path/wp-content/plugins/bbpress/includes/users/template.php(1990): bbp_get_author_link(Array)
#9 /path/wp-content/plugins/bbpress/templates/default/bbpress/loop-single-forum.php(70): bbp_author_link(Array)
#10 /path/wp-includes/template.php(792): require(‘/path…’)
#11 /path/wp-content/plugins/bbpress/includes/core/template-functions.php(103): load_template(‘/path…’, false)
#12 /path/wp-content/plugins/bbpress/includes/core/template-functions.php(41): bbp_locate_template(Array, true, false)
#13 /path/wp-content/plugins/bbpress/templates/default/bbpress/loop-forums.php(35): bbp_get_template_part(‘loop’, ‘single-forum’)
#14 /path/wp-includes/template.php(792): require(‘/path…’)
#15 /path/wp-content/plugins/bbpress/includes/core/template-functions.php(103): load_template(‘/path…’, false)
#16 /path/wp-content/plugins/bbpress/includes/core/template-functions.php(41): bbp_locate_template(Array, true, false)
#17 /path/wp-content/plugins/bbpress/templates/default/bbpress/content-archive-forum.php(27): bbp_get_template_part(‘loop’, ‘forums’)
#18 /path/wp-includes/template.php(792): require(‘/path…’)
#19 /path/wp-content/plugins/bbpress/includes/core/template-functions.php(103): load_template(‘/path…’, false)
#20 /path/wp-content/plugins/bbpress/includes/core/template-functions.php(41): bbp_locate_template(Array, true, false)
#21 /path/wp-content/plugins/bbpress/includes/common/shortcodes.php(197): bbp_get_template_part(‘content’, ‘archive-forum’)
#22 /path/wp-content/plugins/bbpress/includes/core/theme-compat.php(549): BBP_Shortcodes->display_forum_index()
#23 /path/wp-includes/class-wp-hook.php(324): bbp_template_include_theme_compat(‘/path…’)
#24 /path/wp-includes/plugin.php(205): WP_Hook->apply_filters(‘/path…’, Array)
#25 /path/wp-content/plugins/bbpress/includes/core/sub-actions.php(477): apply_filters(‘bbp_template_in…’, ‘/path…’)
#26 /path/wp-includes/class-wp-hook.php(324): bbp_template_include(‘/path…’)
#27 /path/wp-includes/plugin.php(205): WP_Hook->apply_filters(‘/path…’, Array)
#28 /path/wp-includes/template-loader.php(104): apply_filters(‘template_includ…’, ‘/path…’)
#29 /path/wp-blog-header.php(19): require_once(‘/path…’)
#30 /path/index.php(17): require(‘/path…’)
#31 {main} thrown in /path/wp-content/plugins/bbpress/includes/extend/buddypress/members.php on line 229

Any advice to get our site back to life ?

Hello, i get the following error after Updating to 12.0. Could you please help me? 🙂

WordPress-Version 6.4.2
Aktives Theme: Cera (Version 1.2.0)
Aktuelles Plugin: BuddyPress (Version 12.0.0)
PHP-Version 8.1.26

Ein Fehler vom Typ E_ERROR wurde in der Zeile 350 der Datei /homepages/10/d383743307/htdocs/######/wp-content/plugins/buddypress/bp-core/deprecated/12.0.php verursacht. Fehlermeldung: Uncaught Error: Call to undefined function bp_get_groups_directory_url() in /homepages/10/d383743307/htdocs/######/wp-content/plugins/buddypress/bp-core/deprecated/12.0.php:350
Stack trace:
#0 /homepages/10/d383743307/htdocs/######/wp-content/plugins/grimlock-buddypress/inc/widget/fields/class-grimlock-buddypress-groups-section-widget-fields.php(155): bp_get_groups_directory_permalink()
#1 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(324): Grimlock_BuddyPress_Groups_Section_Widget_Fields->change_defaults()
#2 /homepages/10/d383743307/htdocs/######/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#3 /homepages/10/d383743307/htdocs/######/wp-content/plugins/grimlock/inc/widget/class-grimlock-base-widget.php(21): apply_filters()
#4 /homepages/10/d383743307/htdocs/######/wp-content/plugins/grimlock-buddypress/inc/widget/class-grimlock-buddypress-groups-section-widget.php(29): Grimlock_Base_Widget->__construct()
#5 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-widget-factory.php(62): Grimlock_BuddyPress_Groups_Section_Widget->__construct()
#6 /homepages/10/d383743307/htdocs/######/wp-includes/widgets.php(115): WP_Widget_Factory->register()
#7 /homepages/10/d383743307/htdocs/######/wp-content/plugins/grimlock-buddypress/inc/class-grimlock-buddypress.php(202): register_widget()
#8 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(324): Grimlock_BuddyPress->widgets_init()
#9 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#10 /homepages/10/d383743307/htdocs/######/wp-includes/plugin.php(517): WP_Hook->do_action()
#11 /homepages/10/d383743307/htdocs/######/wp-includes/widgets.php(1858): do_action()
#12 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(324): wp_widgets_init()
#13 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#14 /homepages/10/d383743307/htdocs/######/wp-includes/plugin.php(517): WP_Hook->do_action()
#15 /homepages/10/d383743307/htdocs/######/wp-settings.php(643): do_action()
#16 /homepages/10/d383743307/htdocs/######/wp-config.php(116): require_once(‘/homepages/10/d…’)
#17 /homepages/10/d383743307/htdocs/######/wp-load.php(50): require_once(‘/homepages/10/d…’)
#18 /homepages/10/d383743307/htdocs/######/wp-login.php(12): require(‘/homepages/10/d…’)
#19 {main}

Thank you! I realized after I posted that it was the BP Classic Theme that was keeping the page view. Yes, it is the Astra theme. The option in customizer to use round profile images is no longer present after updating to 12.0.

BuddyPress 12.0 function bp_core_get_user_domain deprecated

Hi !

Since version 12.0 I get a critical error.
WordPress debug mode gives me this message :
Deprecated: La fonction bp_core_get_user_domain est obsolète depuis la version 12.0.0 ! Utilisez bp_members_get_user_url() à la place. in /home/nudeoep/www/wp-includes/functions.php on line 6031

I installed BP Classic and it resolves the problem.

BUT when I try to change the options of my Flatsome Theme, I don’t see the regular screen but this :
Dernières notes publiées (BuddyPress)
Titre :
Nombre max. à afficher :

It’s weird !

Thanks in adavance four your help !

I received this message from WordPress :

WordPress a trouvé une erreur avec l’une de vos extensions, « BP Classic »

Une erreur de type E_ERROR a été causée dans la ligne 206 du fichier /home/nudeoep/www/wp-content/plugins/bp-classic/inc/templates/classes/class-bp-classic-templates-nouveau-latest-activities.php. Message d’erreur : Uncaught Error: Call to undefined function bp_nouveau_get_activity_filters() in /home/nudeoep/www/wp-content/plugins/bp-classic/inc/templates/classes/class-bp-classic-templates-nouveau-latest-activities.php:206
Stack trace:
#0 /home/nudeoep/www/wp-includes/class-wp-widget.php(535): BP_Classic_Templates_Nouveau_Latest_Activities->form(Array)
#1 /home/nudeoep/www/wp-admin/includes/widgets.php(276): WP_Widget->form_callback(Array)
#2 /home/nudeoep/www/wp-includes/class-wp-customize-widgets.php(1148): wp_widget_control(Array, Array)
#3 /home/nudeoep/www/wp-includes/class-wp-customize-widgets.php(1096): WP_Customize_Widgets->get_widget_control(Array)
#4 /home/nudeoep/www/wp-includes/class-wp-customize-widgets.php(714): WP_Customize_Widgets->get_available_widgets()
#5 /home/nudeoep/www/wp-includes/class-wp-hook.php(324): WP_Customize_Widgets->enqueue_scripts(”)
#6 /home/nudeoep/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#7 /home/nudeoep/www/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#8 /home/nudeoep/www/wp-admin/customize.php(123): do_action(‘customize_contr…’)
#9 {main}
thrown

Details of my configuration :

WordPress version 6.4.2
Thème actif : Flatsome (version 3.18.2)
Extension actuelle : BP Classic (version 1.2.0)
PHP version 8.0.30