The team is excited to announce the fourth stable release of the incredible CiviCRM 4.5 series. This release includes some important fixes, and is recommended for everyone using CiviCRM 4.5.
» Issues fixed in 4.5.3
We are also releasing 4.4.9 today which is the first full 4.4 LTS release and has a number of fixes as well as the security fixes.
As you may have heard, CiviCRM is about to launch an exciting new help site on Stack Exchange, which will make getting support with CiviCRM easier and more effective.
The new site is about to launch, but the initial "beta" phase will only be available to a limited group of people. This pilot group will have unprecidented access to world's top CiviCRM experts, and it's not too late for you to join them.
In recent blog posts, we've expanded the long-term support effort to 4.4, discussed the release window (first and third Wednesday of each month), and experimented with release-candidates (
On Thursday, October 30th Web Access, Lighthouse Consulting and Design, and The Association Development Group (ADG) hosted the first ever Albany area CiviCRM meetup. Since this was the first of its kind in the area we were unsure of what to expect. We could not have been more pleased at how the event unfolded.
Those of you who have been following our blog, or our linked in discussion group, or are on our partner list will know that quite a few people have been working on a new question and answer site for CiviCRM, based at Stack Exchange. CiviCRM is already a super helpful community. Stack Exchange provides a really powerful tool that 'curates' the question and answer process much more effectively that traditional forums.
CiviCon London happened almost a month ago now so I thought it was about time for a quick review. 2014 was our biggest year yet. As in the previous years, we had a roughly 50:50 split between people new to CiviCRM and CiviCon and people coming back from previous years. We also had a fairly even split between developers, implementors and users.
This extension has been unpublished from the CiviCRM extensions directory, as it is obsolete. The source code is still at GitHub (https://github.com/sgladstone/com.pogstone.paymentprocessorhelper), but is not maintained, nor recommended.
"Sort Name" is used by CiviCRM for tabular search results.
Every software project is faced with the challenge of balancing the need to innovate and introduce new features, with the interest of many users in minimizing their maintenance costs and avoiding the risks that inevitably come with software upgrades. One way to meet this challenge is to provide a Long-term Support (LTS) release with an extended release cycle.
