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.
Blogs
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.
There has been a security release for CiviCRM. Upgrades are available for:
At Third Sector Design, we’re excited to have contributed to adding Group support to FormBuilder, a key feature included in the 5.77 release. We extend our thanks to the Core Team and Coleman for their review and support in getting this important feature across the finish line.
CiviCRM version 5.78.0 is now ready to download. This is a regular monthly release. Upgrade now for the most stable CiviCRM experience:
Duplicate contacts in your CRM are a source of trouble.
CiviCRM 5.79, which will be released around November 7 2024, will include a slightly different experience for administrators who wish to install extensions. On the surface, it is a rather small change which will make CiviCRM easier to use though it may have a bigger impact for CiviCRM hosting providers and for extension developers.