Published
Wednesday, March 5, 2008 - 09:45
Written by
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?  

New 2.0 Installations

If you are installing CiviCRM 2.0 Beta from scratch, use the installation instructions linked below:  

Upgrading from 1.9 to 2.0

If you are upgrading an existing 1.9 site (working with a copy of the site, of course), we have provided a browser-based database upgrade script. Instructions for upgrading are here: If you are working with a database that was initially created prior to 1.9 - be sure to follow the steps to Ensure Schema Integrity that are included in these instructions.  

Reporting Issues and Bugs

We look forward to getting your feedback on the release in the coming days. If you have questions installing, upgrading and / or using 2.0 feature - or you're seeing a problem and you're not sure if it's a bug - please post your issue to the 2.0 release testing section of the community forums. Include as many specifics as possible about the issue or question. Bugs should be reported via our issue tracking system. Please select 2.0 in the ‘Affects Version’ dropdown. You will need to register as a user – this ensures that we can follow-up with you on your bug reports if necessary. Please ensure that the bug you’ve found is not reported already by checking the open issues listing.
Filed under