Blogues

Gee, it seems like everyone is rebranding these days. Companies big and small are getting new names, new looks, new logos and new mascots. We at CiviCRM have thought long and hard about this phenomenon, in fact, for the past few months we've put all of our nonessential tasks on hold (unimportant things like software development, security, stability, release management and the like) to focus exclusively on these very important questions:

This month we looked at fundraising at CiviCRM North East. Izi Clery from Population Matters spoke about how they use CiviCRM to support their fundraising efforts.

Her talk covered the following topics:

CiviCRM version 5.59.0 is now out and ready to download. This is a regular monthly release. Upgrade now for the most stable CiviCRM experience:

Join CiviCRM Core Team member Coleman Watts for a demonstration of SearchKit and FormBuilder, including recent updates and review of work in progress. This webinar will be interactive, so it's an opportunity for participants to bring ideas, questions or suggestions about these two pieces of functionality that are increasingly used through CiviCRM.

There has been a security release for CiviCRM. Upgrades are available for:

I am taking part in a small sprint on CiviCRM standalone today. Alain Benbassat and Klaas Eikelboom are going to be part of the CiviCRM stand on FOSDEM 2023 and thought they could also do a 1 day mini-sprint on Standalone. And Rich Lott, Michael McAndrew, Nic Weistrich and me rallied to the same cause.

CiviCRM version 5.58.0 is now out and ready to download. This is a regular monthly release. Upgrade now for the most stable CiviCRM experience:

When I first started writing CiviCRM extensions it quickly became clear that there were a lot of old parts to CiviCRM's core code which deserved some love. I know that CiviCRM only has a small development team, and so I started searching for quick-win code changes that I could contribute back to the CiviCRM codebase in order to improve the quality and developer experience for everyone. I want to share the PHPStan configuration that I have been using to identify poor-quality (and in some cases buggy) code within the CiviCRM core codebase.

Newsletters and other mailings are an important way to keep in touch with your supporters and mailing statistics like click and open rates can help you learn what your supporters respond best to. CiviCRM provides these features, similarly to many/all other email marketing solutions. But what do those numbers actually mean?

Is it "Oh-Oth"? "Owth"? "Worcestershire"?