Recently on CiviCRM irc and forum few people asked about adding client side validation for phone field. By default CiviCRM packages validate plugin, so this can be easily implemented with minor customization. Below is the example of validating US phone number on new contact form.
Code sprint is always fun. It's gives you great opportunity to meet fellow civi folks, collaborate and implement kool stuff :). Last few days has been very interesting. Besides some great meals we also managed to get some work done. ( If you still don't know, food is the most important part of CiviCRM Sprints )
First we shortlisted features / improvements that we want to accomplish during this sprint. Complete list is available at: http://wiki.civicrm.org/confluence/display/CRM/UI+specific+tasks We started the sprint by converting getContactList(), function that is used in quicksearch into api v3. This will allow developers to build quicksearch like interface ( autocomplete ) on any civicrm forms using jquery or smarty. For eg: "Current Employer" field in profile can be converted into quicksearch autocomplete field using this api.CiviCRM 3.4.2 and 4.0.2 releases includes 100+ bug fixes since the 3.4.1 / 4.0.1 release. Both versions are now available for download. You can also try them out on the public demos: Drupal 6 / Drupal 7 and Joomla 1.5 / Joomla 1.6 sites. We strongly recommend reviewing the 3.4/4.0 highlights post, where you will find out what’s new and hot in this release. The newest CiviCRM versions are:
4.0.2 for Drupal 7 and Joomla 1.6 3.4.2 for Drupal 6 and Joomla 1.5CiviCRM 3.4.1 and 4.0.1 release includes 70+ bug fixes since the initial 3.4 / 4.0 release. Both versions are now available for download. You can also try it out on the public demos: Drupal 6 / Drupal 7 and Joomla 1.5 / Joomla 1.6 sites. We strongly recommend reviewing the 3.4/4.0 highlights post, where you will find out what’s new and hot in this release. The newest CiviCRM versions are:
4.0.1 for Drupal 7 and Joomla 1.6 3.4.1 for Drupal 6 and Joomla 1.5It was a great gathering of people from different backgrounds showing up for the meetup. By far this was one of the biggest meetups (30+ people) that I have attended. Nice to see the growth in the SF Bay Area civi community!
As announced earlier, the Location API has become obsolete in API version 3, which is currently shipped with the 4.0/3.4 alpha versions. It has been replaced by Address, Email, Phone and Website API in v3.
However, in the v2 Location API there was already a param 'version' which was used to determine if the older functionality of the Location API (CiviCRM version 2.2 and older) was used or the newer functionality (CiviCRM 3 and onwards). So the code looked like this:
CiviCRM comes with CKEditor as a default wysiwyg editor. One of the missing features has been ability to upload /browse existing files on the server using CKEditor. So after some investigation I figured out you can easily integrate IMCE drupal module for this purpose.
Here are the steps:
As a part of 3.3 release we will be deprecating all v1 api's and if you are still use them, it's a good time to migrate to v2 api's before upgrading to CiviCRM v3.3 release.
CiviCRM api v2 were introduced in v2.0. For every v1 api there is equivalent v2 api.
Reason for removing v1 api's:
