Hello,

I've previously opened a post about MLHTML and RadEditor, but after more testing, it seems the problem lies elsewhere, so I thought I'd open a new thread to show what I've tied, since neither RadEditor or MLHTML seem to be the problem.

(previous post http://www.dotnetnuke.com/Community/F...)

The problem is when making a link using both EALO or Apollo on DNN 5.4.4, the links point to the wrong language. They show en-US or another language, but never the correct language. We've tried:

- 5.4.4 with RADEditor and Apollo
- 5.4.4 with FCKEditor and Apollo
- 5.4.4 with RADEditor and EALO
- 5.4.4 with FCKEditor and EALO

and nothing seems to work

we've also tried combinations with DNN 5.5 and also with DNNWerk modules, but this didn't work either.

could it be both EALO and Apollo are not usable on DNN 5.4 and above or is there another issue? anyone with the same issues? anyone got a multilanguage portal running 5.x? Any ideas? :)

kind regards,
Dennis

Good idea to look there, but we've looked there as well, but it's not en-US, it's one of the other 2 languages. (nl-BE) I've tried with host (which also has nl-BE as preferred language). It couldn't be en-US, since it's disabled.

- as a side note, when we try it in DNN 5.5, it adds /language/en/ instead of /language/en-US, even more strange..
- an other side note, why is it even necessary at all to add the language tot the links? DNN stays in the current language regardless of the /language/.. in the url?

Sebastian: have you tried this and have the same problems?
Dennis

Hi Sebastian,

I'm not that much worried about DNN 5.5.x, since it's very new and I've read about the changes in 5.5 regarding to language parameters/selection etc. But we can't get it to work in 5.4.4 either, must be there was a change in language parameter handling in 5.4 also. I guess we'll have to wait until EALO and/or Apollo fix things.

Dennis