It's a Drupal site... it's good if you actually know Drupal

I'm working on a Drupal 7 project right now where the site was built by another company. This isn't the first time I've “inherited” a project, and I'm sure it won't be the last. Before this project, my other experiences with taking over existing Drupal sites weren't terrible. Yeah, there were issues with the sites and things could have been better architected but, on the whole, I could jump in and figure out how things were glued together and fix issues or make improvements as needed without too much head-scratching.

This post explains how to configure some Drupal Commerce module package functionality for multiple countries and languages. This information was originally going to be part of my Drupal 7 Multilingual Sites book but I ran out of room!

I'm sitting in the Denver airport killing time before flying back to California. As everyone in Drupal-land knows, we just finished up the very successful DrupalCon Denver conference with over 3000 attendees!

I will keep track of any errata for the Drupal 7 Multilingual Sites book here and/or point off to the Packt errata page(s).

Nothing yet!

If you have very simple content translation needs, you might want to check out the Language Sections module.

There are different ways to access Drupal translation functionality depending on what is being translated. Here's a quick reference table for the various translation access points.

I was not able to include everything I wanted into my Drupal 7 Multilingual Sites book due to space limitations, so here is a list of some extra topics, tips, and tricks that didn't make it in:

My new book will be out soon!!!

http://www.packtpub.com/drupal-7-multilingual-sites/book

w00t!

Here are some Drupal 7 internationalization issues to track:

Here are many of the Drupal 7 i18n modules to help you create multilingual websites. Find more modules at the drupal.org modules search page.