Blogs tagged "v2.1"

The Google Chart API is so simple yet so powerful that can give you some amazing features:

• Create charts simply by using URL with some parameters

• Inserting the chart is as simple as you would be inserting an image

• The chart is created on the fly dynamically

• No need of server side coding

• No need of JavaScript to code or view your chart

• Any resolution of the chart with only a change in URL parameters

• Manipulating the parameters of the URL would change the chart

• A variety of styles to choose as per your tastes.

Lets take a simple case study for our chart. Suppose you are showing Contribution to orgnization using monthly and yearly basis and instead of showing the data in tabular format you could show the data with some visual cues. Charts are the perfect way...

Read more

We've had the ability to add one/more CiviCRM Profiles to the drupal registration page since the first release (thanx to the flexibility of Drupal hooks). This was not possible in Joomla 1.0.x and we hoped the 1.5.x series might help solve this issue and be more open. While Joomla 1.5 is a major step forward in multiple aspects, it did not address this issue. So to some extent we were stuck. I was hoping for someone in the community to step up and do the needful. But that did not seem to be happening either :(

After yet another forum post on this topic, i decided to take a look at the code and figure out what needs to be done. We had abstracted most of the pieces from drupal already, so we just need to make a few function calls at the right places. I started looking for an example component that does something similar, that I could base my work on. Had heard good things about...

Read more

So while doing the custom data hook, CRM-1594, I also implemented a hook for setting the default values of a 'Form' in CiviCRM, CRM-3176. So now we have a defaults and validate hook for the form object. The two missing hooks are for buildQuickForm and postProcess, which I'm planning to implement in the next couple of days. This coupled with template customization will allow developers to inject form elements and save them to the database (similar to drupal hook_form_alter). I'm also planning to implement the ACL improvements as an ACL related hook (along with a sample implementation). These new features should give CiviCRM developers more power and flexibility... Read more

As part of the 2.1 release cycle, we are working hard to simplify and streamline the codebase wherever possible. The intent is to increase performance, reduce the number of bugs and make the code easier to understand and maintain. As part of this effort, we are considering the elimination of two "features" which create (potentially) unnecessary complexity in the code, AND which we believe to be infrequently used...

Store Data for Multiple "Domains" in a Single Database

The current data model allows you to create and maintain separate "data silos" ("domains") in a single CiviCRM database. This concept was derived from Drupal's multi-site table-prefixing model - although it uses foreign keys instead to link each domain's dataset. Over the past few releases, we have seen quite a few use cases where larger hierarchical organizations want to control access to subsets of their data - based on a user's departmental or regional affiliation and/or role. However - the current... Read more