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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogContent Localizing, any ideas?Content Localizing, any ideas?
Previous
 
Next
New Post
2/6/2009 10:52 PM
 

So I do realize that as of today DNN modules do not support content localizing, but if I wanted to modify the blog to support it, can any one give ideas on how to do it? My thoughts are this, just add an extra field to the tables that have the data I want localized and build another set of procedures to retrieve the other language. 

Is there a better way? are there modules like blogs, calendars that already support content localization?

 

Thanks,

Viktor.

 
New Post
2/9/2009 2:44 AM
 

The blog module presents problems with localization for obvious reasons. 

I don't have a lot of experience with localization and only just started dealing with it in the past month for a client who wants multi-languages on her site.  We're using the Delisoft Localizator since the Apollo localization modules did not support search functions, at least not that I could see.  Apollo would work nicely as long as you don't your text content included in the dnn search index.  When using the Localizator with text modules, it's pretty easy to enter two modules, one for each of the two languages we are using, then use the Localizator module show/hide function with the language selection to filter content based on language selection.

With the blog module, we tentatively plan to use child blogs, one child for each language and make the appropriate entries in each child blog for each language.   I have no experience using child blogs but assume that the site visitor can select a child blog to view and only view entries for that child blog, and, in this case, filter the languages in doing so.  There may be a better way of localizing the blog module, and I'm curious what others have done to handle this.  This use of child blogs is one idea that may or may not work well, hopefully the former.  We may also attempt to see if we can place the child blogs on separate pages and then use the Localizator to show/hide the pages based on language selection, but the blog module itself may still allow or show both languages anyway; I don't know enough about child blogs and how they work to know exactly what will happen and what options we will actually have to implement this.  Again, I'd love to hear how others have approached localizing the blog module, too, or if they have gone to third party modules to do this.

Also, I would not recommend customizing the blog module itself.  You then end up with a module that can't be upgraded without custom programming it all over again at each upgrade.  I leave the core code as is and work around its quirks and limitations to avoid problems with upgrades, especially since DNN is fairly active in development, enhancements, and frequent upgrades.

Rick


JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

New Post
2/9/2009 10:56 PM
 

Thanks for your reply rick, i think using the child blogs is a pretty good idea, i may go that route. I downloaded both, apollo and dsl and having hard time figuring out how they work. That maybe because I only looked at it for 15 minutes. I need to spend more time on it soon.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogContent Localizing, any ideas?Content Localizing, any ideas?


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