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...Migrate from Adequation Localization Extensions to DNN Content LocalizationMigrate from Adequation Localization Extensions to DNN Content Localization
Previous
 
Next
New Post
3/15/2012 9:40 AM
 

Paul,

I was just wondering how the Adequation Extensions worked.  I do know all about how the built-in DNN localization works. Personally, I think DNN corp took the wrong path but that is just me.  Unfortunately there aren't many other options.  I have used Apollo pagelocalization and prefer it's method but since Erik V. has joined DNN corp, the code has languished.    I have pulled down a copy of the source and am in the middle of making sure it works with the current DNN version but I am not done yet.  (Not my top priority in my free time)  I do plan on making it available once I am done for those that don't want to use the built in content localization.

good luck on your migration.

Robert

 
New Post
3/19/2012 4:51 PM
 

Hi,

1) about your steps,

if you meen with "manually migrate content from the defunct second language pages to localized versions of base language pages" realy copy manualy the content of each module to the new created modules in the second language, then its ok (or make a export/import). Because you cant "add existing module" from first language to second language.

2) The difference between "Adequation Localization Extensions" and "DNN Content Localization" is very small.

So in reality, you have only to change some fields in the "Tabs" and "TabModules" to create the relationship between pages of first language and pages of second language + the for the modules.

This can basicly done by a SQL script or more easily i think with some programing.

PS : to make your life easier with "Core content Localization" look at http://dnncltools.codeplex.com/

 
New Post
11/18/2013 4:12 AM
 
Hi There.
I also used Adequation Localization Extensions. but they say this is now obsolete.
I don't know why. Maybe because i don't understand the new localisation from DNN6/7 not yet.
But what i want is a mulitilangual website where every language has it's own menustructure, independent from the other languages.
Not one structure that needs to be translated in diffferent languages.
Is this even possible in the new localozation from DNN?

if so, How?

i need to learn more about the new localization.

Thanks for answering

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...Migrate from Adequation Localization Extensions to DNN Content LocalizationMigrate from Adequation Localization Extensions to DNN Content Localization


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