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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0More Localization ProblemsMore Localization Problems
Previous
 
Next
New Post
3/5/2008 4:16 PM
 

Sorry if this has been already posted but I couldn't find it in any of my searches.

I have been having quite a few problems with localization.

First, the fact that DNN doesn't localize CheckBoxLists correct  forced me to hardcode the text on all CheckboxLists which sucks.

Now, while bulletproofing I have came across another when using a RequiredFieldValidator you can't use the resourcekey ErrorMessage correctly.

This code

<asp:RequiredFieldValidator ID="FieldNameReq" ControlToValidate="FieldName" resourcekey="FieldNameReq" Text="*" runat="server" />

Using this resource

  <data name="FieldNameReq.ErrorMessage" xml:space="preserve">
    <value>Field cannot be blank</value>
  </data>

Displays a blank ErrorMessage in the ValidationSummary but

This code

<asp:RequiredFieldValidator ID="FieldNameReq" ControlToValidate="FieldName" resourcekey="FieldNameReq.ErrorMessage" Text="*" runat="server" />

Using this resource

  <data name="FieldNameReq.ErrorMessage" xml:space="preserve">
    <value>Field cannot be blank</value>
  </data>

works but it replaces the Text with the ErrorMessage and of course that is not correct.

I'm I just missing something or localization not fully functional? Any insight would be greatly appreciated!

 

 
New Post
4/19/2008 4:14 PM
 

Hi Josh,

I see that no one has responded, so I'll throw in a comment.  While there are some shortcomings with the DNN localization, it is overall a very solid system.

If you are not able to circumvent the problems you're having, it is possible to re-enable the ASP.NET localization features.  I was recently forced to do this in a project where I had a number of existing usercontrols.  If you're interested in going this route, let me know.

Brandon


Brandon Haynes
BrandonHaynes.org
 
New Post
4/21/2008 1:59 AM
 

Try this:

Code

<asp:RequiredFieldValidator ID="FieldNameReq" ControlToValidate="FieldName" resourcekey="FieldNameReq" Text="*" runat="server" />

Resource

  <data name="FieldNameReq.Text" xml:space="preserve">
    <value>Field cannot be blank</value>
  </data>

The ErrorMessage extension doesn't work (as expected).

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0More Localization ProblemsMore Localization Problems


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