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 5:55 PM
 
JGS DNN Fan wrote:

When it comes to Content Localization, DNN receives a failing grade.  The other items in DNN, such as the speed increases, are a great addition.

If DNN wants to be a serious international CMS player, then they need to deliver world-class Content Localization functionality. 

We want DNN to succeed. 
 

Jud,
I understand your frustrations with the 5.5 release, you bring up some valid comments, but let me ask you something. If you really want DNN to succeed, then why come in here flaming mad and posting content that will only aggravate people?

The same thing with your review on Codeplex, how does that help DNN succeed in anyway? You basically give DNN a horrible review, and anyone who reads your review may very well be scared off from the product altogether, and that sure as hell won't help DNN succeed.

You definitely bring up some valid concerns, and you are more than welcome to ask for a response from DNN Corp, but coming in ranting and raving is highly unlikely to get someone to respond civilly to you.

If you are interested in purchasing the PE version and would like to get some answers about fixes, please feel free to email sales@dotnetnuke.com and the sales team can follow up with you.

Chris


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
8/23/2010 6:04 PM
 
@ Jan & JGS

Fair enough, thank you for taking it easy on me, I expected some heat from my comment.

I'm glad to hear you both have contributed and tried to do more for the community. But, for those who have not yet gotten involved and want to or are new here it may be beneficial to know that there are ways to get involved and to be able to test things out before committing to DNN or upgrades for that matter.

Jan, I know I have benefited from your postings and suggestions, never said I didn't, that's exactly why I'm a community member, I don't require bleeding edge DNN and am content waiting for the trickle down of DNN'ers who put so much into the platform. For that, I thank you.

I too am waiting for more native support of ML in DNN, since I hesitate to purchase modules and prefer to get the functionality in the Core looks like I'll continue to wait for some things but I wont take away from the good DNN provides by "biting the hand that feeds me".

Rock On!
 
New Post
8/23/2010 6:05 PM
 
This problem was not identified during the QA phase for 5.5 - nor was it reported during the Public Beta phase ( which provided the ability for anyone in the DNN community to download the package and test it in their environment ). So I can not explain why it was not discovered prior to release, but I can guarantee that it will go on the hot list of items which will be addressed in 5.5.1.

It would be very helpful if we could get a bit more detail on the exact configuration of the sites affected. Does it reveal itself immediately after an upgrade? If so, what are the localization settings? How many languages are installed/enabled? How are the problem URLs formatted? Is the system throwing errors, or is it not navigating to the proper location? Or does this problem only occur after you Enable Content Localization?

Please help us to help you by providing all the info needed to reproduce the problem, diagnose it, and resolve it.

My comments are my own and are offered WITHOUT PREJUDICE

Shaun Walker
http://www.siliqon.com
 
New Post
8/23/2010 6:22 PM
 
Jan Olsmar wrote:
Sebastian, sure its a major extention and I had expect lot of small bugs. However if you release a PE and CE version I thiks the release should work for most of the users that will use it in an multilanguage enviorment.
But...it does not work for anybody!!!

Jan, this is not true - DNN 5.5.0 works fine for any DNN installation with a single language enabled - considering 95% of the paid installations be in the U.S., Australia, GB and their territories (nearly all single language), as well as around two of three of the other installations being single language as well, by far the majority of the sites will still be not affected after the upgrade. Those numbers are (my personal) assumptions, and of course a higher rate would be preferable - but for any existing multilingual site, upgrading to DNN5.5 with content localization will be a breaking change and require major attention.


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 6:33 PM
 
Shawn all needed information is in gemini I think.
Just upgrade a site with more than one language.
I dont think this issue was in the beta's I think it was introduced in some of your internal builds between the beta and the release.
The problem is if or if not you enable localization.

The problem is logged in gemini!!

If you don't find error like this and the other error I logged, dont blame the Community as usual -  blame your QA process!!
If you need more information please log them in gemini on the issue.
http://support.dotnetnuke.com/issue/V...
http://support.dotnetnuke.com/issue/V...
http://support.dotnetnuke.com/issue/V...

 
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