The beta4 release was missing the DAO files. We've replaced the beta4 release with a new beta5 release.
The Beta 5 release of CiviCRM 2.0 is now available for download on SourceForge. As we noted in our blog, the 2.0 beta series has gotten really good community feedback and testing. However, we'd like to increase the number of downloads and installs for Beta 5. Check this out if you need convincing that downloading this beta is worth your time!. We currently have close to 300 sites that have tested a beta release. We'd like to see this number go past 400 before the final release.
If you've already installed 2.0 beta 1 or 2 or 3 - and have reported issues - please take the time to install beta 5 and verify that your issues have been resolved. There were no database changes from beta 3.
We hope that this will be the last beta before a final release next week. This is also the last opportunity for us to help you upgrade your 1.9 database. If we think your db has triggered a potential bug, we will ask you to mail us the database, fix the bug AND your database and mail it back to you :)
If you have some suggestions or comments on how we can improve CiviCRM usability, please post on our newly created forum topic: What part of CiviCRM are you having difficulty with right now?
Blogues
Restez à l'affut des dernières nouvelles de CiviCRM avec les billets de blogue de développeurs et d'utilisateurs de partout dans le monde.
There is an interesting thread going on in the CiviCRM forum: CiviCRM is scary. This thread started off on the Progressive Exchange mailing list. You can view the archive here ( you need to be sign up to view the archives).
So some folks have complained about the paypal sandbox and the performance on the forums. PayPal has been our primary processor primarily because of its international coverage and decent api's. We set up most of this a couple years back and other than periodic testing, have not really used it too much. However with the 2.0 restructuring, we introduced a few bugs in the process and spent a bit more time on the paypal sandbox than normal.
Almost every week on the forum someone posts a search / reporting question...
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?
... and although CiviCRM's built-in search components are pretty powerful - there's clearly lots of things they just don't do. AND, given how varied the organizations using CiviCRM are - these general search tools probably will never be able to handle everyones' needs.
This article covers - how to install CiviCRM v2.0 on Joomla 1.5 without Legacy support. It also provides some insight into the way components are organized and accessed through Joomla.
The Beta 3 release of CiviCRM 2.0 is now available for download on SourceForge. As Lobo noted in his blog, the 2.0 beta series has gotten really good community feedback and testing. However, we'd like to increase the number of downloads and installs for Beta 3. Check this out if you need convincing that downloading this beta is worth your time!
If you've already installed 2.0 beta 1 or 2 - and have reported issues - please take the time to install beta 3 and verify that your issues have been resolved. There were minor database changes in beta 3 - to fix a few bugs. You'll need to run the SQL statements listed here if you want to keep working with your beta 1 or 2 database (rather than installing a new DB / re-upgrading your 1.9 DB).
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).
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.
Dave Greenberg and myself will be in New Orleans during NTEN. If you are interested in a meeting please let us know via email (lobo at yahoo dot com) and we can figure out a convenient time. We'd love to meet individual/organizations who use/deploy CiviCRM but are not active in the community. We'd like to hear more about what you do and get some feedback on things we do right/wrong and things we should improve upon. Additionally, there are a few CiviCRM related events during NTEN:
After a lot of back and forth, we've finally settled on our first developer training session for 2008. The training is in New Orleans on March 18th and 19th before the NTen Conference. The exact venue is yet to be determined. If anyone is in New Orleans and can host us please let us know.
