05 April, 2011

As part of the Google Grants program for non-profits, Google offers their Google Checkout service to qualifying non-profits at no-charge with no processing fees. Depending on the fees you would pay with a competing processor this represents an instant 3% jump in your organization's fundraising efforts just by using Google Checkout.

 

The only limitation has been recurring donations. To address this Google launched Google Subscriptions and now we need to get support into CiviCRM so we can enjoy a single free processing fee payment gateway.

 

A new Make it Happen iniative was launched to get this going in 4.1 or even 3.4 if we meet the campaign...

Read more
04 April, 2011
By shot
Filed under v3.4 and v4.0, CiviCRM

Stable is getting closer and closer, as proved by a second pair of betas for CiviCRM 3.4 and 4.0!

An remember - if you didn't already, make sure you read "Step up and help out" section of this blog post!

The newest versions are:

  • 4.0.beta2 for Drupal 7 and Joomla 1.6
  • 3.4.beta2 for Drupal 6 and Joomla 1.5

Please remember this is an BETA release and it should NOT be used on production sites - however, we enourage you to install it on your test sites and let us know about any bugs or problems. If you want to find out what's the beta/final release schedule - it is available on our wiki.

There are a few public sandboxes where you can try one (or many) of above versions:

Read more
29 March, 2011
By shot

I’m happy to announce the rebuilding of CiviCRM translation resources. If you’ve been a visitor to our Transifex page previously, you know that CiviCRM always ran two concurrent sets of translation resources – one for the stable version and one for the upcoming version (since its first beta release). This was cumbersome – and is the past now.

From now on there’s only one set of resources (POT templates, translated to per-language PO files), cunningly generated from a set of recent versions (the current set is built to cover CiviCRM 3.2, 3.3, 3.4 and 4.0). This is a welcome change for both our beloved translators (no more version confusion!) and your l10n maintainer, who no longer needs to synchronise translations across versions. Our full translation...

Read more
24 March, 2011
By michal
Filed under v3.4 and v4.0

Stable is getting close! This week, we bring you totally new thrill in CiviCRM Releases series (season 3.4/4.0) - the BETA1!

An remember - if you didn't already, make sure you read "Step up and help out" section of this blog post!

Versions released today are:

  • 4.0.beta1 for Drupal 7 and Joomla 1.6
  • 3.4.beta1 for Drupal 6 and Joomla 1.5

Please remember this is an BETA release and it should NOT be used on production sites - however, we enourage you to install it on your test sites and let us know about any bugs or problems. If you want to find out what's the beta/final release schedule - it is available on our wiki.

There are a few public sandboxes where you can try one (or many) of above versions:

  • ...
Read more
22 March, 2011
By kurund
Filed under v3.4 and v4.0, API

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:

 

$params = array(&#39;version&#39;=&gt; &#39;3.0&#39;, &#39;location_type_id =&gt; 1 etc.);<br />
$result = civicrm_location_add($params);


This version param now conflicts with the version parameter introduced in API v3, were we use the version to determine if API v2 or API v3 will be used. So the call will now be something like:

 
... Read more
21 March, 2011
By shot
Filed under v3.4 and v4.0, CiviCRM

Paging all multilingual CiviCRM users: We’re considering turning some of the multilingual fields back to be monolingual (i.e., have the same values in all languages, even on a multilingual installation), and your feedback on this is crucial. Since the introduction of multilingual capabilities in CiviCRM 2.1 we only ever added new fields to the multilingual set (fields that can have different values in different languages). Most of our choices were right, but after a couple of CiviCRM versions we’re hearing feedback that some of the multilingualisations cause more harm than good. Thus – we’re considering turning the following CiviCRM fields (in practice, their counterpart database columns) monolingual:

Contact names

civicrm_contact.sort_name, .display_name, .first_name, .middle_name, .last_name, .household_name, .organization_name and ....

Read more
17 March, 2011
By michal
Filed under v3.4 and v4.0

Did you already try CivicRM 3.4 and/or 4.0? If not, we're releasing next alpha version, third one, especially for you. :-) Before downloading, make sure you read "Step up and help out" section of this blog post and let us know what you think (and what problems did you encounter).

Versions released today are:

  • 4.0.alpha3 for Drupal 7 and Joomla 1.6
  • 3.4.alpha3 for Drupal 6 and Joomla 1.5

Please remember this is an ALPHA release and it should NOT be used on production sites - however, we enourage you to install it on your test sites and let us know about any bugs or problems. If you want to find out what's the beta/final release schedule - it is available on our wiki.

There are a few public sandboxes where you can try one (or many) of...

Read more
10 March, 2011
By michal
Filed under v3.4 and v4.0

Here's another double release, fresh and ready, being a perfect opportunity for you to contribute to your favourite Open Source project (How? See "Step up and help out" section of this post):

  • 4.0.alpha2 for Drupal 7 and Joomla 1.6
  • 3.4.alpha2 for Drupal 6 and Joomla 1.5

Please remember this is an ALPHA release and it should NOT be used on production sites - however, we enourage you to install it on your test sites and let us know about any bugs or problems. The beta/final release schedule is on our wiki

There are a few public sandboxes where you can try one (or many) of above versions:

Read more
25 February, 2011
By lobo
Filed under v3.4 and v4.0

Overview and New Features in CiviCRM v3.4 / v4.0 With the release of 3.4.alpha1, a brief tour of some of the new features and changes in v3.4 / v4.0 is in order. This release had 7 successful Make It Happen Projects. We also had a record number of patches (100+) that were incorporated into this release.

  • v3.4 and v4.0 have the same set of CMS independent features. v3.4 supports Drupal 6.x and Joomla 1.5.x only. v4.0 supports Drupal 7 and Joomla 1.6.x. v3.4 is expected to be the last release to support D6/J1.5.
  • API v3 - The new version 3 API contains the standardisation that many of us have been hanging out for. The names of the function files and the functions have been standardised as have the inputs and outputs. There is a new wrapper function: civicrm_api( entity,action,$params ); to make it easier to call. If you have any doubt on how to...
Read more
24 February, 2011
By michal
Filed under v3.4 and v4.0, Drupal, Joomla

It's been a while since CiviCRM 3.3 went stable and the world around changed a bit: Drupal 7 and Joomla 1.6 were released. Since making CiviCRM work with new versions of these two CMSes required some backwards incompatible changes, we're releasing two versions of CiviCRM:

  • 4.0.alpha1 for Drupal 7 and Joomla 1.6
  • 3.4.alpha1 for Drupal 6 and Joomla 1.5

Please remember this is an ALPHA release and it should NOT be used on production sites - however, we enourage you to install it on your test sites and let us know about any bugs or problems.

There are a few public sandboxes where you can try one (or many) of above versions:

Read more