Skip to main content

CiviCRM multilingual and customization: nice progress!

Today we've launched the 2012 French for the Future National Essay Contest. The full site is someone else's, but the contest submission pages are built using CiviCRM.

The essay submission pages are actually implemented as event registration pages of CiviEvent, which isn't exactly what CiviEvent is built for, but was close enough and provides some nice functionality that other alternatives (e.g. a simple CiviCRM profile) wouldn't provide.

Before starting, my biggest fears were around the custom presentation bits. My first CiviCRM implementation was back in 2006, and ever since then, my standard wisdom for anyone using CiviCRM is that CiviCRM is great as a CRM, but less great in exposing itself on your website. Partly, that's because CiviCRM is CMS agnostic, so it can't use all the great tools that I'm accustomed to with Drupal (notably the forms api), but also because of the whole Smarty/QuickForm architecture, which was okay for the day, but now way behind the competition.

On the other hand, CiviCRM has put a lot of work into improving this aspect over the past few years. My personal favourite trick, ever since learning jQuery and having that available for CiviCRM pages, is to use it via the theme layer or a custom module for almost any cosmetic changes. It's cheap, easy, safe and powerful. But it won't do functionality changes - for that, the new hooks are a nice complement.

Another great example - the new ability to add multiple profiles to event signups. Breaking up the fields into groups (which have to correspond to separate profiles), is both sensible from a useability point of view, as well as backend organization.

What I hadn't experimented with so much was the multilingual option, which until recently (i.e. mysql 5.1) required very unsafe mysql permissions for the site. But after one earlier success, I jumped in and have been surprised all the way along - the functionality has been perfect, and the administrative tools more than adequate. Particular thanks to DaveD for pushing forward the new "Word Replacement" feature (but no points for changing the name from string replacement and hiding it in the options section, I almost didn't find it!).

So my report from this project is: awesome, and thanks. I had a highly detailed-oriented client, and could satisfy almost all her requests.

CiviCRM also was able to import previous year's data, and next we'll be setting up donation pages and testing CiviMail.

Popular posts from this blog

Me and varnish win against a DDOS attack.

This past month one of my servers experienced her first DDOS - a distributed denial of service attack. A denial of service attack (or DOS) just means an attempt to shut down an internet-based service by overwhelming it with requests. A simple DOS attack is usually relatively easy to deal with using the standard linux firewall called iptables.  The way iptables works is by filtering the traffic based on the incoming request source (i.e., the IP of the attacking machine). The attacking machine's IP can be added into your custom ip tables 'blacklist' to block all traffic from it, and it's quite scalable so the only thing that can be overwhelmed is your actual internet connection, which is hard to do.

The reason a distributed DOS is harder is because the attack is distributed from multiple machines. I first noticed an increase in my traffic about a day after it had started - it wasn't slowing down my machine, but it did show up as a spike in traffic. I quickly saw that…

CiviCRM's invoice_id field and why you should love the hash

I've been banging my head against a distracted cabal of developers who seem to think that a particular CiviCRM core design, which I'm invested in via my contributed code, is bad, and that it's okay to break it.

This post is my attempt to explain why it was a good idea in the first place.

The design in question is the use of a hash function to populate a field called 'invoice_id' in CiviCRM's contribution table. The complaint was that this string is illegible to humans, and not necessary. So a few years ago some code was added to core, that ignores the current value of invoice_id and will overwrite it, when a human-readable invoice is generated.

The complaint about human-readability of course is valid, and the label on the field is misleading, but the solution is terrible for several reasons I've already written about.

In this post, I'd like to explain why the use of the hash value in the invoice_id field is actually a brilliant idea and should be embrac…

Upgrading to Drupal 8 with Varnish, Time to Upgrade your Mental Model as well

I've been using Varnish with my Drupal sites for quite a long while (as a replacement to the Drupal anonymous page cache). I've just started using Drupal 8 and naturally want to use Varnish for those sites as well. If you've been using Varnish with Drupal in the past, you've already wrapped your head around the complexities of front-end anonymous page caching, presumably, and you know that the varnish module was responsible for translating/passing the Drupal page cache-clear requests to Varnish - explicitly from the performance page, but also as a side effect of editing nodes, etc.

But if you've been paying attention to Drupal 8, you'll know that it's much smarter about cache clearing. Rather than relying on explicit calls to clear specific or all cached pages, it uses 'cache tags' which require another layer of abstraction in your brain to understand.

Specifically, the previous mechanism in Drupal 7 and earlier was by design 'conservative' …