Home » Forums » Ubercart » Support

Multi language übercart store

Submitted by drupalhizmetleri on Thu, 07/03/2008 - 06:47
drupalhizmetleri

Posts: 69
 Joined: 01/23/2008

Does anyone have experience about multi language übercart store? (Not just translating the fixed übercart text). Is the drupal intertationalization module fine for this purpose. Or is there any other solutions for this?

And how can i force the customers to select the product quantity in English site with amount of 1 and in Turkish site with amount of 10? Is this possible?
permalink #1 Fri, 07/04/2008 - 03:01
zmove
Posts: 534
 Joined: 08/13/2007
Bug FinderEarly adopter... addicted to alphas.Getting busy with the Ubercode.Internationalizationizer

Internationalization is pretty good with drupal (espacially 6.x), with ubercart too, but both have some translation limit that make you feel crazy sometime Eye-wink

For example you can't translate :

  • Products attributes & options
  • Tables header generated with tapir
  • Many small things I don't remember

So it's very small things, but not minor things. When you want to provide a multilanguage website and your product attributes are not translated, it's very annoying... But I think it will be corrected for the drupal 6 version of ubercart isn't it Ryan ? Eye-wink

So, ATM, a multilanguage shop is usable, but with small concessions.

permalink #2 Mon, 07/07/2008 - 09:19
Ryan

Posts: 5269
 Joined: 08/07/2007
AdministratorHead Code Monkey - I eat bugs.

zmove wrote:
But I think it will be corrected for the drupal 6 version of ubercart isn't it Ryan ? Eye-wink

Your explanation sounds about right, but I'm not sure exactly how much we'll be able to fix with the initial port. Sticking out tongue I have a few ideas, but there are bound to be gaps...

permalink #3 Tue, 07/08/2008 - 09:31
zmove
Posts: 534
 Joined: 08/13/2007
Bug FinderEarly adopter... addicted to alphas.Getting busy with the Ubercode.Internationalizationizer

I'm not sure exactly how much we'll be able to fix with the initial port.

I'm not sure to understand that sentence, but I know that, even with the great improvements made with drupal 6, that all content is not translatable today. That's why modules like i18n continue to live even with drupal 6.

Maybe the solution can be in i18n itself, you could provide a module for i18n to translate all content that cannot be translated with the drupal core. Like that, it would not be required for a non multilanguage website, and, after all, all "true" multilanguage website require i18n.

If you don't want to add dependencies like that, maybe the t() function is the key, but I'm not sure if it's doable with variables like attributes...

A third solution would be to add a language option for all non translatable attributes (and so, a language column in the database), this column could be added if you enable the multilanguage content core drupal module.

Even if drupal have some multilanguage missing features in core, there are a lot of ways to deal with it Eye-wink