Hello Gentleman,

We're experiencing a problem to get the RadEditor localized for a DNN 5.6.1 multi-language site (i.e. en-US - fr-CA).

As you know currently most of the modules that runs on DNN are auto localizable creating the corresponding .resx files using the Languages module editing the resx for the given language, this is also true for RadEditor, but RadEditor have a bug and don't get automatically change for the site language selected . The rest of the dnn world modules changes its language when a user select french flag, it displays all text strings on french, if user selects english flag displays all text strings on english if french resx are available for the module.

 We have tried  with the built in DNN Rad Editor since version  5.6 and 5.6.1 too, and both have the problem to get localized depending on the current site language selected by the user.

The DNN RadEditor don't take the resex translations unless you force it on the ConfigDefault.xml
setting utilizing the <property name="Language">fr-CA</property>
This makes the RadEditor to take the french Resex files, but also when the site is on english the Editor will be displayed on French due to this enforcement.

So this option only serves for a one language site installation, not for a multi-language site.

This confirms too that the french resex files are well placed for, Providers\HtmlEditorProviders\Telerik\App_LocalResources\   and that is not a problem with missing files or the directory.

We've tested different configuration removing the language property, or leave it empty or set value to "auto"  to get auto localization depending on language selected but the problem remains, so this is clearly a bug from the DNN RadEditor module.

The Problem is that we need that the RadEditor module be localized on a DNN multi-language site depending on the selected language.
DNN is 100% multi-language platform since  version 5.5, and DNN RadEditor is the main editor provider for DNN.
It must work properly for multi-language site as the rest of the modules, but it is not doing it. Any Ideas?

Is there a fix or workaround you can share to get this bug fixed soon as possible?

Please answer soon as possible, we need to get this fixed soon.

Thanks in advance.

Thanks Sebastian,

We've tried with it already, but unfortunately the dnnWerk RadEditor Provider 01.01.04 don't fix the reported problem.

I Hope that the reported problem can be addressed for the next DNN release.

If you or anyone have other suggestion to get this fixed, please share it.

Thanks in advance,
Javier Esteller