Mathieu Viet

Thanks for your review.

I agree testing on a staging site where your production site is cloned on is important. I would advice not to wait until the major version is published as it’s a bit too late. I wish you and other users like the one who published this review for example give the BP Core Team some of their time to beta test major releases. Beta period for 12.0.0 lasted more than 4 months and we haven’t got any help from many end users to anticipate issues like the ones you’re talking about. For 12.0.0 we knew some specific / very customized configs would have difficulties with it. The important change we made in 12.0.0 is crucial for next BuddyPress features some BP plugins might still not be ready for it, that’s why we built the BP Classic Add-on you’re talking about.

Hi @earl_d,

Thanks for your report. Looks like the same file was included more than once.

I’ll work on a fix from this GH issue: https://github.com/buddypress/bp-attachments/issues/103

Hi @mike2972

Thanks a lot for your review & sorry to read about your issues.

BuddyPress version 12.0.0 doesn’t break sites or communities. The best way to figure it out is to start a fresh install of WordPress and only activate BuddyPress 12.0.0.

But you’re right, when updating to 12.0.0, as we’ve been informing for almost a year, some admins need to take precautions because of some of the 3rd party plugins they installed :

• Version 11.0 added (into its Hello modal that opens when you activate BuddyPress for the first time) announcement about the fact we would make a big shift in 12.0.0 and we would make a backwards compatibility add-on available because we were anticipating some 3rd party plugins or themes wouldn’t be ready for the change.
• we had a 5 months beta period and repeated about the important need for plugins and themes to test our pre-releases to be ready for the best of you and other users.
• we’ve built the BP Classic plugin to bring the backwards compatibility to specific configurations like yours informing since 12.0.0-beta1 : if your 3rd party BP plugins were not updated for the last 4 months, or if you are still using the BP Default theme (we deprecated 10 years ago) or if you are still using BP Legacy widgets, please activate BP Classic.
• In 11.4.0 we added a new feature: Admin notifications to display a message to site admin about BP Classic
• We’ve updated the readme.txt to also warn users about the major changes.
• we’ve added developer and user documentation about the change
• we’re now helping users like you from our support forum.

We took actions to prevent such a situation to happen, the only thing we couldn’t do is perform the update of your site or update the code of 3rd party plugins & themes (mostly premium).

We can’t bring great new features and at the same time do not touch our code. The 1 star of your review seems very unfair with the work the BuddyPress Core team achieved during this year.

Thanks for your feedback, I’ll work on it from there:

https://github.com/buddypress/bp-attachments/issues/98

Thanks for your feedback, I’ll work on it from there:

https://github.com/buddypress/bp-attachments/issues/97

Hi @bclaim

Thanks for your feedback. You’re right, this BuddyPress Add-on mainly uses the REST API. There’s no documentation about it, but I totally agree with you, we absolutely need one!

I’ll work on it from there: https://github.com/buddypress/bp-attachments/issues/93

I’ve just published 1.2.0 to fix this issue.

I’ve just published 1.2.0 to fix this issue.

Hi @awol

I confirm the issue, I’ll fix it asap. You can follow my progress from this GH issue.

Hi @earl_d

Thanks for your feedback, the component is not being retired!! It’s caused by a wrong use of a BuddyPress filter hook. It will be fixed in next minor release.

You can follow my progress from this GH issue.

Thanks for your report. I’ll check again.

Hi @awol

I can understand how frustrated you feel. But there are so many themes available not to mention custom styling people like you are doing, that it’s very difficult to adapt perfectly magically to your theme. We inject our templates with minimal styling so that you don’t need to use a specific BuddyPress theme to use the plugin, you can directly use it within your custom theme. The downside is that you need to add some lines of CSS.

Once we will make possible to edit BuddyPress area from the Site Editor for Block only themes, this will probably be improved. If more people contribute to BuddyPress it can happen during the next release.

Hi @testovac

You can achieve this using the BP Theme hierarchy. You simply need to check what is you active template pack from the BuddyPress panel of the WordPress site-health info tab. Let’s say it’s BP Nouveau.

From your active theme create a new PHP file named:

/wp-content/themes/your-active-theme/buddypress/members/single/index-component-messages.php

Into this file copy the content of your theme’s page.php template and replace the post loop with <div id="buddypress"></div>

Inside this div paste the content of:

1. the /wp-content/plugins/buddypress/bp-templates/bp-nouveau/buddypress/members/single/member-header.php
2. then /wp-content/plugins/buddypress/bp-templates/bp-nouveau/buddypress/members/single/messages.php

Repeat all these steps replacing messages by notifications

Version 1.1.0 has just been released, there’s now a delete avatar link.

Version 1.1.0 has just been released, you can now use the filter.