Thanx to Elin Waring, we had two of Joomla core developers, Rob and Louis, attend the CiviCRM training in New Orleans. We had a pretty diverse CiviCRM crowd attend the training and hence could not work as much as we'd like on improving the CiviCRM Joomla integration. However, I did spend some time with Rob and got a few ideas on how to improve and optimize our Joomla integration. Here are a few things we plan on doing in v2.1 to better support Joomla v1.5
Blogues
For April 20th and 21st. The session is already sold out. However if there is more interest, we can schedule another training (in Sydney?) and/or get another developer to help with this training. Please contact us immediately if interested.
A minor typo in a php file managed to squeeze its way into the release (CRM/ACL/BAO/ACL.php, line 799 or so there is an extra 'x')
So we've released CiviCRM v2.0.1. We took the opportunity to fix a few other minor issues. We expect to do bug fix releases every other week for the next few months.
A few folks from the core CiviCRM team (dave greenberg, kurund jalmi, michal mach, yashodha chaku and lobo) are having a CiviCRM team meeting in Nelson, NZ. Our current dates are for the meetup to happen between Apr 23rd to May 4th. We could potentially do a developer and/or end user training on the weekends apr 26/27 or may 3/4. Locations could be auckland/wellington/christchurch or if a lot of interest in AU, sydney/melbourne is a possibility.
Earlier today at approx 6:00 am NZT (yes, we are early birds), we released CiviCRM v2.0-beta4. At approx 9:00 am, I saw a post from aaron about some missing files in the release. I downloaded and verified what aaron said and realized we had messed up big time :(. Our release czar piotr was offline and not reachable.
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.