BP Rewrites 1.0.0 Release Candidate

Hi BuddyPress contributors!

“Release Candidate” means that we believe this first version is ready for release! The next step if everything goes well after a last round of testing is to publish the plugin on the WordPress.org Plugins Directory.

Many thanks to the ones of you who contributed to testing 1.0.0-beta2 🥰. Please help us make sure we’re ready to make this important step: Test this release candidate.

If you haven’t tested 1.0.0-beta1 or 1.0.0-beta2, please have a look at this announcement post about it.

What’s new fixed in the first Release Candidate of BP Rewrites 1.0.0?

fixed
Make sure BP Rewrites loads when BuddyPress is network activated. See #32.
fixed
Avoid a fatal error when trying to access to a BP Core Nav too early. See #33.

Props 💚

@adiloztaser@eha1, @imath.

Let’s contribute to BuddyPress’ next way of parsing URLs: test the first release candidate of BP Rewrites 1.0.0.

Please note BP Rewrites requires BuddyPress 10.0.0. Make sure to download the bp-rewrites.zip file from the Plugin’s GitHub repository release page. Use the “Add new” WordPress Administration Plugin screen to upload the zip file. Finally check BuddyPress is activated before activating BP Rewrites.

Happy testing 🙏 😍 🤝

#10-0-0, #feature-as-a-plugin, #rewrites

BP Dev-Chat Agenda & Documentation contributor meeting agenda: March 30, 2022

Hi!

Dev-chat Agenda

Our development meeting will happen on March 30 at 19:30 UTC and of course in #BuddyPress. Here’s our agenda:

  • 10.2.0 feedbacks
  • Open floor

If you have specific/additional points you need to discuss about, please share them into the comments area of this post.

Documentation Contributor meeting agenda

Right after the dev-chat, everyone is very welcome to join this new documentation meeting on March 30 at 20:00 UTC in #BuddyPress. Our agenda is:

  • Table of contents review, see #8658
  • Getting started / troubleshooting sections.

If you’re interested in giving us a hand, please have a look at these explanations 🤩.

🇺🇦 🕊 ☮️

#agenda, #dev-chat, #documentation

BuddyPress 10.2.0 is available

Hi,

Here’s 10.2.0, a maintenance release: please upgrade.

🍕

#10-2-0, #maintenance, #release

BP Dev-Chat Agenda & Documentation contributor meeting agenda: March 16, 2022

Hi!

Dev-chat Agenda

Our development meeting will happen on March 16 (today) at 19:30 UTC and of course in #BuddyPress. Here’s our agenda:

  • 10.2.0 updates & schedule
  • Open floor

If you have specific/additional points you need to discuss about, please share them into the comments area of this post.

Documentation Contributor meeting agenda

Right after the dev-chat, everyone is very welcome to join this new documentation meeting on March 16 (today) at 20:00 UTC in #BuddyPress. Our agenda is:

  • Table of contents review, see #8658
  • Getting started / troubleshooting sections.

If you’re interested in giving us a hand, please have a look at these explanations 🤩.

🇺🇦 🕊 ☮️

#agenda, #dev-chat, #documentation

BP Dev-Chat Summary : March 2, 2022.

10.1.0 feedbacks

Apart from a mysterious bug about the avatar crop step (we were not able to reproduce it so far), and a question about how to bring back legacy widgets, @vapvarun confirmed there was no alerts posted in our support forum.

@dcavins is using the 10.0.0 new features on several new sites and so far he hasn’t found any other issues.

10.2.0 Schedule

Unfortunately the notifications user cache issue was partly fixed in this release, see #8642. @im4th is in favor of packaging a new maintenance release soon to include the fix committed lately as well as other 10.0.0 regression issues that could have been fixed in the meantime. @vapvarun & @dcavins agreed about this plan 👉 expect 10.2.0 to be released asap!

Open floor

@im4th has been tested BuddyPress using PHP 8.1. He has found a lot of notices and improving our support to this PHP version will need some heavy changes about our PHPUnit testcases, see #8649.

Next Dev-Chat

It will happen on March 16 at 19:30 UTC in #BuddyPress.

#10-0-0, #10-1-0, #dev-chat, #summary

BP Rewrites 1.0.0-beta2

Hi BuddyPress contributors!

Many thanks to the ones of you who contributed to testing 1.0.0-beta1 🥰, I can’t stress enough how this is really important for the BuddyPress project in order to migrate to the WordPress Rewrite API and let administrators have a full control over any BuddyPress URLs. If you haven’t tested 1.0.0-beta1, please have a look at this announcement post about it.

Thanks a lot to Sarah Gooding who wrote this great post about BP Rewrites’ first beta on WP Tavern. We’re very thankful you spread the news to the WordPress world.

What’s new fixed in 1.0.0-beta2

fixed
Anticipate WordPress 6.0 changes about the WP Request to make sure BP Ajax requests are using the Rewrite API. See #31.
fixed
Make sure BuddyPress is active before trying to change anything into the site’s set up. See #29.
fixed
Remove the BP Pages settings tab to prevent any rewrite rule errors. See #27.
fixed
Fix bpRewritesUI() function call when readyState is not fired. See #26.
fixed
Remove superfluous parameters on remove_filter() calls. See #25.

Props 💚

@adiloztaser@imath.

Let’s contribute to BuddyPress’ next way of parsing URLs: test BP Rewrites 1.0.0-beta2

Please note BP Rewrites requires BuddyPress 10.0.0. Make sure to download the bp-rewrites.zip file from the Plugin’s GitHub repository release page. Use the “Add new” WordPress Administration Plugin screen to upload the zip file. Finally check BuddyPress is activated before activating BP Rewrites.

Happy testing 🙏 😍 🤝

#10-0-0, #feature-as-a-plugin, #rewrites

Using PR to share your patches on BuddyPress Trac

Thanks to Dion Hulse (@dd32), it’s now easier to share patch directly from your BuddyPress GitHub fork to a specific BuddyPress Trac ticket 🙌. It’s a great improvement and I believe it can potentially attract more people to contribute to BuddyPress code.

How does it work?

First if you haven’t created your BuddyPress fork on GitHub, log in to your GitHub account, head over to the https://github.com/buddypress/buddypress.git repository and click on the “Fork” button !

You’ll get a new repository on your GitHub account to work from to contribute to BuddyPress, here’s mine for instance: https://github.com/imath/buddypress.git

Clone it locally, create a new branch to add your changes, commit and push your changes on your branch, go to your fork’s page on GitHub and click on the link to create a Pull Request. You’ll be directed to the page where you’ll be able to link your PR to an existing BuddyPress Trac ticket.

Find the <!-- insert a link to the BuddyPress Trac ticket here --> text and replace it with the Trac Ticket link, for example https://buddypress.trac.wordpress.org/ticket/8647. Of course, if the ticket doesn’t exist yet, you can always create a new one from there.

NB: BuddyPress core committers, do not merge PRs from the BuddyPress GitHub repository, the feature’s goal is to ease code review, we still need to commit changes from our SVN repository.

Click on the “Create pull request” green button and go to your BuddyPress Trac ticket’s page.

As shown in the above screenshot, your pull request will be included into the “Pull Requests” section of the corresponding Trac Ticket. From there BuddyPress contributors can enjoy the GitHub code review features clicking on the View PR’s link or get the patch using the “View patch” link.

To get more information about this feature which is also available on the WordPress Trac, you can read this documentation page of the WordPress Contributor’s handbook.

Getting the most out of this feature

As you may have noticed, we also have some information about automatic checks applied to pull requests. We currently haven’t set these from a GitHub action, but it would be interesting to include PHP Unit tests and why not WordPress code standards checks, see #7228.

#github, #trac

BP Dev-Chat Agenda March 2, 2022 & Documentation contributor hour kick off

Hi!

Dev-chat Agenda

Our development meeting will happen on March 02 (today) at 19:30 UTC and of course in #BuddyPress. Here’s our agenda:

  • 10.1.0 feedbacks
  • 10.2.0 schedule

If you have specific/additional points you need to discuss about, please share them into the comments area of this post.

Documentation Contributor hour agenda

We’re starting our documentation big refresh on March 02 (today) at 20:00 UTC in #BuddyPress. Here’s a suggestion about the first topics we can talk about:

  • User / Developer documentation
  • First ideas about user documentation organization
  • Tools and contributions management

If you’re interested in giving us a hand, please have a look at these explanations 🤩.

🇺🇦 🕊 ☮️

#agenda, #contributor, #dev-chat, #documentation

BuddyPress 10.1.0 is available!

Hi,

10.1.0 is a maintenance release, please upgrade 🙏

😘

#10-1-0, #maintenance, #release

BP Dev-Chat Summary : February 16, 2022.

10.1.0 maintenance release

@im4th started the meeting asking if the team has seen something specific relative to the 10.0.0 upgrade. An issue about avatar upload was found there. So far none of us were able to reproduce the issue. @im4th wondered if it could be some users disabling the Backbone base UI in favor of the legacy one. He has tested since this situation and there is a bug preventing the avatar to be successfully uploaded in 10.0.0. It has been fixed by @oztaser into trunk and the 10.0 branch, see #8619.

@vapvarun shared about the issue rtMedia had with the Groups component, it has been fixed by the plugin authors since in plugin version 4.6.10. He also shared an issue about the Privacy page not being included into the registration form when it should. This issue is still under investigation.

Team agreed we need to package a maintenance release. We were planning to do it at the end of last week, but some other issues were reported on Trac so we prefered to delay a bit to include fix for these new issues. As soon as the last one will be fixed (See #8637), we’ll package 10.1.0 (probably later today or tomorrow).

BP Rewrites’ first beta

@im4th published an announcement post on this blog a few days ago. It’s important to prepare the plugin to be hosted on WordPress.org so that testing is made more widely. @oztaser already started to test the plugin and found some issues, fixed most of them. The one issue that is not fixed yet is the one that happens when you activate BP Rewrites before BuddyPress.

@dcavins shared his doubt about his plugins: “My doubt there is I know I’ve written plugins that run on bp_init . It will be interesting to see if they all blow up.”

That’s precisely the goal of the Backcompat mechanism the plugin is including which needs the most testing. @im4th said “The goal is to try to  have a first version with the less bugs as possible to publish it on WordPress.org plugin directory and see how it goes when used more widely. Then wait a few BuddyPress releases like 2 or 3 to be sure it’s ok to merge it into Core”.

4 to 6 months to improve the BuddyPress’ documentation site

No major releases, all energy on docs!

@im4th

We’re all in favor of spending the energy we put in building a major release into improving the documentation site. And we’ll try to do it by organizing each other wednesdays (when we usually meet to talk about BuddyPress development) a “contributing to docs hour”. From 19:30 UTC to 20:00 UTC, we’ll discussed about potential maintenance releases and from 20:00 UTC to 21:00 UTC everyone is welcome to contribute to BuddyPress documentation.

@vapvarun said we need a direct link fromt this site to the official BuddyPress site, it has been added into the “Official site resources” sidebar widget ✅. He can also contribute with walkthrough videos.

We’re all very eager to start this new type of meetings and we really hope you’ll be a lot to join us.

Next Dev-Chat

It will happen on March 02 at 19:30 UTC in #BuddyPress.

First Contributing-to-docs-hour

It will happen on March 02 at 20:00 UTC in #BuddyPress

#10-0-0, #dev-chat, #summary