Blog posts by kurund

The team has released version 2.2.3 with approximately 84 bug fixes and improvements. Notable fixes and improvements include:

Lately there has been lot of confusion using Name, Title/Label and Value. There is also a lot of inconsistency in code and database, hence we are planning to fix it in CiviCRM v2.x release.

Lets take an example of Participant Status, 'Registered'. In this case Name will be 'Registered', value will be an integer from 1..N (this depends on each install) and Label/title can be "Registered" or "I will come" etc. (or a localized version of the word/phrase).

Basic rules are:

It was an eventful period after beta 4. With excellent support from the community, we were able to identify and close quite a few trivial issues (and a few critical ones). The fifth 2.1 Beta distribution (probably last one before stable) is now available for download on SourceForge.

For all those eagerly waiting to being translation work on 2.1, we are now in "string freeze" - and the translation site has been updated with 2.1 files: http://translations.civicrm.org

If you are planning on using new 2.1 features AND / OR upgrading an existing site to 2.1 - NOW is the time to test the upgrade with YOUR DATA and identify any remaining issues with new or existing features. The development team will actively work with you resolve any upgrade issues during this phase of the release cycle. If you are unable to test the release by downloading it - then the next best thing is to try out the new features, bug fixes, as well as the workflows you use most often by logging in to the public demo.

It was 6th August 2008, CiviCRM team was getting ready for first alpha release of version 2.1. You could feel the tension and sense the responsibility on everyone's face. Although it was an alpha release, each one wanted to close their outstanding issues / bugs. We were trying to get Open Issues count below 10 and wanted to close as much QA issues as possible.

I am a big fan of the Lord of the Rings trilogy, hence i was very excited about coming to New Zealand and exploring few Middle Earth locations. I must say NZ has some of the most amazing places I have ever seen.

Continuing the database cleanup that we started with v2.0, we are planning to drop some of the unused fields from civicrm_address table.

CiviCRM v2.0 ERD

List of fields that will be dropped.

1. street_number 2. street_number_suffix 3. street_number_predirectional 4. street_name 5. street_type 6. street_number_postdirectional 7. street_unit 8. supplemental_address_3

And it all began like normal Barcamp (like any other non-conference). As we all know, most of the developers are nocturnal, yet again CodeCampMumbai was no exception and started off schedule.

I am here with one of my colleagues(Deepak) to work on Facebook plugin for CiviCRM. Some initial specs on this feature: Facebook Integration

Other interesting projects include lighting up bulb using web interface(PHP), Mapping and Adding Events on Google Map.

I traveled all the way to Delhi to attend OSSCampDelhi, Non-Conference (Bar Camp), my first Open Source Camp in India. It started well with a good presentation on "HIGH Performance Websites". Speaker shared few tricks how to make you front-end load faster.

* Use of expire headers for javascript, css * Use of compressor to remove spaces in javascript using tools like (Dojo Shrink safe, YUI Compressor, JSMin, Dean Edwards Packer) * use of mod_gzip / mod deflate for apache * not to use @import use "link" tags * load script at last ( although I don't agree )

In addition to many new features in CiviCRM v1.8, we have worked on few improvements for CiviCRM Profile.

1. We have added functionality which allows people to create User Account in Drupal using CiviCRM profile. So this way, user can create customized User Registration pages without using default Drupal User Registration form.

For more details: CRM-1633

2. Another interesting feature for profile is Option to Generate Email Notifications when a profile is created or edited.