Upgrade from 3.1.1 to 3.3.3 issue : [L] prefix to localized stri

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

Home All Forums

1
2
3
4
5

Home

Getting Started

Installing DNN ...

Upgrade from 3.1.1 to 3.3.3 issue : [L] prefix to localized strings

7/27/2006 11:56 AM

Kall GUQUET

Joined: 10/11/2004

Posts: 7

Upgrade from 3.1.1 to 3.3.3 issue : [L] prefix to localized strings

Hi !

I'm working as a developer in a small IT company. One of the sites we've installed is running DNN 3.1.1., with 3.1.1 french language pack.

I recently decided to test an upgrade to 3.3.3 on a testing environment. The upgrade process went well but when I go back to my homepage, I notice that all the localized strings (with their values in resources files) are now displayed with a '[L]' prefix !

Since a google search with dotnetnuke + [L] ignores the brackets and returns all the sites containing dotnetnuke and the letter "L" I don't really know how to find someone experiencing the same issue !

7/28/2006 6:01 AM

Sebastian Leupold

www.dnnwerk.de
Joined: 3/8/2004

Posts: 46212

Re: Upgrade from 3.1.1 to 3.3.3 issue : [L] prefix to localized strings

[L] indicates to the developer, that the string is used from localization resource files.

This is only shown, if "show missing keys" in web.config is set to true (should be in developement envirements only).

Cheers from Germany,
Sebastian Leupold

Speed up your DNN Websites with TurboDNN

7/28/2006 6:24 AM

Kall GUQUET

Joined: 10/11/2004

Posts: 7

Re: Upgrade from 3.1.1 to 3.3.3 issue : [L] prefix to localized strings

Great ! This has solved the problem.

Still, I don't really understand how these keys could have been detected as missing, as they were shown on the site with their french translations.

Anyway I'll try to turn this web.config back on when 3.3.3 fr language pack will be released, to check if the keys are still detected as missing.

7/28/2006 10:04 AM

Sebastian Leupold

www.dnnwerk.de
Joined: 3/8/2004

Posts: 46212

Re: Upgrade from 3.1.1 to 3.3.3 issue : [L] prefix to localized strings

[L] indicates, that these strings are properly localized, all strings without [L] need investigation.

Cheers from Germany,
Sebastian Leupold

Speed up your DNN Websites with TurboDNN

Page 1 of 1

Home

Getting Started

Installing DNN ...

Upgrade from 3.1.1 to 3.3.3 issue : [L] prefix to localized strings

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:

No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
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.
Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
No Flaming or Trolling.
No Profanity, Racism, or Prejudice.
Site Moderators have the final word on approving / removing a thread or post or comment.
English language posting only, please.

Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

DNN Corp. (DotNetNuke)