CeSGO Dashboard 2.1.0

BuddyPress 5.1.2 is now available. This is a security release. All BuddyPress installations are strongly encouraged to upgrade as soon as possible.

The 5.1.2 release addresses one security issue:

• Certain REST API requests could result in the exposure of private data. Discovered and reported independently by Petter Walbø Johnsgård and Jacek Suski.

The vulnerability was reported privately to the BuddyPress team, in accordance with WordPress’s security policies. Our thanks to the reporters for practicing coordinated disclosure.

For complete details, visit the 5.1.2 changelog.

Update to BuddyPress 5.1.2 today in your WordPress Dashboard, or by downloading from the WordPress.org plugin repository.

BuddyPress 5.1.1 is now available. This is a security release. All BuddyPress installations are strongly encouraged to upgrade as soon as possible.

The 5.1.1 release addresses one security issue:

• A denied of service was fixed that could allow a logged in user to remove another user’s avatar and also any empty folder. Discovered by nomnom.

Thi vulnerability was reported privately to the BuddyPress team, in accordance with WordPress’s security policies. Our thanks to the reporter for practicing coordinated disclosure.

For complete details, visit the 5.1.1 changelog.

Update to BuddyPress 5.1.1 today in your WordPress Dashboard, or by downloading from the WordPress.org plugin repository.

Immediately available is BuddyPress 5.1.0. This maintenance release fixes 8 bugs related to the 5.0.0 release, and is a recommended upgrade for all BuddyPress installations.

For details on the changes, please read the 5.1.0 release notes.

Update to BuddyPress 5.1.0 today in your WordPress Dashboard, or by downloading from the WordPress.org plugin repository.

Many thanks to 5.1.0 contributors

szepe.viktor, JarretC, Renato Alves (espellcaste), David Cavins (dcavins), Boone Gorges (boonebgorges), John James Jacoby (johnjamesjacoby) & Mathieu Viet (imath).

Yesterday morning we’ve deployed the first stable version of the BP Beta Tester plugin on the WordPress.org plugins directory.​​

This plugin’s goal is to make it easier to beta test our pre-releases. You just need to install and activate the plugin to be ready to try our beta and release candidate versions once we’ve announced them on this blog.​​
​
Beta testing BuddyPress is very important to make sure it behaves the right way for you and for the community. Although we, the BuddyPress Development Team, are regularly testing it, it’s very challenging to test every possible configuration of WordPress and BuddyPress. That’s why we absolutely need your help during these pre-release stages.​​

Making this plugin available was one of the means we thought about during our post 5.0.0 release development meeting to have more BuddyPress contributors.​​
​
Beta testing is actually a good way to start contributing, to anticipate and fix potential issues before you have the bad surprise to meet them once you’re upgrading to a new stable version of the plugin.​​

NB: to beta test BuddyPress, we strongly advise you to have a local copy of your live site or a staging site : it’s always safer than doing it on a production site.​​

During our next pre-release stages, when you will find something is going wrong during your beta tests, please think of warning us about it submitting a ticket on our Development Tracker or posting a new topic in our support forums.​​

Thanks in advance for your time and help <3

Hi everyone!

First, we’d like to thank all the people who contributed to the poll we shared on our development updates blog and into a topic of one of our forums a month ago. It was really important for us to have your expectations about the content the plugin should provide to the WordPress Block Editor.

It’s now time for us to share with you the results of this poll and tell you how we plan to work on BuddyPress blocks for the next release(s) of your favorite community engine!

The results of the Blocks Poll

It received a total of 161 votes divided as follows:

• A block to share a post or a page via the Activity Stream : 17 votes.
• A block to list the recently published posts from across your network (Exists as a widget) : 13 votes.
• A block to display Sitewide Notices posted by the site administrator (Exists as a widget) : 12 votes.
• A block to dynamicaly list the recently active, popular, newest, or alphabetical groups (Exists as a widget) : 11 votes.
• A block to display Profile photos of online users (Exists as a widget) : 10 votes.
• A block to highlight a single Group : 10 votes.
• A block to highlight a single Member : 10 votes.
• A block to dynamicaly list the recently active, popular, and newest Friends of a given member (Exists as a widget) : 9 votes.
• A block to display the Profile photos of recently active members (Exists as a widget) : 9 votes.
• A block to restrict content to a Group type : 9 votes.
• A block to dynamicaly list the recently active, popular, and newest members (Exists as a widget) : 8 votes.
• A block to restrict content to a Member type : 8 votes.
• A block to restrict content to Group members : 7 votes.
• A block to list the Member types : 7 votes.
• A block to display a selected Activity as a quote : 6 votes.
• A block to list the Group types : 5 votes.
• A placeholder block for directory pages to eventually make them benefit from wide alignments : 5 votes.
• No blocks! : 3 votes.
• Other : 2 votes.

As you can see, top results are mostly corresponding to existing widgets except for:

• A block to share a post or a page via the Activity Stream.
• A block to highlight a single Group or a single Member.

We also analyze from these results that there is no blocks expected to be a must have and it’s interesting to see that the 2 first blocks are about highlighting WordPress content. Finally only one suggestion was made : A “Block for Activity Stream component” (PS: in Nouveau there’s an existing widget for it).

About the BuddyPress development team’s decision regarding BuddyPress blocks.

We think working on blocks to highlight a single Group or a single Member is a good starting point. Moreover it’s something we don’t make possible yet. We also think converting existing widgets to blocks is an obvious move to do.

We’ve decided to work on these blocks from a specific GitHub repository and to merge into the Core of the BuddyPress plugin the “JavaScript built” blocks as soon as they are ready. To the very least, we’ll have the 2 blocks to highlight a Group or a Member of your community site merged into BuddyPress for its next major release (6.0.0).

We’ve just pushed the minimal code to start working on BuddyPress blocks into the BP Blocks’ GitHub repository. We’ll soon add contributing notes into this repository so that you can help us building beautiful BuddyPress blocks. You can already share with us your “Pull Requests” forking the repository.

If you can’t wait for the contributing notes to start working on BuddyPress Blocks, here’s a quick “how-to” :

• Once you cloned your fork into your development environment, do npm install
• The JavaScript (ESNext) code for your block needs to land into the /src/bp-{ID of the BP Component}/js/blocks/ directory.
• Have a look at the way the bp/member block is registered here to build your registration code.
• run npm start to see how your JavaScript code behaves at each edit.

Let’s build awesome BuddyPress blocks, together <3.