Have been trying all day to get language support to work, or rather not to work, as our different portals only have ONE language and we want no interference from DNN in this regard.


But even though we have disabled the "Use language parameters in URLs" (its called something like that) we are still getting URLs including /language/fi-FI/ which is NOT a part of the urls the pages should have. But this seems very random, different web browsers get different results, some reporting getting "301 redirects" from DNN to use these faulty links, while other stay on the URL they should have.

How can we make sure that DNN does not try to do any trickery with languages etc? We would like to have different cultures set though, if possible, but we can skip that if we can just get this to work...

Any ideas are welcome? This is just one of the problems we have experienced with DNN 9.1 which does unfortunately not seem to be ready for production usage...

Thanks. We did do a bit of debugging and found out what seems to be that with more than one language enabled, DNN9 ignores all other settings about language, including the one about letting the user decide the lanuage. This was not obvious at first since we have a custom skin that does not even display the flags, but we saw this using the debugger. None of this however explains why different browsers showed different results, and even the same browser and version showe different paths. Something is definately fishy here.

Will do that, but the problem is finding a secure way to reproduce it as the problems seem very random.