Hi, after updating to 12.0.0 I see an error:
Deprecated: Function bp_core_retain_legacy_widgets is deprecated since version 12.0.0 with no alternative available. in /wp-includes/functions.php on line 6031
Can you tell me how to fix it?
It’s a deprecation notice. According to it you are still using BP Legacy Widgets. These widgets were moved into our Backwards compatibility Add-on « BP Classic »:
You can find them back downloading and activating this Add-on.
I activated this plugin before upgrading to 12.0.0!
Thanks for this new information, this notice shouldn’t be shown then. I’m going to look at it more deeply asap. I’ll keep you updated.
Hi there! in the latest 12.0 update, I can’t see a way to set pages to buddypress core functionalities like – members, activity streams, register and activate. Is there a new way of doing these things? Thanks
My activity feed page stop working with the upgrade. How do I fix it.
The new way to customize URLs or directory titles is happening in Settings > BuddyPress then click on the URLs tab. More info about it here: https://github.com/buddypress/buddypress/blob/master/docs/user/administration/settings/urls.md
If for some reason (compatibility with a 3rd party BP plugin) you need to get this page back, you can use the BP Classic add-on.
BP 12.0.0 SHOW CRITICAL ERRORS ” There has been a critical error on this website.” WITH OR WITHOUT BP CLASSIC PLUGINS & LEGACY.
Sorry to read about it, we never had such errors during our tests, can you give us some more details about it? Eg: the last lines of your error_log file ?
I run/help administer quite a number of BuddyPress sites (and I greatly appreciate all of the work that makes ours possible!), but almost all of the sites that I administer or assist with are not working, even with the BP Classic plugin installed and activated.
Conflicts so far include: Grimlock BP add-ons (required for several Themeforest themes), Kleo (very popular Themeforest theme), and any of the sites using Visual Composer/WP Bakery widgets. All of these sites continue to throw errors (or have broken displays in the case of WP Bakery widgets), even with BP Classic installed and activated. I have stopped upgrading other sites until I’m able to figure out what is causing these to crash, even with the BPC plugin activated, but I’d assume that there are probably additional conflicts with the 5 other themes we utilize.
The only sites that continue to be fully operational are those running Divi (with BP Classic installed and activated) or WP Default themes.
I am reaching out to theme and plugin authors for updates, but this seems to be pretty widespread, so I’m hoping there’s some other conflict or issue that I’m missing or not understanding.
I greatly appreciate any help or guidance. Thanks again for all of the work that goes into this plugin. 🙂
@imath thank you so much for your prompt response. So to link the page, the page name and the directory tile has to be the same?
There are numerous errors in my BP site with this new update. I also do not understand how the BP Classic plugin ever got installed on my site without my permission.
But what I really want to know is if I can go back to the previous version of BP and not crash my site? And how do I do that? I do have WP Rollback, latest version, but it warns me of a risk of crashing the site if I do…
@varadkk if I understand well you need to get the link to your BuddyPress directories or to the registration page.
For these pages, it should always be
https://yoursite.url/$slug_valuewhere the $slug_value is the value of the slug input.
You can alternatively use the BuddyPress Directory menu or logged out member menu items if you use a regular theme, see https://github.com/buddypress/buddypress/blob/master/docs/user/administration/navigations/README.md
I have the same issue… I use woffice theme (themeforest)
debug.log show this if I activate ONLY Buddypress plugin without no other one…
[12-Dec-2023 14:48:45 UTC] PHP Deprecated: str_starts_with(): Passing null to parameter #1 ($haystack) of type string is deprecated in Path….\wp-includes\class-wp-styles.php on line 430
I would be very thankful for help!
I believe there can be errors when a plugin/theme has not been updated since the last 2 versions of BuddyPress, we only load by default deprecated functions back to 2 previous versions. I suggest you to use 2 constants in your wp-config.php file:
define( 'BP_LOAD_DEPRECATED', true );this will load all deprecated functions (from version 12.0 back to version 1.2)
– Errors should become deprecation notices. Errors/notices should never be output on front-end, so if some errors are output on front-end, I advise you to also use
define( 'WP_DEBUG_DISPLAY', false );
@fraughtithrouble 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 » to the one of you version, see https://codex.buddypress.org/releases/. For instance for version 11.4.0, into the
_bp_db_versionoption should be
13408. Only then download and activate a previous BuddyPress version (11.4.0).
@westmdresearch I’m sorry to read about all these troubles, we took all possible precautions to avoid it on our side: beta period was extended to 4/5 months, we documented the changes, we’ve built a backcompat plugin, unfortunately we cannot test and fix all free or premium plugins, this part remains their responsibility.
Thanks for your feedback, as we don’t use this function (see https://github.com/search?q=repo%3Abuddypress%2Fbuddypress+str_starts_with&type=code ), It’s probably a plugin or a theme hooking to a BuddyPress filter or action.
Do you have the full error trace ?
same as BP 12.0.0 Show error with KLEO, BUDDYAPP & WEB BECARY. I USE BUDDYAPP.
Thanks @imath for the detailed response!
Is there a list of deprecated functions that we could use as a starting point to troubleshoot the critical and non-critical errors? By checking error logs, all of the errors seem to be in custom theme functions for BuddyPress-specific themes, but it would be handy to have a starting point with so many themes throwing different errors (because of custom function naming). All of the non BP-specific themes I’ve toggled through appear to be working fine with BPClassic installed and activated, so this could be the root issue I’m seeing across different installations (I’m thinking it has something to do with pulling user functions, user meta, messages, etc… or something universal that is only present on themes with BP support built-in).
Some of the sites we work with are 5-10 years old, and even though we update themes/plugins as they become available, there are a lot of functional BP themes/plugins that have been psuedo-abandoned/un-updated, that I’d like to try to update with my limited BP-specific knowledge.
I completely understand that progress must be made, so I’d like to try to see what I can do on my end to support the legacy ecosystem that seems to grow more and more each year. BP is an incredibly powerful tool for community work and non-profits, but many of the tools, plugins, and themes that we’ve used will have to be carried forward by the community to remain functional.
Thanks again, and have a great day!
I’ve just checked about
bp_core_retain_legacy_widgets(). It’s not used by BuddyPress or BP Classic. I guess another plugin, a theme or some custom code is using it. To fix the issue:
1. if you’re the author of the custom code, you can replace it with:
function_exists( 'bp_classic_retain_legacy_widgets' ) && bp_classic_retain_legacy_widgets();
2. otherwise you can report to the plugin/theme author this issue.
Sure, here’s the list organized by the BuddyPress version when there were deprecated:
Thank you for your support, as you wrote above the problem was in the template! I fixed it as recommended and everything worked!
I want to add that today I managed to test two dozen third-party plugins and half of them stopped working properly with the 12.0.0 update, so the problem is not with BuddyPress but with third-party developers who have not prepared for this update!
Thanks for confirming it fixed the issue and for your feedback.
I am sorry to read 50% of these third party plugins are not ready for 12.0.0. As I’ve said a bit earlier, we’ve tried our best to raise most 3rd party plugin authors attention about the important change we’ve introduced in 12.0.0:
– we extended our beta period to 4 months
– we documented the changes.
– we’ve built a backwards compatibility Add-on
– we’ve added a new feature to display Admin notifications in version 11.4.0.
For those having issues like i did with the ACTIVITY PAGE NOT LOADING..
Heres what i did to recover it after i lost all of my content i forgot this 12 update was coming in and i had all of my plugins set for auto update. while i was moding my marketplace i thought i messed everything up and did a total complete fresh install of everything.. WRONGGG ANSWER GESSH MONTHS OF WORK LOSSED. MY FAULT. so here is the fix as they suggested to do go to plugins get the classic buddy press then activate it then go to settings on the left side of your dashboard then go to pages at the top click it and then go to the bottom and choose save it resolves your activity page not loading.
What i saw was my site said there was a critical error! message and my site sent me this message to my emails about it. so i hope you read this first before you made the same huge mistake i made. Great job developers for making it clear that this was gonna take place it was my mistake i made not making a recent back up of my site and chose the wrong actions. lol keep up the great work..!!!!!
- The topic ‘BuddyPress 12.0.0’ is closed to new replies.