Topic: BuddyPress 12.0.0 · BuddyPress.org

BuddyPress 12.0.0

Mathieu Viet
Moderator

@imath

11 months, 2 weeks ago

Please read this post carefully before upgrading:

BuddyPress 12.0.0 “Nonno”

Viewing 25 replies - 101 through 125 (of 197 total)

← 1 2 3 4 5 6 7 8 →

jaymzwayne
Participant

@jaymzwayne

11 months, 1 week ago

Perfect thank you very much good sir there’s not many plug-in developers that show this much care and respect to their users but he pressed has shown a great deal of respect to everyone keeping everyone properly informed and and always being very responsive shows a great deal of respect maybe at a later time I may be interested in going back to the 12 very but for now I need it to be back to the way it used to be until I can re-engineer all of my coding to catch up to the 12 version thank you again

Mathieu Viet
Moderator

@imath

11 months, 1 week ago

Sure, you’re welcome 👌

priyam1234
Participant

@priyam1234

11 months, 1 week ago

Hello, I noticed that I can’t retrieve the ID from your directory page URL using ‘url_to_postid()’. Could you provide guidance? Additionally, I’m having difficulty understanding the function you sent for ACF fields.

claudiovillagra
Participant

@claudiovillagra

11 months, 1 week ago

Woffice just made an update, it fix it.

However, we lost the customization of BuddyPress Birthdays…

@imath Thoughts?

Mathieu Viet
Moderator

@imath

11 months, 1 week 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.

Mathieu Viet
Moderator

@imath

11 months, 1 week ago

Hi @claudiovillagra

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

erotmil
Participant

@erotmil

11 months, 1 week ago

buddypress birthdays looks like a wbcom designs widget, I’m gonna try and install it on a site with buddypress 12 to see if it works, will report back

mattobiwan1982
Participant

@mattobiwan1982

11 months, 1 week ago

I have gone back to version 11.40 and was wondering how I can hide certain pages etc fron non regsitered members.

Mathieu Viet
Moderator

@imath

11 months, 1 week 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.

AWOL
Participant

@awol

11 months, 1 week ago

I am attempting to ensure that all the deprecated functions are either changed, or the plugins that are still using them are informed, but I have one that is appearing in the debug log that I can’t trace, as follows:
PHP Deprecated: Function bp_get_displayed_user_link is deprecated since version 12.0.0! Use bp_displayed_user_url() instead. in /wp-includes/functions.php on line 6031

Obviously the message is referring to the file that generates the message, and not the file where the function is being used, so any tips on how I can find this? I am aware of the BP-Classic plugin, and have it installed, but deactivated it to see what needs addressing. I have gone through all my own code and customisations, as well as several plugin files, but it is like a needle in a haystack, so is there some method I can use to trace this? Or any way to change the debug log to be more useful?!

cristan17
Participant

@cristan17

11 months, 1 week ago

Hello, thank you for your assistance. I have upgraded to BuddyPress v12, but now I am facing an issue. I am unable to customize my site from WordPress, specifically under APPEARANCE/CUSTOMIZE. Every time I try to customize the site, I receive an error message. Even the widget page is not loading properly for customization and some widgets stopped working (eg: who’s online widget)

This issue prompted me to use WP Rollback to revert to the previous version, but going back broke my site. Is there a fix for this? I would really appreciate your help.

priyam1234
Participant

@priyam1234

11 months, 1 week ago

You and your teamar are great. I have one last question . i have my all ACF fields in set_general_options() function. could you please provied me hook with the help of i can put that field in your <<BuddyPress directories>>

priyam1234
Participant

@priyam1234

11 months, 1 week ago

Okky i found my issue thank you so much for your every support.

Mathieu Viet
Moderator

@imath

11 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

priyam1234
Participant

@priyam1234

11 months ago

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.

perchenet
Participant

@perchenet

11 months ago

Hello everyone, bonjour Mathieu

Bravo pour le travail !

Since the update in 12, I have a slug problem.

My BP is installed as a sub-site, according to the procedure described here https://codex.buddypress.org/getting-started/installation-in-wordpress-multisite/#b-network-wide-activation-buddypress-root-blog-in-secondary-site

Main site: auposte.fr
BP site: comico.auposte.fr

However, I can’t impose my slugs. WP refuses to overwrite the slugs and use the basic slugs. It always adds -3 (activity-3, members-3).

Example: https://www.auposte.fr/wp-admin/network/admin.php?page=bp-rewrites won’t register simple slugs (without the -3). I tried in English (groups, members): same defeat.

What I don’t understand is how BuddyPress generates different slugs (members, members, members-3) for the same thing?

Where are the slugs managed in the database since BP version 12? Can I modify them in the database directly?

Thanks/Merci mille fois Mathieu et l’équipe!
David

priyam1234
Participant

@priyam1234

11 months ago

now its compatible with better messages new version thank you

Mathieu Viet
Moderator

@imath

11 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

Mathieu Viet
Moderator

@imath

11 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?

Mathieu Viet
Moderator

@imath

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

perchenet
Participant

@perchenet

11 months ago

Thank you @imath !

I did https://www.auposte.fr/wp-admin/network/admin.php?page=bp-tools
I used the « Reset slugs » but I got a critical errors, without changing the standard slugs.

I can delete everything if it is better to do ?

Thank you!

perchenet
Participant

@perchenet

11 months ago

Here we are the wp_{site_id}_option values of the bp-pages option name:

a:6:{s:8:"activity";i:5404;s:6:"groups";i:5405;s:5:"blogs";i:5406;s:7:"members";i:5407;s:8:"register";i:5408;s:8:"activate";i:5409;}

But this not what I see in admin.php?page=bp-rewrites (BP components)

perchenet
Participant

@perchenet

11 months ago

I saw somthing strange in my wp_{site_id}_option

Option_id: 1172
Option_name: rewrite_rules
Option values:
bp_members=1&bp_member=$matches[1]&bp_member_component=$matches[2]&bp_member_action=$matches[3]&bp_member_action_variables=$matches[4]";s:36:"membres-3/([^/]+)/([^/]+)/([^/]+)/?$";

Mathieu Viet
Moderator

@imath

11 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.
perchenet
Participant

@perchenet

11 months ago
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      |
+----+-----------+
```