Drupal Multilingual Tips – Browser Settings, Session Params and Account Settings

I have a front/login page that is available to anonymous users. I need to be able to deliver the page bilingually but I rely primarily on the Drupal account settings and language switcher to determine whether the site is presented in English or Spanish. So how do I present in Spanish to anonymous users when appropriate? Drupal also allows you to use the user’s browser settings as well to determine what language to display. And it also allows you to change the order of factors to determine what language to present in. After some testing and a lot of thought about the UX, I have settled on,

  • Browser settings – Helps for Anonymous
  • Session parameter – If a Spanish defined account want to use the language switcher to get English instead for that session
  • Account settings – The catch-all
  • Default site language

In my specific case, this will provide the most flexibility for my audience.

Drupalchat and User Relationships

The integration from User Relationships and Drupalchat works as I hoped it would. Out of the box, Drupalchat for authenticated users allows all users to see everyone. But with the integration, you can create a buddy list.

the one other thing that i need is a way to have any authenticated user communicate with me. especially in the beginning so that I can provide a high level of support for the pioneering members. I believe that can also be done.

Here is what you see from the Drupalchat config screen regarding User Relationships:


Relationship method

 All authenticated users
 User Relationship module
This determines the method for creating the chat buddylist.
User Relationships Role Names to integrate with

The singular form of User Relationships Role Names (e.g. buddy, friend, coworker, spouse) separated by comma.

Panel Pages, Views and Variants – UX

I feel like such a slacker because I didn’t post anything at all yesterday. But I have my two kids with me this weekend, and being a divorced dad doesn’t allow for much inattention when you do have them! And we’ve had fun. But, now, back to work.

I am working with the functional layout of the pages. This is where the storyboarding techniques come in handy. Writing out what will happen, how the user will react to it, what they expect and what you ARE ABLE to deliver. Drupal can do a lot. It can do about anything if you have all the skillsets needed. But, if you are working with the system in a drag and drop, plug n play sorta way, you will need to be creative in how to meet the needs of your customer.

So, i have all the diagrams about how the user will see what is available. and i have created most of the functional elements by combining core features (aggregator items, blogs and forums, etc) with Views. Views is the key.

Then, i take the View and create an interface based off of Panels. Now this will get most of the functions and workflows in the proper place. But it will look really bare boned. So after I get the main parts of the functionality in place I will begin to style everything with CSS. Then, it will be more or less complete. Once I get the core functions in place, I’ll put the name of the site out there for anyone who cares see how it fits together. There are sure to be other elements of theming in place at that point as well.

One of the things worth mentioning in using variants to supply different users with different content from the same page. and this is where variants come into play.