Forum Replies Created
-
In reply to: BuddyPress 12.0.0
Hi @yatesa01
About this:
> The option in customizer to use round profile images is no longer present after updating to 12.0.It’s not an issue, we’re removed it on purpose, to avoid messing with the active Theme’s way of displaying an avatar.
https://buddypress.trac.wordpress.org/ticket/8273You can easily get it back using this CSS rule:
.buddypress-wrap .avatar { border-radius: 50%; }In reply to: BuddyPress 12.0.0Hi @bmoreau92
Thanks for your feedback.
I agree it’s weird.
BP Classic also brings back the BP Legacy widgets. The Latest Activities is one of them. But this widget is only available if the BP Nouveau Template pack is active. It looks like although it’s the case this template pack is not loaded which is causing the error because one of its functions is used by the Latest Activities widget.
I’ve tried to reproduce an issue but wasn’t able. As it’s a premium theme, I cannot see what’s wrong.
If you do not need this BP Legacy widget, you can simply unhook it and it should fix the issue. You can add the following code into a bp-custom.php file for example.
function flatsome_weird_option_bug() { remove_action( 'bp_widgets_init', array( 'BP_Classic_Templates_Nouveau_Latest_Activities', 'register_widget' ) ); } add_action( 'bp_after_setup_theme', 'flatsome_weird_option_bug', 6 );In reply to: BuddyPress 12.0.0Hi @priyam1234
Can you test the following code to see if that’s enough for ACF to load its fields UI?
function priyam1234_generate_post_type_ui( $args = array() ) { $args['show_ui'] = current_user_can( 'manage_options' ); return $args; } add_filter( 'register_buddypress_post_type_args', 'priyam1234_generate_post_type_ui' );About your questions on BP URL functions, you can read this developer documentation resource which includes some examples of use for most of the described functions:
https://github.com/buddypress/buddypress/blob/master/docs/developer/functions/rewrites.mdIn reply to: BuddyPress 12.0.0yatesa01: I see from this other topic, it’s the Astra theme. I’m looking at it.
Here’s the ticket about the BP Blocks regression: https://buddypress.trac.wordpress.org/ticket/9037
In reply to: Member Nav Menu Items for WP6 FSE12.1.0 will be a minor release. There won’t be a 13.0.0 release just like the 13th floor often lacks in building. We’ll jump to 14.0.0 for our next major release.
How long will it take us to reach 14.0.0, it depends on the number of people who will contribute to it. 12.0.0 took us almost a year and 46 people contributed to it.
In reply to: BuddyPress 12.0.0Hi @yatesa01
Thanks a lot for your feedback.
About the URLs BP Settings tab it’s only available when the BP Classic plugin is not active. To have the ability to customize each BP URLs we need the BP Rewrites API.
About BP blocks being displayed differently, this is a regression and I’ll work on fixing this in next minor release.
About BP Nouveau, what is the kind of theme you are using? A regular one or a Block only theme ?
In reply to: BuddyPress 12.0.0Hi @nktine
Sorry to read about this issue, and thanks a lot for sharing your specific configuration.
Slug constants are deprecated since version 1.5.0 (meaning it’s been 12 years 3rd party plugins or themes should have stopped using them). Starting in 12.0.0, as slugs are totally customizable from the URL tabs of the BuddyPress settings screen, we’re not defining them anymore, that’s probably the reason of your fatal errors.
To solve this issue, you can try to define these constants from a bp-custom.php file for example, you’ll only get deprecated notices in this case. Let’s hope Grimlock will soon update his code
In reply to: BuddyPress 12.0.0@erotmil Awesome! I’m happy the issue is resolved 👌
In reply to: BuddyPress 12.0.0@jaymzwayne Thanks for your feedback I’ll try to figure out why there’s such an issue between Legacy wigdets and the BP Attachments Add-on.
In reply to: BuddyPress 12.0.0The Pages tab of the BuddyPress settings has been replaced by the URLs one where you can customize all BP URLs slugs. Directories, registration/activate pages are now managed ged from there. See:
https://github.com/buddypress/buddypress/blob/master/docs/user/administration/settings/urls.mdIf you need to add some of these pages to your WordPress menus, I advise you to read:
https://github.com/buddypress/buddypress/blob/master/docs/user/administration/navigations/README.mdIn reply to: BuddyPress 12.0.0Here is how you can get involved with documentation:
https://github.com/buddypress/buddypress/tree/master/docs/contributor/documentationYou and everyone are very welcome to contribute.
In reply to: BuddyPress 12.0.0Hi @chuchy10 thanks for your feedback I’ll look at it. I believe you can use the regular Menu Administration in the meantime.
In reply to: BuddyPress 12.0.0@erotmil this is a public forum, do not share access to your site. I never ask to log in to a user site, and I’ll never log in to edit a user site. I just deleted the access you shared in your previous reply.
Your custom page is out of BuddyPress scope. The only thing that has changed since 11.4.0 that could possibly interfere imho is the fact BuddyPress used to put its JavaScript and Styles everywhere on your site, including this page. You can try to use the gist the way I commented it to have these JavaScript and Styles back.
In reply to: BuddyPress 12.0.0@erotmil I just tested:
When I click on the “calendar request” button, I reach this page
https://yoursite.url/calendar-request/and the form below button is about requesting a calendar.When I click on the “website request” button, I reach this page
https://yoursite.url/website-request/and the form below button is about requesting a website.At first sight, I don’t see issues. Do buttons need to do something else?
Otherwise, you’ll need to refresh your pemalink settings (Settings > Permalinks, simply click on the form button) because BP directory/pages are not reachable for now.
I also commented on your gist to show you where the filter needs to be added.In reply to: new update crashed my sitesHi @beachcalsix
Thanks for your feedback, can you share the fatal error traced in your error_log file ? We performed many tests before releasing this upgrade and never encountered such an error (fatal).
In reply to: Member Nav Menu Items for WP6 FSEHi,
It’s on our todo list. Not available at the moment but probably at next major version.
In reply to: BuddyPress 12.0.0@erotmil you can turn WP_DEBUG to false. Deprecated notices need to be addressed, but they are not responsible for the bug.
BP Classic can be activated before or after BuddyPress 12.0.0. In 11.4.0 we suggested to activate it so that the 12.0.0 migration task is short circuited, but it can be done after, it will simply revert the 12.0.0 migration task.
I’ll look at your HTML page asap.
In reply to: BuddyPress 12.0.0About documentation: I agree with you. Writing what we need to do is nice. It would be even greater if you could take another step: contribute to it 😅.
We’ve tried to get contributors to help us twice to update https://codex.buddypress.org unfortunately we were not able to get enough people to help us.
For this particular release, we’ve made a big shift and I personally took the time to write docs about the effects for users as I wrote into the announcement post. You can read it here: https://github.com/buddypress/buddypress/blob/master/docs/user/administration/README.md
Problem is: being in the code makes you miss important things for users. The fact we now uses the URLs BP settings tab instead of the WordPress pages we used before to set BP directory slugs and titles does not seem to be too difficult to find to me. I see reading your and some other replies it’s not that easy.
Adding directory links to WP Menus hasn’t changed that much, here’s a direct link to the doc: https://github.com/buddypress/buddypress/blob/master/docs/user/administration/navigations/README.md
In reply to: New version 12.0.0 BugHello, thanks for your feedback and happy you found the way to solve the issue 👌
In reply to: All widgets removed after updateAwesome ! Thanks for confirming 👍
In reply to: BuddyPress 12.0.0Hi @dangbird
Many thanks to @vapvarun for working on it from the Reign theme 😍. I’m confident it should fix your issue with 12.0 in a near future.
1) we only add this cover image on the member’s profile page or into an activity when a member has changed their avatar or cover image
2 & 2b) I believe it’s something your active theme is adding, there are ways to override it using the BP Template hierarchy if you are using a child theme, but maybe your theme has an option or a more straightforward way of disabling it, have you tried to contact the theme author?In reply to: BuddyPress 12.0.0Hi @priyam1234 about ACF, the thing is we don’t use a UI to edit BP directory pages. As anyway we never used the content of the
pagepost type for BuddyPress content, now we’ve migrated to abuddypresspost type we’re not generating the corresponding UI in WP Admin. I’m going to look at it to see how we can integrate ACF with our new way of dealing with thebuddypresspost type. I just need 2 or 3 days to figure it out.In reply to: BuddyPress 12.0.0Hi @erotmil thanks for sharing this code. I don’t see anything particular that would conflict on the server side. Since your issue is about button visibility I wonder if the fact we’re not including BuddyPress template pack styles and scripts everywhere on the site but only in BuddyPress generated pages could be the reason why you’re not seeing the buttons of this custom page. If you already rolled back to 11.4.0 a good way to figure it out is to temporarily add this code into the functions.php of your theme:
remove_action( 'wp_enqueue_scripts', 'bp_enqueue_scripts', 10 );. Note that this code will remove all CSS and JS for BuddyPress, make sure to use it before refreshing your custom page from your browser, once refreshed if your buttons are gone, then we’ve found the issue. Remove immediately after the above code. If you still have BP 12.0 active, you can test adding the following code to see if it’s fixing the issue for your custom page:
add_filter( 'bp_enqueue_assets_in_bp_pages_only', '__return_false' );. If it’s the case you can leave this code, otherwise remove it.In reply to: BuddyPress 12.0.0Hi @erotmil Sorry to read about this issue, I’m not sure to understand what the custom code is doing. As you’re talking about widgets I guess it may contain some
<?php dynamic_sidebar( 'name_widget_zone' ); ?>. Have you checked your error_log to see if there were some errors? About BP Classic, it contains the BP Legacy widgets, they are automatically loaded if you’re not using the Block Widgets editor, the function you mentioned was used to do this check, I believe you don’t need to care about it in your case. If your custom code is viewable from a Github Gist for example, I can look at it to see if I can find an explanation to your issue.@claudiovillagra I understand your frustration. If I often talk about BP Classic when replying to support requests about the 12.0.0 upgrade that’s because it’s the Add-on we’ve built to “neutralize” the 12.0.0 change BP Plugins might not be ready with (even if we’ve been working on 12.0.0 and communicating about it for almost a year…). I thought Woffice was a plugin but find out it was a premium theme. Unfortunately I can’t look at their code to understand the issue. If you haven’t try BP Classic, what I would do in your case would be to put up a staging site to replicate your production site and give 12.0.0 some other tests, try BP Classic and if issues are not solved with it, try to identify the issue checking the error_log file or using
define( 'WP_DEBUG', true ).In reply to: BuddyPress 12.0.0Hi @dangbird
Thanks for your feedback, in version 11.4.0 we’ve (exceptionally) introduced a feature to display notifications only to admins to inform them about the massive change coming into 12.0.0. See https://buddypress.trac.wordpress.org/ticket/9007
This feature we called “Admin notifications” is temporarily overriding the notifications for all admin users as long as one of the admin clicks on the exclamation mark to read the important message we want him to read. This message is about when to activate BP Classic to preserve backwards compatibility required by a specific config (BP Plugins not updated for the last 4 months, the deprecated BP Default standalone theme activated or the need to still use BP Legacy widgets).
It may be the reason explaining what you saw with the Reign theme. It should disappear as soon as you read the Admin notification. Let me know if it helped you fix (or not) the issue with 12.0 for you.
