- How do I get a list of contacts whose records were added in the past month - along with the name of the person who added them?
- Is there a way to export total contribution amount for a given year by Household? I want to include all contributions from individuals that are household members.
- I can't export the name of each contact's current Employer. What's the solution?
CiviCRM v2.0 has gotten really good community feedback and testing. We plan on having at least two more beta releases before issuing a final release. Both the forums and the issue queue have been very busy with good bugs (some of which have been there for the past couple of versions!) and great feature ideas, many of which we plan to implement in v2.1. We've already resolved more than 375 bugs in v2.0 which is close to 100 more bugs than the previous highest (282 in 1.8). The forums are averaging more than 75 forums post / weekday. Most of these posts are either related to 2.0 or we test it on 2.0.
We currently have at least 150 sites that have downloaded and installed 2.0 (thanx to our new improved ping back mechanism which gives us stats with regard to version numbers and cms). We'd like to bump this number up significantly over the next couple of weeks. Some reasons why you might want to try the new beta include:
- We are super helpful if your db does not...
CiviCRM 2.0 doesn’t only start introducing significant code oriented architecture changes, we’re also using the occasion of having a nice, round release number to introduce some new things in the process. This version is the first one where we want to announce official string freeze stage in our release process. From now on, every beta3 release of an upcoming version (2.0.beta3, 2.1.beta3, 2.2.beta3, etc.) will be officially the point at which translators can be sure that they won’t be “racing” with developers to provide decent translation of new version in their native language.
CiviCRM is evolving quite rapidly, there is a lot of community feedback and a lot of new functionality getting in from version to version. We admit – for every version, we’re also improving existing texts, as people find different glitches in them. This makes default language version (American English in CiviCRM’s case) more polished, but in the same time makes...Read more
We continued with work in team strategy, helping team members to learn / share the work strategy and approach towards a problem. In last 5-6 days we have resolved 25 issues, created 29 and closed 43 issues which is the indication of better QA towards v2.0.
We also had sessions on Dojo, Test Cases, File editor and OS (ubuntu) Tricks, Shushi Administration and Release Process, other than those held on day1 and day2. “File editor and OS tricks“ was interesting one by Piotr, highlighting how we can speed up coding process by cutting down a few repetitive and boring steps. During release session we did our first 2.0 alpha release....Read more
You can also try it out on our sandbox site here
This release has significant code and schema changes to improve performance and scalability. The upgrade process is now a multi-step web based process. We would like to encourage folks to download and test the release and help improve the final product
You can view Release Highlights hereRead more
v2.0 has significant schema changes, and hence a simple sql script could no longer serve as our primary upgrade mechanism. We are introducing a new upgrade system in 2.0 which will run in a couple of steps and upgrade the user's database. It has been an interesting exercise to come up with the upgrade script. Here are a few things we learned as we went through the process.
To simplify things, we split the upgrade process into multiple small steps. One step for each of the four major schema changes (contact, location, activity and custom), one step for the other minor schema changes and a final step to get rid of all the old columns and tables. With the exception of custom, most of the others were packaged as simple sql scripts that could be executed against the old database.
Upgrading Custom group/field/value required some amount of php code. We had to create new tables for each old custom group with columns based on the fields in each custom group. The custom option...Read more