BuddyPress 8.0.0: Call for Tickets

BuddyPress 7.0.0 was released on December 9, 2020. We did the 7.0.0 release review during our latest “dev-chat”, just before the end of the year we shared with you a wrap-up post about 2020, today we’re inviting you to contribute to 8.0.0’s kick-off by replying to this call for tickets.

The priorities of the BuddyPress community matter, please let us know what:

  • bug(s) you’d like to get fixed for 8.0.0?
  • improvement(s) you’d like to see in 8.0.0?
  • new feature(s) you’d like to see introduced in 8.0.0?

Share your wish-list!

To do so, you simply need to pick the ticket number(s) you think we should prioritize on from our code source management tool and paste them into this post’s comment form. If you’d like to, you can also share your ideas about the corresponding ticket(s). If some “already shared” tickets are also interesting you: use the ⭐️ Like feature to second them.

You need inspiration?

PS: don’t hesitate to add a new ticket, if you haven’t found a match into the above queries 

PS2: Adding your ticket here won’t necessarily guarantee inclusion. But no one can fix things they can’t see, so bravely share your thoughts!

Deadline

This call for tickets will end on January 13, but we’ll begin discussing about what we’d like to see in BuddyPress 8.0.0 during our next dev-chat (January 6) : so the sooner you share your wish-list the better!

#8-0-0, #tickets

BP Dev-Chat Agenda: December 16, 2020

Hi BuddyPress contributors!

Please join the last #BuddyPress developer meeting of the year that will happen on December 16 at 19:00 UTC (tomorrow), here’s our agenda:

  • 7.0.0 release first feedbacks & results
  • Let’s talk about our 8.0.0 wishlist!
  • Open floor

Thanks in advance for your contributions 🤶🏾🎅🏻🎄.

#agenda, #dev-chat

BP Dev-Chat Summary: December 2, 2020

7.0.0 release tasks progress

We started the dev chat chacking our progress about our next major release tasks.

TasksOwnerProgress
BP REST API documentation updates@im4th100%
BP Survey results@im4th100%
7.0.0 Release note@vapvarun100%
7.0.0 Credits update:
– BuddyPress Trac
– BP REST GitHub repository
– Translators

@dcavins
@im4th
@im4th

100%
100%
100%
7.0.0 Pizza Restaurant name@dcavins🤫
7.0.0 Announcement post@im4th20%

7.0.0 second release candidate

The main goal of this release candidate is to beta test improvements brought to the BP Nouveau’s compatibility with the WordPress 5.6 new default theme “Twenty Twenty-One” (see #8395). @im4th insisted on the fact it was important to make sure text was readable in both modes : dark and light and as the 7.0.0 final release will happen one or two days after WordPress 5.6, it’s important BuddyPress looks nice in Twenty Twenty-One. The initial patch attached to the ticket is using the companion stylesheet feature so that styles are only loaded for this theme or this theme’s child themes.

@vapvarun said he would test the patch asap and that he would probably improve it. That’s what he did a few days after the development meeting.

The RC2 was released very soon after.

7.0.0 release schedule update

  • 7.0.0-RC1: November 20 (string freeze).
  • 7.0.0-RC2: December 2nd
  • 7.0.0: December 9th (asap!)

We still need to finish the announcement post of the release, so we couldn’t have it packaged to the scheduled date 😞. As soon as it is ready, we will package it. Thanks in advance for your comprehension.

Open floor

Topics we’ve been talking about:

  • How to find ways to get more contributors to beta test BuddyPress? @vapvarun suggested:
    • Write a todo list about tasks to achieve for next release (8.0)
    • Improve documentation about BP support for themes
    • Make template customization easier for users (WP FSE?)
  • Possible 8.0 early tasks: #7162 & working on giving more control to the user about the registration form (allowing users to select what xProfile fields to use in this form).
  • What about having a new BP Standalone theme? @johnjamesjacoby shared his wishes about it:
    • a 3 columns bp-default looking “chat app” theme.
    • It’s time to take advantage of all the work that’s gone into BuddyPress since the beginning, and use that to rethink what a “bp-default” looking theme would be today.
    • It should be responsive and use the BP REST API.
  • What about having a BP Specific area into WP Admin to manage every feature?

Next Dev-Chat

It will happen on December 16 at 19:00 UTC and of course in #BuddyPress. If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

#7-0-0, #dev-chat, #summary

Welcome to BuddyPress Filippi!

Hello!

BuddyPress 7.0.0 “Filippi” has just been delivered, enjoy it 🍕 ! Thanks again to all contributors who helped us to build it and translate it 😍, here’s the official announcement post:

https://buddypress.org/2020/12/buddypress-7-0-0-filippi/

#7-0-0, #release

BuddyPress 2020 survey results

Hi everyone,

We’ve just published the BuddyPress 2020 survey results, you can check them from our official site:

Many thanks to all participants 😍.

#2020

BP Dev-Chat Summary: November 18, 2020

6.4.0 “PHP 8.0” compatibility release

BuddyPress 6.4.0 has been released yesterday, as we’ve been discussing during the development meeting, it includes fixes to PHP 8.0 deprecated notices for BP Core & BP REST. It also includes a security fix. Read more about this release.

7.0.0 release tasks progress

TasksOwnerProgress
BP REST API documentation updates@im4th100%
BP Survey results@im4th0%
7.0.0 Release note@vapvarun40%
7.0.0 Credits update:
– BuddyPress Trac
– BP REST GitHub repository
Translators

@dcavins
@im4th
@im4th

100%
100%
0%
7.0.0 Pizza Restaurant name@dcavins🤫
7.0.0 Announcement post@im4th20%

@vapvarun has been working on the release note, the remaining things to write is the changelog. @johnjamesjacoby removed the link to the BP Survey on our official site, @im4th needs to write a post about the results and publish it on BuddyPress.org asap.

7.0.0 first release candidate

We’ve spent the rest of the meeting working on getting the 7.0.0-RC1release ready:

  • @dcavins reviewed the Hello Screen texts 😍 (#8376).
  • @im4th worked on improving the Activity Embed block instructions (#8397) as only public activities can be embed into a post or a page.
  • @vapvarun tested #8394.
  • Finally we decided to include the feature to list the displayed Member’s Member Types into their profile header (#8394) as the poll @im4th made on Twitter got 83% votes for 🙌.

7.0.0-RC1 has been released 2 days late (November 20) according to the initial schedule. It’s an important step, BuddyPress plugin/theme authors should really test their piece of work against it so that our users can fully enjoy 7.0.0. If you find a bug, please open a ticket to report it on our Trac environment or use this support topic.

RC1 also marks the string freeze point of the 7.0.0 release schedule. So we will not add/edit or delete i18n strings until 7.0.0 is released. Just like what we did for 6.0.0, we will credit people who contributed to translating BuddyPress into as many languages as possible. Don’t hesitate to join the effort!

Here’s 7.0.0 (development column on GlotPress) translation tops so far:

LocaleProgress
English 🇬🇧100%
Romanian 🇷🇴100%
French 🇫🇷100%
Chinese 🇨🇳99%
Czech 🇨🇿98%

7.0.0 release schedule update

Next Dev-Chat

It will happen on December 4 at 19:00 UTC and of course in #BuddyPress. If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

#7-0-0, #dev-chat, #summary

Meet the new default avatar for Sites

The BuddyPress Members and Groups were the only components to have a default avatar so far. The Site Tracking component felt very strongly about it, protesting it was about time to give it a default “blavatar” (blog avatar) 😁. It’s finally happening in BuddyPress 7.0.0 🙌.

The default site avatar

The default blavatar !

Multisite WordPress configurations will be able to find it when displaying the Sites directory. It appears when sites of the loop doesn’t have a WordPress Site Icon set. Here’s how this directory will look like once BuddyPress 7.0.0 will be released.

Using a Site Icon as the Site’s avatar

The Site Icon / Site Avatar synchronization of the Site Tracking component was introduced in BuddyPress 2.7.0, but here’s a reminder about how to set a Site Icon for a site of your network.

The Site Icon Customizer’s panel

The primary use of the WordPress Site Icon feature is to generate icons for your site so that, for example, it displays into your browser’s tab (favicon). You can set it using the Cutomizer from the corresponding site of the network. In our example the WordPress site. Once the Customizer is loaded, head over to the Site Identity panel and you’ll find the place to set the Site Icon at the bottom of it (⚠️ don’t confuse with the Site Logo). Click on the “Select Site Icon” button (or the “Change image” button if you already have a Site Icon in place) to upload your image and crop it to match WordPress needs. Once you’ll publish your changes, BuddyPress will automagically use this image to set the Site’s avatar and use it everywhere the Site Tracking component is displaying your site (into the Sites directory and into the “Sites” tab of the Member’s front-end profile page for the users attached to this site).

Tada!

Keeping the Site’s admin avatar as the default Site’s avatar

If you prefer to keep on displaying the Site’s admin avatar as the default site avatar after BuddyPress 7.0.0 is released, you can always do so using the following piece of code into your bp-custom.php file for example.

/**
 * Filter to carry on using site admin avatar.
 *
 * @param array $args The Blog Avatar arguments.
 * @return array      The Blog Avatar arguments.
 */
function carry_on_using_site_admin_avatar( $args ) {
	global $blogs_template;

	if ( isset( $blogs_template->blog->admin_user_id ) ) {
		$args['admin_user_id'] = (int) $blogs_template->blog->admin_user_id;
		$args['alt']           = sprintf(
			/* translators: %s: the author display name */
			__( 'Profile picture of site author %s', 'buddypress' ),
			esc_attr( bp_core_get_user_displayname( $args['admin_user_id'] ) )
		);
	}

	return $args;
}
add_filter( 'bp_before_blog_avatar_parse_args', 'carry_on_using_site_admin_avatar', 10, 1 );

If you’d like to know the story of this change, you can get more information reading the #8179 ticket.

The new default site avatar will be available into the BuddyPress 7.0.0-beta2 release we plan to publish next Wednesday, we strongly encourage you to test it as well as all the 7.0.0 new features 🙏.

#7-0-0, #8179, #site-tracking

BP Dev-Chat Agenda: November 4, 2020

Our next development meeting will happen this Wednesday November 4 at 19:00 UTC in #BuddyPress. Here’s our agenda:

  • 7.0.0 latest updates.
  • Last checks before releasing 7.0.0-beta2.
  • Open floor.

If you have anything you wish to add (or remove) to this agenda or specific items related to those listed above, please leave a comment below.

PS : 7.0.0-beta2 will be packaged just after the meeting.

#7-0-0, #agenda, #dev-chat

Assigning multiple Member Types to a user

Starting in BuddyPress 7.0.0, community administrators will be able to assign more than one member type directly from the user’s WP-Admin/Extended profile page.

The regular select box of the Member Type metabox has been replaced by a multiple select box so that you can assign as many member types as you need to a single user.

Be aware of a change we made to the Member Types bulk actions behavior.

Community Administrators can bulk assign a member type to a list of users from the corresponding Administration screen by:

  1. activating the corresponding checkboxes at the left of users avatars.
  2. selecting the Member Type name from the Member Types dropdown list that is located over or under the users table.
  3. clicking on the change button immediately at the right of this dropdown list.

This strictly means you are changing the existing member type(s) of a user to the selected member type. In other words, if the user nicknamed imath was selected, he would be reassigned to the Lead Developer member type only (and lose the Pizza lover one 🍕).

If you choose the “No Member Type” option, then all the assigned member types of the selected user(s) will be removed.

If you want to read about how this change was made and thank the contributors who made it happen, head over this trac ticket.

By the way, did you know you’ll be able to create, edit, delete Member & Group Types directly from your WordPress Administration in BuddyPress 7.0.0 ?

#7-0-0, #member-types

BP Dev-Chat Summary: October 21, 2020

7.0.0-beta1 feedbacks

7.0.0-beta1 was released on October 16. So far, nothing specific to it was posted into our support forums. At the time we had the meeting, @im4th, thanks to @IAmTheWebb tests, had reported an issue (now fixed) with the Activity Embed block into our Trac environment. This last Friday @k3690 reported a wrong usage of the member term into a Group Type meta property (now fixed).

7.0.0 remaining tickets

  • #8292 @vapvarun submitted a patch during the meeting 💪, @im4th reviewed it some time after, brought some minor improvements and it has been fixed yesterday. It’s now possible to assigned more than one member types to users from their WP Admin Extended Profile 🙌 .
  • About #8179, @im4th asked @vapvarun to update the ticket with 2 squared corner avatars with these dimensions: 150px x 150px (full) & 50px x 50px (thumb). @im4th will try to progress on a patch in the meantime.
  • We’ve postponed #8093 (Profile Field visibility improvements) to a next milestone.
  • #8375 was reopened by the reporter, as the filter we’ve added wasn’t matching its needs. @dcavins @johnjamesjacoby & @im4th have been discussing about it last week in #BuddyPress and came to the conclusion a possible better place to allow the invitation table’s name filtering was to include the {$bp_prefix}bp_invitations table name into the global_tables property of the BP_Members_Component object. @dcavins will investigate this week about that possible change.
  • Finally shortly after our meeting, @boonebgorges reported a new ticket about improving the xprofile_get_field() function so that it only pulls up the data for a field when necessary. The patch he suggested as a first step looks safe to @im4th who thinks it should be included into the 7.0.0 release: it’s always great to improve DB performance. Please have a look at #8378 and send him some feedbacks about your thoughts.

7.0.0 release schedule update

We are going to package a new 7.0.0-beta to include as much fixes as possible considering the previous chapter. Packaging will happen shortly after our next BP Dev-Chat.

  • 7.0.0-beta2: November 4th
  • 7.0.0-RC1: around November 18 (string freeze).
  • 7.0.0: December 1st 🎯

7.0.0 release tasks

The following list of tasks needs to be achieved before we package our next major release (7.0.0).

TasksOwner
BP REST API documentation updates@im4th
BP Survey results@im4th
7.0.0 Release note@vapvarun
7.0.0 Credits update:
– BuddyPress Trac
– BP REST GitHub repository

@dcavins
@im4th
7.0.0 Pizza Restaurant name@dcavins
7.0.0 Announcement post@im4th

NB: we’ll also need to add a patch to #8376 to update our “Hello BuddyPress” modal.

GitHub default branch naming for BuddyPress repositories

This point was moved to a future development meeting. @johnjamesjacoby shared his thoughts about it. Possibilities are main or trunk. FYI WordPress contributors decided to use trunk for repositories of the WordPress organization on August 19.

Open floor

@dcavins asked a question about using the new BuddyPress development environment: when making changes to the BuddyPress source code, he was wondering how is updated the running environment? In other words, do we need to run some specific commands to update it?

@im4th replied changes were automatically taken in account without doing anything more than saving the BuddyPress source code changes. @IAmTheWebb confirmed: “the folder you see outside docker is mapped to inside, so changes you make should appear automagically

Next Dev-Chat

It will happen on November 4 at 19:00 UTC and of course in #BuddyPress. If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

#7-0-0, #dev-chat, #summary