BuddyPress 1.6.1 is now available! This version contains fixes for a few edge case bugs that came up after BuddyPress 1.6 was released last week, including: full compatibility with Multisite installations using NOBLOGREDIRECT; a regression in one of our avatar functions that caused avatars to be malformed in some themes; and a load order issue that caused fatal errors with some legacy themes. You can check out the changelog for the release at our bug tracker.
BP 1.6.1 is a recommended upgrade for all installations running BuddyPress 1.6. Have you been holding off on upgrading to 1.6? We’ve got you covered: the BP 1.6 section of the BuddyPress Codex is full of helpful information that’ll help you get your site up to date.
Upgrade to BuddyPress 1.6.1 from your WordPress plugin updater, or download directly from the wordpress.org plugin repository today!
Bp updated successfully! nice work 🙂
I didn’t understand why bp plugin and frisco theme are disabled automatically after update?
Similar issue… was using ‘BuddyPress Default’ with some widgets and display option changes and found the site was running ‘Twenty Eleven’ after the upgrade. Switching back to ‘BuddyPress Default’, I found that the settings were lost. No big deal, I made the widget changes etc., but seemed a bit odd…
Does this require any child theme changes from 1.6?
No theme changes – just a couple of bugs fixed in the core logic.
Is there any reason you do not use the proper changelog format of other WordPress plugins?
It is extremely frustrating to click on the view details on the update screen and not see the changelog for the plugin.
I’m only pointed to a release page which doesn’t list the changes!. I have to search around the website to find this blog post which still doesn’t list all the changes; I have to follow a link to the bug tracker. It’s incredibly annoying.
Please, at a minimum just copy the bug titles from the bug tracker into the changelog section of the readme! Preferably write a proper changelog.
Mike
Mike – We don’t put the changelog inline in the readme file because it would make it extremely long. Our major releases sometimes have hundreds of fixes. We have full changelogs available at https://codex.buddypress.org/releases
I did a crummy job linking to the 1.6.1 changelog https://codex.buddypress.org/releases/version-1-6-1/ in our release notes and this blog post. I’ll try to be more conscientious about that in the future. Sorry to have raised your incredible annoyance.
Boone, I was not incredibly annoyed, and I can understand redirecting people to the website for the longer posts. Maybe linking to the releases https://codex.buddypress.org/releases instead of https://buddypress.org/about/release-history/ in the WordPress Plugin popup and have the verbiage reflect that if the version number doesn’t match due to a mistake like this one to check there. Thanks!
Good tip, HEX. Thanks!
Maybe at least linking to the codex age for the release in the changelog part of the readme would be a start.
Perhaps list the three most important changes and then link to the codex page.
This release happened to come in the middle of a go-live ready for customer testing. I needed to make an assessment of whether to update based on the changes: vital bug fix/security issue or something non-vital like new language translation (another plugin update had that on the same day)
The update to 1.6.1 doesn’t fix any avatar issues I have with avatars since I updated to 1.6 with Salutation theme (AND BP Default). It’s all the same – Buddypress loads always another avatar size. Sometimes …-bpfull-16×16.jpg another time -bpfull-24×24.jpg and all of them are resized to 80×80 by CSS. That just looks awful… ;(
Is there still a problem with the avatar fix?!
Philipp – BuddyPress does not create avatars of the form -bpfull-24×24.jpg. This must be a customization by Salutation.
The avatar fix in BP 1.6.1 had to do with displaying the URL vs the HTML img entity, and was indeed fixed.
Thanks for the update! for me it fixed an annoying bug 🙂
I’ve been waiting for this for a couple of my web development client sites. Hopefully this fixes a couple of bugs my clients have reported!