The CiviCRM community is going back to where it all started to celebrate 20 years of serving nonprofits.
Start planning now to attend the event in the San Francisco area.
There will be three parallel tracks of sessions over two days, packed with case studies and the latest in SearchKit, FormBuilder and new extensions.
Planning for this gala event is already underway:
Mass email campaigns are a staple of digital marketing, providing a powerful way to reach a large audience quickly. However, ensuring that your email content resonates with your audience can be challenging. One of the most effective ways to optimise email performance is through A/B testing, a feature that has been core functionality for a long time and is now fully implemented using Mosaico.
CiviCRM version 5.79.0 is now ready to download. This is a regular monthly release. Upgrade now for the most stable CiviCRM experience:
The project #CiviOneClick aims to simplify access to CiviCRM – starting with an easy setup of demo sites but with the long-term goal of a new way to install CiviCRM.
CiviCRM Standalone has reached a significant milestone. We are now ready to make the November 5.80 release candidate “the RC” for a first official, stable release of the new Standalone in December.
It’s an exciting prospect, representing lots of work from across the community over the past couple of years. For me personally, getting to this stage has been a key focus of my work on CiviCRM this year.
Most developers in the CiviCRM community are probably familiar with Composer. If not, Composer is a dependency manager for PHP. That's just a fancy way of saying that composer allows codebases like CiviCRM to pull in code (dependencies) from other projects.
We recently experienced a massive slow down in one of our background jobs and tracked down the cause via redis tools to a cache clearing issue. I decided to write up how we tracked it down to share with other developers - but this blog post comes with a geekery warning : the target audience is definitely solidly in the developer space and assumes the reader has a lot of background knowledge.
Card-tumbling, like its evil relatives of automated spam, script kiddies and privacy breaches, is not a problem to be solved, but is a fact of life on the internet.
Recently, new strategies for bad actors means that even if you thought you'd fixed this, you might need to review your defenses.
If you've got a publicly accessible contribution page using an on-site payment processor, there's a good chance that you're a target.
Around July last year, I wrote a blog post about a few user interface changes that might go unnoticed to most (covering versions around 5.55 to 5.65). Here are a few more changes that have been introduced in versions 5.75 to 5.80.
