Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...True Multi-Locale website - best approach?True Multi-Locale website - best approach?
Previous
 
Next
New Post
11/7/2008 9:27 AM
 

Be sure to look at ASPDNSF ML/DNN (www.aspdotnetstorefront.com) if you want a serious contender. Among it's may great features is the way it can be extended and customized. I mention it because it of course does a solid job of dealing with ML.


Eric Swanzey
www.swanzey.com
 
New Post
11/7/2008 9:32 AM
Accepted Answer 

DavidToohey wrote
 

The problem I'm hitting up against is that modules such as Catalook (and other e-commerce ones) aren't truly multi-currency and multi-locale... as at most they can handle content but not multi-currency.

Hi David,

Sounds like you should join the pro EU DNN group. In any case this is the exact subject I've been working on in the lost hours in DNN for a year now. My own document exchange is ML, but as you found out, many modules are not. The ambition currently is to have DNN support a least amount of ML functionality by v 5.1 (see also your other thread). About the discussion above I'd like to quote from my presentation at OF US last year on this subject:

You can make a ML solution either at (1) site level, (2) page level, (3) module level, or (4) content level. Let me explain:

  1. Site level: a site for every locale
  2. Page level: a page is flagged for display for a certain locale
  3. Module level: a module is shown depending on locale
  4. Content level: the module shows content based on locale

Now, the magic content and other 'wrappers' operate at level 3. There has been talk at DNN of implementing level 2. My goal is to push for level 4. The reason is that the 'lower' the level, the bigger the administration nightmare. OK, not all modules will be able to do ML, ever. And there are other reasons for having levels 2 and 3 as well. So I support an effort within the CT to implement those as well. But I really will do my best to get support for 4. This means for instance, that the module title must be localizable. Let's move forward ...

Peter

 


Peter Donker
Bring2mind http://www.bring2mind.net
Home of the Document Exchange,
the professional document management solution for DNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...True Multi-Locale website - best approach?True Multi-Locale website - best approach?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out