Naturkontakt (Nature contact) is the home for members of the Swedish Society for Nature Conservation (SSNC), Sweden’s largest environmental NGO with over 200,000 members. This is a private site where SSNC members can read and publish internal news about the organisation, take part in forum discussions, and join or create groups to help them organise their work. Members of SSNC can create WordPress user accounts using their membership numbers from the organization’s CRM (Customer Relationship Management) software.
Naturkontakt has been around since the 90’s, powered by FirstClass. By 2010, that platform had become outdated and its market share was declining. This led some members to write proposals to find a new platform. Their goal was to select a platform which would serve as a hub for all the different aspects of SSNC’s mission and vision. These include “spreading knowledge, charting environmental threats, proposing solutions, and influencing politicians and authorities, both nationally and internationally. Under democratic forms, we work regionally in 24 county branches and locally in 270 community branches.”
Moving to WordPress
In 2011, SSNC acted on their decision to set up a new web-based platform for internal communications and contacted us at Klandestino to work on this project. After evaluating different platforms, we chose WordPress. Some deciding factors include WordPress’ open source licensing, our experience working with the platform, and the plethora of different plugins that extended WordPress to make it suitable for online communities.
The first iteration of the new Naturkontakt site was launched in 2011, powered by WordPress and WP Symposium. This was quite a while ago but as I recall (plus email logs), the choice stood between BuddyPress and WP Symposium. At that time, WP Symposium already had a forums component while BuddyPress lacked a solid forum integration. Remember that this was the time of the stand-alone bbPress forums which took a tortuous and unstable route to integrate to both WordPress and BuddyPress.
bbPress 2.0 to the Rescue
A year after we launched the new site, we undertook an evaluation which revealed some pain points. To name a few, WP Symposium had limited extensibility, some security issues, and major problems with performance. With those challenges in mind, we researched again into other community solutions for WordPress. By that time, the new bbPress 2.0 plugin was available and it worked very well with BuddyPress.
It was an easy decision to switch from WP Symposium to BuddyPress and bbPress. The major tasks were the arduous migration of data and continuous testing. This new set up has stood the test of time, we’re really pleased with it. The BuddyPress-bbPress combination gave us a running start with forums, groups, profiles, and messages, which are some of the required pieces of functionality needed on Naturkontakt.
Further development of Naturkontakt 2.0 led to the introduction of multisite features to the community. Fortunately, BuddyPress works very well in a multisite environment. Each local organisation (group) of SSNC could have their own subsite to publish news.
To make this work as smoothly as possible, we wrote custom plugins for the following functionalities:
Many-to-many relationships between groups and subsites. For example, the group coordinating work on forest issues could be connected to the subsite publishing news about forest issues.
File archives for groups so that members can upload and version docs, PDFs, images, etc.
Sitewide search, a plugin that indexes all content from the entire multisite network into a “ghost” site to make it possible to have a centralised search throughout the entire network and blog/archive pages that lists posts from all sites.
A drag and drop front page workflow where the editors of the site can search for and list articles from all sites on the network on the main site front page.
This second version of Naturkontakt was released in late 2012. Since then, the basic functionalities have remained more or less the same. The site did get a facelift a few years ago when we focused on making the site work better on phones and tablets.
Going forward with PHP 7
Last year, after a month of capacity/speed problems, a new evaluation showed that some long-delayed upgrades had to be made. We started a new project to focus mainly on stability and speed improvements. We finished the project just right before this article was written.
We implemented the following improvements:
Combed through the codebases. We searched for deprecated functions and places where custom functionality could be replaced with newly added functionality from BuddyPress, WordPress, and bbPress. We decreased the number of active plugins by a third because of the new features that had been rolled into the above-mentioned projects.
Switched over to Elasticsearch/ElasticPress. Our custom sitewide search has served its purpose well. However, since it’s only been used on this platform its development has fallen behind. And compared to new technologies such as Elasticsearch it didn’t cut the mustard. By switching to Elasticsearch we have offloaded a lot of the most expensive queries currently done by WordPress to a server/platform that’s fine-tuned for that kind of work.
Upgraded to PHP 7. This was the last part of the project. We’ve seen major improvements in the response time from the server, on average about 50%-70% decrease in response times! That is, of course, very important on a dynamic site such as for any community where static page caching often isn’t an option.
Our stats show the continued growth of the SSNC community, even though the competition from Facebook can be really hard. One of the major advantages of using WordPress, BuddyPress, and bbPress is that SSNC owns its own data.
Of course, there are always things to improve on. When we completed the recent project to improve performance, despite limited budgets and time constraints, we were all satisfied and hopeful that the site will be around for many more years. We also expect that upcoming development work will be focused more on the user interaction elements of the site, hopefully by building upon and extending the great work that has gone into BP Nouveau. <3
To end on a personal note I’d like to thank all of the wonderful contributors to BuddyPress who have welcomed me into the community and helped me along with trac tickets and patches. Beyond my satisfaction with Naturkontakt and working with SSNC (whom I share a lot of political views with), and the functionality that BuddyPress has provided for the project, the best part of having worked on this site is that I also feel that I’ve become part of a community that tries to do something constructive about the unpleasant grip that Facebook has over our personal and professional lives.
Alexander Berthelsen and his two colleagues are co-owners of the web development co-operative Klandestino AB. Based in the suburbs of Stockholm, Sweden they mainly do WordPress work with a focus on NGO’s and member organisations. Alexander spends most of his five-for-the-future time on making small contributions to BuddyPress.
NefisYemekTarifleri.com is the largest Turkish recipe sharing platform in the world. It has more than 290,000 recipes that reach millions of users every single day. NefisYemekTarifleri is a unique platform that uses WordPress and BuddyPress for all its applications — desktop, mobile web, Android, iOS, and AndroidTV.
290k+ recipes, ~500 new recipes from different authors per day
~2.2M+ registered users with ~2.6M xprofile_data, 24M+ usermeta
NefisYemekTarifleri.com is turning 10 years old this August and has been using BuddyPress for the last 5 years. According to my boss, “BuddyPress has helped a lot to increase our user base.”
Our platform is community-driven, i.e., all the recipes come from our users. The membership and number of recipes submitted have increased dramatically since we started using BuddyPress. The users feel more welcome because they have their “own space” where they can easily add their avatars, cover images, post their recipes, and share other social media links. BuddyPress has enabled users to engage more with other registered members as well as invite new users to the site. Our editorial team spends a majority of their time editing user recipe submissions.
Currently, we are using all BuddyPress core components except Friends and Groups. Thankfully, r-a-y‘s BuddyPress Followers plugin is a great replacement to the built-in Friends component.
Customized BuddyPress Features
Our notification system is quite different from the standard BuddyPress notifications. It supports push and web push notifications and works async over the message queue.
There are a lot of activities which can trigger notifications. There were and are many instances when we send notifications to tens of thousands users every day. For example, when one author with thousands of “followers” publishes a new recipe, it took a long time to send a simple notification like, “Hi there! Jane Doe published a new recipe, take a look!” Consider when we have 10 authors with many followers publishing new recipes at the same time.
In the early days, we created a custom `nyt_bp_add_notification` script which called BuddyPress’ own notification that added a function for bulk messaging. We found out that it was causing lags on our slave MySQL servers because the impact on the disk IO was dramatic. Our solution was a new custom script, `nyt_bp_add_bulk_notification`, which inserts data directly to database (as a bulk SQL query). By the way, we highly recommend Percona’s PMM for catching performance hogs.
At the end of 2016, we migrated from parse.com to our self hosted parse for push notifications. After which, we used web-push-php for the web push notifications.
We decided to replace the built-in cover image feature and create our own Facebook-inspired UI which was more user-friendly. The feedback has been quite positive from our members.
Features of our new cover image UI:
A user can directly upload a cover image by clicking on an icon on top of the cover image area.
The full-size image is saved behind the scenes.
Quick image resizing after the image upload has completed.
A user can change image position via drag-drop.
The full path and image coordinates are recorded as meta.
The Messaging component is active but not fully open for the end users. We will make this available for everyone when we’ve completed our mobile app integration. This is how we are setting this up for our site:
All messages have to be between two people, we canceled group messaging.
When someone you are not following sends a message, that message is marked as “pending”. You also “block” that person.
Fluent messaging: all conversations between two people use the same thread.
Cache: We hated touching BuddyPress directly, but we had to hack core file to fix memory issues. (We have submitted a patch that reduces memory usage for BP#7130)
Messaging, reimagined: We made some necessary changes a bit in a hacky way on the messaging component. Changing messaging behavior was not easy and there are some edge cases we have to monitor and address.
Limit notifications: Only allow 200 notifications per user, WordPress’ cron cleans up on a daily basis.
API Endpoints: We had to be careful on managing API endpoints, addressing the mobile apps a bit differently than web, especially when you do caching inside the device.
Long-running process: MQ workers are long-running PHP scripts and they caused memory problems on production after a while. We fixed this issue with stop_the_insanity.
In the Works
Following are some of the features we have in queue:
Upgrading BuddyPress, of course
Elasticsearch integration over ElasticPress. (We haven’t tried it yet but Pascal already wrote some code we can start playing with.)
User suggestion to follow a member.
Activity improvements (currently, just acting like feed).
PHP 7.1 upgrade with dockerizing all the things. (Still using different versions of PHP)
BuddyPress allows us to build one of the largest niche communities in the world. Fortunately for everyone, BuddyPress is being maintained by developers who are active contributors to WordPress core. Our thanks to all BuddyPress contributors, especially the BP core team.
Ginny Wright started an outdoor boot camp fitness business, Body By Ginny, in Arlington, Virginia in 2003. The business grew and Ginny expanded into nutrition and wellness coaching. As a result, she began offering “Challenges” on printed sheets to her clients a few years later. They could track their daily wellness activities (nutrition, fitness, and mental health) on the sheet, giving themselves points for good behaviors and subtracting points for negative activities. This “game” became popular among her clients, just as online wellness communities started offering similar experiences on websites and apps.
Tara Claeys, a fitness client and friend, offered to help Ginny expand her existing WordPress site by adding a membership component, allow commenting to create interaction between members, and also include the ability for people to track their “Challenge Points” online using a Google Spreadsheet. This was the rudimentary beginning of the online program for her Challenges.
In 2015, Ginny decided to brand her Challenges and decided to launch a separate website for this program, The Total Wellness Challenge (TWC). Her goal was to expand the program beyond her fitness clients and to offer branded Challenges for corporate wellness programs. Tara worked with her to create a multisite installation with BuddyPress and MemberPress that would have:
Subsites for individual, private Challenges in corporate and other groups
Restricted access to Challenges for members only
Allow a “Reflections” commenting page for Challengers to interact with each other
Point Logging for 3 components of the Challenge
Limit submission to same day after 8pm until next day until 5pm.
Allow users to select one day to be a “Free” day where they would receive the maximum nutrition score, no matter what they ate
Add a “bonus” point automatically if a user logs 5 consecutive 12-point days
Show points for all Challengers on a Totals Page
Limits to only one entry per user per day
Each category (nutrition, fitness, lifestyle) has limit on max points per day
Ability for admin to edit user points on the back end
Tara hired Tom Ransom of One Big Idea to help develop a custom plugin that would connect MemberPress with BuddyPress. They chose BuddyPress because is primed for multisite configuration, it worked well with MemberPress, and is very customizable. Plus, the BuddyPress Groups functionality was a good fit for the separate Challenges. For TWC, each Challenge is a unique BuddyPress Group, set up on the front end by the admin.
The TWC is a point-logging game at its core. Participants keep track of their activity throughout each day for about 4 weeks and must log in to the website each day to record their points. There are 3 components of the Challenge:
1. Nutrition: Players can earn up to 12 points per day. Everyone starts the day with 5 points, and can gain points for positive food choices, such as avoiding white flour, eating 3 cups of greens and drinking a specified amount of water based on their weight. Players lose points for unhealthy choices, such as eating too much sugar, eating processed foods, and consuming more than one serving of beer or wine.
2. Fitness: Players can earn up to 2 points per day. They earn one point for doing 30 minutes or more of exercise per day and another point for stretching for at least 10 minutes.
3. Lifestyle: Players earn one point for posting a daily Reflection on the twcfit.com website, and a second point for participating in the lifestyle challenge of the week. Each week, a different lifestyle activity is listed, including behaviors such as noting 3 things you are grateful for each day, getting 7 hours of sleep, or doing an act of kindness for someone. A maximum of 2 lifestyle points can be earned each day.
The participant can go to the Totals page to check their score against other players.
Tom’s plugin includes code that directs the PayPal IPN to the respective subsite for MemberPress (MP) purchases. In addition, this plugin adds the new MP user into the corresponding BuddyPress group once the MP transaction was returned compete. (twc-fit-challenges-member-management.php)
Other components of the custom plugin include:
buddypress.php: sets up BuddyPress (message for logged out users, custom date picker)
Challenges-bp-points.php: Extends BP Group functionality: add_points => adds to database
admin-menu-points — UI for front end
admin-points — Doing work
admin-menus — puts nav in Dashboard
twcfit-challenges.php — timezones – offset GMT, returns city timezone (php only reads city)
In addition, a separate twc-utility plugin hides some BuddyPress content that is not needed and redirects login to BuddyPress.
Tara customized the style sheets and some BuddyPress theme files to add a custom button to the BuddyPress Group page, and edited the BuddyPress navigation and styles. For example:
activity > post-form.php customized “What is your reflection for the xx Challenge today, name?”
groups > single > group-header.php — Adds RESOURCES button to header
The site also uses the BuddyPress Custom Profile Menu and Custom User Profile Photo plugins.
Over the past 13+ years, Ginny has hired 4 instructors, expanded her business to McLean, Virginia, and wrote the “Good Food Recipe Book” which is available for sale on her website. At this time, Ginny is still deciding whether she wants to invest in marketing Total Wellness Challenge or keep it small, mostly based on word of mouth. The increased competition in this space has made it harder to gain exposure without a large marketing budget.
The Total Wellness Challenge website has been running well for a little over a year. Six Challenges have been conducted so far, and participants have loved interacting with each other. Tara and Tom are happy with the positive feedback on their customized “gamification” of BuddyPress and how it has helped provide additional clients and exposure for Ginny’s outdoor boot camps.
Tara Claeys of Design TLC, LLC provides custom website and graphic design services, with a focus on creating effective, clean and personal communication platforms for small businesses. Tara has a marketing background, combined with design and website coding expertise. Tara is the proud recipient of the Arlington Chamber of Commerce 2016 “Best Technology Business Award.”
Links: Twitter, Linkedin
This report presents the results from the 2016 BuddyPress Survey held from November 1 through December 31, 2016. Three hundred and two (302) respondents from 61 countries completed the survey and provided valuable and interesting feedback. Many thanks!
The survey contained 36 questions geared towards Site Builders and WordPress Developers. Adjusting to this more focused target audience compared to previous years’, I selected some questions from our BuddyPress 2013, 2014 and 2015 Surveys, combined/split/modified some of the questions, and added 15 new questions. The survey was designed to maximize responses and get snapshots of:
– basic demographic information
– versions of WordPress, BuddyPress, bbPress, and PHP used
– the types, languages, number of members in BP sites
– comfort levels with BuddyPress, BP theme compatibility, and BP Hooks
– development practices and tools
– respondents willing to share their BP use cases
– BuddyPress participation and contributions
– comments about BuddyPress, BP theme/plugin development, and the survey.
The questionnaire was finalized after incorporating the feedback on the draft from the BP Lead/Core Developers last year. The survey was then promoted via Twitter, BP support forums, bpdevel.wordpress.com, and survey banners added by @johnjamesjacoby at https://buddypress.org and https://codex.buddypress.org which helped a lot.
This section shows some of the highlights from the survey with short comments about each. All supporting graphs, tables, and user comments from this survey are available in the accompanying accessible webpage.
A. What’s New
1. PHP Versions Used
BuddyPress 2.8 requires at least PHP 5.3. It’s encouraging to learn that 99% of respondents’ sites are on PHP version 5.3.x or better. Kudos to the 88% of respondents who are already using PHP 5.6.x or better for their sites.
2. Years Using BuddyPress
Providing additional context for the results of this survey, a whopping 45% of respondents have been using BuddyPress for a year or less. Welcome!
3. Testing BuddyPress
The majority of builders/developers (58%) prefer to test their sites, themes, and plugins against BuddyPress stable releases while 27% do so a month after Stable release and 13% test sites at RC 1. Eleven percent (11%) do not test BuddyPress.
4. Keep Updated with BuddyPress Development
Following the top-ranked preference of reading changelogs to keep updated with BuddyPress development, users ranked these preferences almost evenly: follow BP Twitter account/s (32%), subscribe to bpdevel.wordpress.com (32%), and checking buddypress.trac.wordpress.org regularly (29%).
5. BuddyPress Knowledge
The table above is a compilation of the answers to three questions which sought to gauge the users’ confidence or comfort levels with BuddyPress in general, BP Theme Compatibility, and BP Plugin development.
6. BuddyPress Theme Dev
On the other side of the equation: 27% sometimes customize style sheets while the remaining 22% never customize BP style sheets.
7. BuddyPress Plugin Dev
Around a third of BP users extend the following components every time: Members, Extended Profiles, User Groups, and Activity.
8. Number of Members
Most of the respondents who had up to 500 members are those using BP for 2 years or less, have BP installed in WP domain root, have sites on Shared hosting plans, on PHP 5.6 or better, test against BP Stable release, and on the latest versions of WordPress, BuddyPress, and bbPress.
9. Local Development
Out of the 70% who develop locally, the preferred local development environments after LAMP are: XAMPP (19%), MAMP (18%), WAMP (13%), and VVV (13%), among others.
10. Sharing BuddyPress Use Cases
Expect posts about how site builders or developers are using BuddyPress. Thank you to everyone who signed up!
1. Using BuddyPress
For the fourth year in a row, “I use BuddyPress in My Own Site” ranks number one (62% in this survey), followed by “I build BuddyPress sites for others” at 37%. One participant commented “Also have a family BuddyPress site on a raspberry pi (in dev).”
2. Languages of BuddyPress Sites
For the third year (2013, 2015, 2016), the English language is used in most of the sites (69%). This is followed by Spanish (11%), German (10%), and French (9%), among many others.
3. Types of BuddyPress Sites
For the third year (2013, 2015, 2016), Generic (33%), Academic (29%), Sports (16%), Artistic (15%), and Gaming (12%) are the most common types of BuddyPress sites built. Generic and Academic types are consistently in the top two spots.
4. BuddyPress Versions Used
Eighty six percent (86%) are on BuddyPress 2.7+, followed by BP 2.6+ (23%), BP 2.5+ (6%), BP 2.4+ (4%), and BP 2.3+ (4%). Note: BP 2.7.x was the current release version during the survey period.
5. WordPress Versions Used
Ninety two percent (92%) have WordPress 4.6+ installed, followed by WP 4.5+ (13%), WP 4.4+ (5%), WP 4.3+ (3%), and WP 4.2+ (3%). Note: WordPress 4.6 was the current major release version when the survey was launched.
6. BuddyPress Setups
BuddyPress activated in a single WordPress installation continues to be popular with 72% of the respondents in 2016 as it was in the 2013 survey with 75%.
7. BuddyPress Hosting
For sites hosted on Shared Hosting plans: half have 500 members or less, 40% of the sites are on single WP in domain root, 47% on PHP 5.6 or better, almost half of the respondents have been using BuddyPress for a year or less, and a little more than a third use BuddyPress for their own sites.
8. Other Software Evaluated
For the third year in a row, most of the users (54% for 2016) shared that they did not evaluate any other networking/membership plugin/software before selecting BuddyPress.
9. Contributions to BuddyPress development
Note: 26% of the 58% who indicated that they have not participated nor contributed to BuddyPress development have also checked that they: helped out in the BP forums, reported bugs at BP Trac, submitted patches at BP Trac, among others.
10. bbPress Versions Used
Consistent with the vast majority using the latest versions of WordPress and BuddyPress at the time of this survey, 89% of respondents are using the latest version of bbPress which provides a tight integration with BuddyPress.
11. bbPress Setups in BuddyPress
For the third year in a row, the Sitewide and Group Forums setup is the most popular bbPress configuration at 60%, a big bump from its 49% first place ranking in 2015.
1. Female Participation in Survey
The number of female respondents increased from 8% (17) in 2015 to 13% (37) in this survey. Levels of BuddyPress knowledge range from Beginner through Expert.
2. BuddyPress Sites Per Respondent
In 2015, 41% of respondents (87) built or were responsible for one site followed by 38% (80) with 2 to 5 sites. For 2016, there were more developers who built or were responsible for 2 to 5 sites (99) than for only one site (95).
3. Number of Survey Participants
The number of respondents increased from 211 from 42 countries in the 2015 survey up to 302 respondents from 61 countries for the 2016 survey. We are grateful to everyone who took the time to take the survey.
The lead developers have set the priorities for this year and we look forward to the bp-nouveau template pack and the BP REST API, among many other new features based on some of your comments/requests from this survey.
Finally, all supporting graphs, tables, and comments from this survey are available on the accessible and mobile-friendly BuddyPress 2016 Survey Results webpage. Where possible, data from the 2013, 2014 and 2015 surveys have been added to the charts for comparison. Some data from the older surveys have been recalculated when needed to fit in the format of the question in this survey and noted as such.
Contributor Day is a big part of WordCamp London. This year it was held on Friday 17th March at London Metropolitan University. 100 contributors descended on the venue each aiming to make WordPress better in some wonderful way.
Attendees were asked to choose an area of interest. The options were Accessibility, BuddyPress, Community, Core, Design & Flow, Documentation, Polyglots, Support and Themes. 5 of the 100 contributors chose BuddyPress. 2 of the 5 were new to contributing in general but all had used, or had at least heard of, BuddyPress at some point.
After a quick refill of coffee the team convened and began discussing how to get the most from the next 8 hours. Due to a diverse range of skills available within the group, we were able to focus on documentation, coding and localisation.
As a team we managed to identify an issue related to colour contrast in the Twenty Seventeen theme. #7471 was opened and a patch was submitted. We were also able to translate all remaining strings into Italian.
The day was a huge success and all team members indicated they will contribute again going forward.
BuddyPress 2.8.0 “San Matteo” is now available for download from the WordPress.org plugin repository, or right from your WordPress Dashboard. “San Matteo” focuses on various improvement for developers, site builders and site managers.
For Developers & Site Builders
Modernizing the Codebase
To continue the migration of legacy code to modern standards and techniques necessary for the BP REST API project and other new features moving forward, BuddyPress 2.8 requires at least PHP 5.3. This will allow us to build better, robust, and secure code, benefiting developers and users now and in the future.
More helpful “Activate Pending Accounts” screen
When you click on the username on the “Users > Manage Signups” page, you can now view profile data entered by the user at the time of registration.
Support for List-Unsubscribe header in emails
Allow users to unsubscribe from BuddyPress email notifications in some email clients such as Gmail (web), when properly configured.
Twenty Seventeen Companion Style sheet
BuddyPress looks great in WordPress’s latest default theme with the new Twenty Seventeen companion style sheet.
To change the default two-column page layout to a full-width layout as seen in the image, add the following code to the functions.php file of your Twenty Seventeen child theme.
More hooks for Messages
We’ve added new filters and actions for different methods throughout the Messages component.
A more flexible Group search
The new search_column parameter allows developers to specify which columns should be matched, as well as where wildcard characters should be placed, when searching via BP_Groups_Group::get().
Alphabetical sorting for Groups widget
The groups widget can now be sorted alphabetically, in addition to sorting the results by recently active, popular, and newest groups.
Enable choice of PHPMailer
Developers can specify which PHPMailer should be used when sending BuddyPress with a new filter.
We continue to improve our localization internals, making it easier for translation editors to ensure that BuddyPress will be available for everyone in their own language.
Regular updates to inline code documentation make it easier for developers to understand how BuddyPress works.
Continued improvements for universal access help make BuddyPress back- and front-end screens usable for everyone (and on more devices).
Many, many thanks to all those who contributed during this development cycle. This is a volunteer-run project, and these contributors freely gave of their time and expertise to make BuddyPress better than ever:
BuddyPress 2.8 is called “San Matteo” after a great pizza restaurant in New York City. San Matteo specializes in the “panuozzo”, a pizza-sandwich hybrid native to Salerno, Italy. The proprietor of San Matteo is a friendly fellow who insists on speaking Italian even to customers who don’t understand a word of it. If you find yourself in the neighborhood, be sure to stop by for a great pizza.
BuddyPress 2.8.0 Beta 1 is packed with new features and enhancements and is now available for testing. You can download the BP 2.8.0-beta1 zip or get a copy via our Subversion repository. We’d love to have your feedback and testing help.
BuddyPress 2.8.0 requires PHP 5.3+, and will not be activated on a server with a lower version of PHP. We also remind you that BuddyPress 2.8.0 will require at least WordPress 4.3.
A detailed changelog will be part of our official release notes, but, until then, here’s a list of some of our favorite changes. (Check out this report on Trac for the full list.)
BP Email: Allow end user to specify which PHPMailer should be used #7286