Blogs

Hi all,

Was reading lobo's latest blog and I'm almost sure that with these improvments we can have an event smoother event registration. The workflow would be:

So far so good, same as before

Rumour has it that certain, ahem, consultants have been known to, on occasion, miss setting up the occasional CiviCRM cron, or not notice when the cron stops working on upgrade. Such consultants could wind up with egg on their face over crons. Somewhat less culpable are the CiviCRM newbies who didn't know their event waitlists wouldn't work or their memberships wouldn't roll over without the right cron.

We are super pleased to annouce CiviCRM developer and implementor training in London this May 18th and 19th in partnership with the CiviCRM core team.

We're very pleased to annouce that CiviCon is coming to London this August 22nd.

In the grand tradition of CiviCons, we've timed this one to co-incide with DrupalCon London (though we haven't gone quite as mad as they have with UK branding cliches).

Many modern web applications have a lot of spam deterrent such as Captcha, Bayesian filters, URL, ip detections etc. One example is trying to do 2 consecutive search on the CiviCRM.org forum and you will get a an error that look like

"Your last search was less than 5 seconds ago. Please try again later."

The concept behind this is flood control is to prevent a webbot (automated script) that is trying to spam and flood the server. 

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.

The team is excited to announce the release of CiviCRM 3.3.6 - it is now available for download. You can also try it out on our demo site. This is a bugfix release resolving a few issues.

Update: We now have sponsorship committed for 63% of this project and have started a Make-it-Happen Campaign!

CiviEvent is the most popular CiviCRM Component. We get a steady stream of feature requests along with quite a few patches. We were approached recently by an organization that wanted to add Reminder Emails for CiviEvent.

We had a quick online and offline conversation with them and realized that there was a fair amount of cool integration so an event administrator could schedule and send messages to event participants. Briefly the set of features would include:

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:

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: