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...DNN 5.5 and languages and urlDNN 5.5 and languages and url's
Previous
 
Next
New Post
8/23/2010 6:36 PM
 
Sebastian you are right, It does not work for anybody in an multilanguage enviorment. I should have been more precise.
 
New Post
8/23/2010 6:48 PM
 
Josh Wheeler wrote:
At risk of sounding like I'm picking sides here, might I just add an outsider's perspective. Though I am not affected by your predicament and can not understand to what extent this has complicated your existing and future business this is simply my opinion, maybe suggestion how you could approach this and other problems for that matter.

If you or your company has such an investment in DNN that breaking bugs, changes or features could affect you to this extent it would be advantages to be one of the Beta Testing users. I am not, and do not have a need to be as of now but can imagine that given some of the comments on this thread that if you are not now one you may want to become one.

To blame DNN for all your woes is a little short sighted and could prove to be bad for you.

On the other hand, getting involved, performing your own tests and making suggestions/requests during the Alpha & Beta testing stages could work to your advantage. I'm pretty sure that user features and fixes are now being included in the Core.

Furthermore, no one is "forced" to upgrade or even use DNN. If a version doesn't meet your expectations then get involved for future versions and try to get features added and bugs fixed that will benefit you and the community.

I get your plight, just not your approach, I am a community user and have not had to pay for more than a few modules and did so happily. They don't always work as hoped or expected but being cooperative and constructive has proven to be a good way to go.

Hope you all get this resolved soon, best of luck!

 Josh, according to you name, I assume you are a native English speaker and might not understand the vital interest of the others to get a localizable solution - for us it is a just basic need. That is the reason, why the European Network of DNN Professionals (www.dnn-europe.net) organized a workshop with this subject last year and a number of European members of the DNN core team spend time in the international team (due to the lack of members from Turkey, Israel, Arab countries or far East, we currently have difficulties to validate their needs in addition). DNN 5.5.0 is a big step into the multilingual direction, but there is still some way to go - and I doubt, that DNN will ever be able to fulfill everybody's needs - there is too big a risk to affect the majority of users. IMHO the strength of an application platform lies in providing a solid basis for extensions, which should be created by experts in targeted use cases.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/23/2010 7:15 PM
 
Sebastian Leupold wrote:Josh, according to you name, I assume ...

 Sebastian, you know what happens when you "ass-u-me" right?! ;-)

(sorry, just no way to respond without sounding like I'm gloating)
Well, actually, you are correct, I am a native English speaker, however, I lived in Brazil and speak the language fluently. I also created and manage a web system that is being used by 10 countries, 4 Continents and 5 languages for a Japanese based company. We had to create our own content and localization management systems to accommodate such diversity.

In addition to these sites we host 8 DNN portals, some B2C others B2B, on two separate installations, none of which I can say are Multi-Lingual, somewhat in part due to the lack of ML Support in DNN, the other part is we just haven't "had to" yet. (This is not counting my own and the side jobs I do with DNN)

One project we're vying for is a B2B project for our European Affiliate Companies and this will require extensive ML support. So, to say the least I was very disappointed when I came across this thread. This is exactly the type of thing I look for as part of my discovery process before saying I can or can not do something for a project. 

Even though this ML issue could be considered a setback for me, I didn't feel the need to take out my frustrations on anyone, rather, point out (if they didn't already know) how to get involved and make a difference.

For now, this just means that I'll keep reading the forums and watching the new versions until I feel that DNN has reached a point that it can support my "customer's" requirements. Until then I'll tell them what I can do and if they're Okay with that then great, we can do business!

This may not be the right place or time to mention this, but I'll do it anyway... If you are looking for some bilingual testers and feedback, let me know.

Thank you for hearing us.

 
New Post
8/23/2010 7:50 PM
 
Jan, I read your Gemini issue before I made my post in this forum. Although it mentions that the error happens after upgrade, it does not contain many of the other details I was hoping for ( ie. number of languages installed, whether or not there were language packs installed for each language, settings for each language ). It also does not indicate what the effect is - other than in one of the comments on the issue it indicates that "that all links that is rendered from menu skin object  sitemap etc is like www.yyy.com/pagename/tabid/zz/languag...". So there are no 404 errors ( ie. failure to resolve an inbound URL ) ?

I am not sure why you would think we would blame the Community for a bug in the product? I indicated in my earlier post that we did not discover this in our QA phase. I obviously wish we would have but regardless, we will ensure it is resolved for the 5.5.1 stabilization release.

My comments are my own and are offered WITHOUT PREJUDICE

Shaun Walker
http://www.siliqon.com
 
New Post
8/23/2010 8:14 PM
 
Shaun,
to support with Jan's issue: DNN 4.x to 5.4 used to have a language setting, controlled by a checkbox in Admin :: Languages menu item, called "Enable Language Parameter in URLs for Current Portal?". When unchecked, the language param would not be included in the URL.  In DNN 5.5.0, this option has been dropped (I validated earlier today). There is no effect of the number of languages installed or enabled or any resource files be present in the web site. I use this feature on www.deutschnetnuke.de (DNN 4.9.5), to use a single page URL to display content in proper language (English or German) accoding to the user's browser setting when providing a deep link, e.g. in these forums.
The issue has been properly reclassified by Alex from a show stopper (it is not breaking display of pages) to a major issue (breaking change to previous versions).

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...DNN 5.5 and languages and urlDNN 5.5 and languages and url's


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