v1.8

CiviCRM 1.8 Release Schedule

Published
2007-06-25 15:37
Written by
UPDATED: July 24th (slipped beta by a few days and final by a week) Here is a tentative release schedule for v1.8. As in any software project, these dates are tentative and subject to delays. However, based on past history they should be pretty close. Check out the 1.8 Release Roadmap for a summary of features and improvements. We'll be looking for lots of volunteers to start pounding on the Alpha Sandbox next week - announcement to follow shortly.

Price Sets in 1.8

Published
2007-06-12 22:24
Written by

In 1.7, event management was added to CiviCRM. The timing on this was good for us (Ideal Solution, LLC), and allowed us to use CiviCRM for a customer who primarily wanted to allow members to sign up for events, such as conferences. The difficulty was that conferences typically have multiple options, each with its own additional price: basic registration, meals, guests, etc. Each additional option increases the total number of possible combinations. Price Sets were added to manage this.

Payment Processors redesign in v1.8

Published
2007-06-10 00:25
Written by

Based on some conversations on IRC with Marshall from Ideal Solutions LLC, I embarked on extending CiviCRM to allow different payment processors for different contribution/member/event pages. Our current restriction of just one payment processor for the entire system did not feel right and we had a few requests to extend this functionality. I took this opportunity to review parts of the code base that I was not familiar with and make a few improvements to CiviCRM in the process. I suspected this would be a fairly quick project. It boggles my mind as to how wrong I was on this count.

CiviCRM 1.8 Update

Published
2007-06-06 10:02
Written by

The entire team has been focused on getting the 1.8 open issues queue down to (almost) zero items by next week - which is our target for code freeze. As of this morning, we're down to 18 open issues - of which several larger items are just about ready for our QA cycle.

CiviCRM 1.8: Merging Contacts

Published
2007-05-31 01:53
Written by

One of the main features of CiviCRM 1.8 is the ability to find duplicate contacts and merge them. The relevant spec of phase one is on our wiki, and in this post I’d like to quickly describe the merge screen. As with most of CiviCRM features, we decided to introduce merging functionality incrementally, so we can get the basic merge screen as soon as possible and then add more features based on the feedback we get.

Site preferences in v1.8

Published
2007-05-28 14:20
Written by

One of the requested features in the recent past has been the ability to hide certain sections of various forms at the site level and the ability to modify this at a user level. I committed code that does this at the site level earlier this week. The issue is described as Site and User Level UI Configuration options (phase 1) in our issue tracker. A related issue is Add a config option to set which fields should appear in the address form.

CiviCRM v1.8 update ...

Published
2007-05-25 02:54
Written by

Here in CiviCRM land we are hard at work making progress with v1.8. We are knocking off a fair number of issues from the issue queue on a weekly basis. You can check the current open issue list here and the v1.8 feature set here. At this point we have posted all the outstanding issues to the issue tracker. We will release a schedule for v1.8 in the next week or so.

Onwards and Upwards...

Published
2007-05-08 10:32
Written by

Those of you who've been using CiviCRM for a while and/or following the progress of the project already know that there's never a dull moment around here. It's only a few days after the release of 1.7 stable - and we're well into work on the NEXT release (1.8).

Planning for 1.8 and Future Platform Requirements

Published
2007-03-29 14:40
Written by
With version 1.7 "almost" out the door, the CiviCRM planning team spent most of this week's team meeting evaluating potential "big ticket" items for 1.8 and discussing future platform requirements for CiviCRM. The platform issues are:
  • When do we drop support for PHP 4.x?
  • When do we drop support for MySQL 4.1
There are compelling technical and management arguments for requiring PHP 5.x and MySQL 5. On the management side, we estimate that it costs the project approximately 4-6 person-weeks of extra time to code, test and debug the PHP 4 version. As the codebase grows - this cost of supporting two very different programming models grows. These are resources that we'd prefer to use improving the overall functionality, usability and quality of the software.

Developer perspective of Google Checkout vs Paypal Pro/Standards

Published
2007-03-22 19:34
Written by
We've integrated support for Google Checkout in CiviCRM v1.7. This was primarily on the initiative and lead of Deepak, part of our awesome India developement team. This also allowed us to compare the ease of use and integration between the two transaction providers. Here are some things we found:
  • PayPal has a much richer and more well thought out SDK. They do quite a few things right from a developers perspective, primarily allowing the code to set various defaults (like the return url)
  • Have the Google Checkout folks tried to use the sandbox with the awful "sandbox" background that they use. Makes it fairly hard to read and navigate the site