Skip Navigation LinksHome / Community & Support / Developer Productivity Tools Forums / ASP.NET AJAX > RadControls in DotNetNuke > RadGrid localization isnt working

Not answered RadGrid localization isnt working

Feed from this thread
  • Patrik Johansson Master avatar

    Posted on Jul 29, 2010 (permalink)

    I've tried to localize the RadGrid following the instructions from Telerik to the letter, but it just doesnt seem to be working. The resourcefile is in the App_GlobalResources, with correct name (RadGrid.Main.sv-SE.resx) and the culture of the RadGrid has been set to sv-SE. In fact, when I tried to edit something in the RadGrid.Main.resx, that didnt work either it seems.

    I've been reading about some problems with resource files and DotNetNuke, and that with RadEditor etc. you could use the LocalizationPath, but that doesnt seem to be available for the RadGrid. Not sure how to interpret what I've been reading about the resource files and DotNetNuke, is it just that it isn't  working in the same way as the resource files in DotNetNuke, or is it that it is not working AT ALL (maybe DotNetNuke prevents access to the resource files in App_GlobalResources or anything like that).

    Can anyone confirm that the localized resource files do actually work in DotNetNuke for RadGrid??

    Reply

  • Pavlina Pavlina admin's avatar

    Posted on Aug 3, 2010 (permalink)

    Hi Patrik,

    Unfortunately DNN does not support ASP.NET localizations mechanisms. Thus the built-in RadGrid localization will not work by default in such environment. In order to workaround this DNN limitation you may consider using explicit localization through code (more details under Controls->RadGrid->Localization/Accessibility) or maybe consider/implement a 3rd party localization provider for DNN such as this one.

    Regarding the localization path, we will consider adding such property in a feature version of the control.

    Best wishes,
    Pavlina
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

    Reply

  • Say Hello to Telerik's PivotGrid for ASP.NET AJAX, Silverlight, WPF and WinForms. Now packed with OLAP support.
  • Patrik Johansson Master avatar

    Posted on Aug 11, 2010 (permalink)

    Thanks for the information regarding the "DotNetNuke ASP.NET Localization BuildProvider"! Didn't know about that one and will definitly have a look at it. Has anyone tried it out and can confirm that it works well with the latest DNN versions and that it seems to solve this problem (which really doesn't seem to be Teleriks fault)?

    Reply

  • Pavlina Pavlina admin's avatar

    Posted on Aug 12, 2010 (permalink)

    Hello Patrik,

    I'm afraid that, at this time the only way to use the built-in RadGrid localization in DNN will be to use a 3rd party localization buildprovider.

    Regards,
    Pavlina
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

    Reply

  • Patrik Johansson Master avatar

    Posted on Aug 20, 2010 (permalink)

    So, will the newly release DNN 5.5 solve this problem, as it should have better support for localization?

    Also, how come the RadGrid doesnt seem to have any support for LocalisationPaths like some other controls have? I am REALLY trying to understand how it can be possible not to include this property in what must probably be your most popular control by far, but no matter how hard I try, I just can't understand how it can be possible. It really should be included in the next release, I mean, how hard can it be since you already have this in other controls? :)

    Reply

  • Pavlina Pavlina admin's avatar

    Posted on Aug 25, 2010 (permalink)

    Hello Patrik,

    As already stated, we will consider implementing similar to RadEditor's LocalizationPath functionality for a future version of RadGrid control. Meanwhile you should consider using the suggestions from my previous message.

    Please excuse us for the inconvenience.

    Greetings,
    Pavlina
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

    Reply

  • Patrik Johansson Master avatar

    Posted on Aug 25, 2010 (permalink)

    What I mean is that it is a bit odd that some of the controls seem to offer full support for localization several ways, others one way, and yet others not at all. In a site where you use localization, it would seem logical that not only parts of the content is localized but all of it, or nothing. Of course, some of the controls perhaps are not really "localizable". I've seen reports that the "DotNetNuke ASP.NET Localization BuildProvider" might not work as expected with the latest DotNetNuke versions, even though it is of cource not your fault that DotNetNuke has limitations in its handing of standard .NET localization.

    Reply

  • Patrik Johansson Master avatar

    Posted on Oct 1, 2010 (permalink)

    I still think that the localization path option should be added to the RadGrid as well, and I am sure other customers would want this to (if I am right, please let Telerik know this).

    However, my main question right now is rather if anyone has experienced with removing the " <remove extension=".resx" />" from the web.config in DNN? This is the line that is killing the support for standard ASP.NET localization (so this really isn't Teleriks fault to be honest). I've done it in our development environment and so far, it seems like I currenly have both DNN and ASP.NET localization working, but further testing is required.

    Reply

  • Pavlina Pavlina admin's avatar

    Posted on Oct 1, 2010 (permalink)

    Hello Patrik,

    Our developers are still researching how to implement this functionality. I am afraid I can't provide specific timeframe as to when the RadGrid's LocalizationPath functionality will be available.

    Please excuse us for the inconvenience caused.

    All the best,
    Pavlina
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

    Reply

  • Say Hello to Telerik's PivotGrid for ASP.NET AJAX, Silverlight, WPF and WinForms. Now packed with OLAP support.

Back to Top

Skip Navigation LinksHome / Community & Support / Developer Productivity Tools Forums / ASP.NET AJAX > RadControls in DotNetNuke > RadGrid localization isnt working