For many bilingual websites, the standard Language Switcher block that comes with the locale module (shows both language links in one block) will suffice. However, for Canadian Federal Government sites, the more typical method is to have a menu item in the top nav which shows only the single flip language.
I have come across a few implementations of this all which are implemented in templete.php. Since this is not the correct way to do this (since this is not a theme function) I thought I would document how we do this at LiquidCMS.
We are currently involved in multiple bilingual Drupal 7 projects. As we proceed with development we are coming across numerous i18n related issues. I thought it might be useful to list the various issues/fixes/patches/solutions we are providing all in one spot.
A very useful module in D6 days called Admin Role. It attempts to convert the concept of the superuser (uid = 1) to a role; thereby allowing multiple users to be the superuser. Obviously a concept that should be in Drupal core. So much so that in D7 they did included this into core. The downside of this is that they totally screwed up its functionality and despite attempts to get the functionality fixed (Admin role should always provide all permissions (create a superuser role)); no such luck.
On most projects we have node types created which we have no reason for full page views. Typically these are support node types. If we mix this with the concept that NO page that a user should be able to see should ever have a url like node/456 then it is simple to simply implement the following logic:
If a node page does not have a url alias defined; let's not allow access (unless admin).
The University of PEI (subcontracted from Dave Kisly) required a complex multipaged user registration form for their CAUBO project. There are a few posts around on creating multipage forms, but most are incorrect, don't apply well to the user registration process or are simply too complex to map to your specific requirements.
We did an initial version of this registration module based on one of these recipe guides but with numerous changes from the client it eventually became a very messy piece of code that was too complex to continue with all the changes required.
Just a quick note to those followers of our blog - as of around August 13, 2010 the Dev release of Views 2.x now supports cloning a display. Very cool feature and huge time saver so thought i would mention it.