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!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

Fixing issue with Portal Localization if using a non en-us default language

I recently blogged about the Portal Localization enhancements in DotNetNuke 5.4.0 ( Unfortunately theres a potential problem that may occur if users use a particular configuration.


As mentioned in my previous post Portal Localization supports multiple fallbacks. If a localized record for a culture cannot be found (i.e. does not have an entry for that portal in the PortalLocalization table), it wil automatically "fallback" to it's fallback language e.g. de-AT might fallback to de-de. If no record is found for that it will fallback to the portal fallback - by default this is en-us. An en-us record always exists (it's created as part of the install). However if users have changed their portal default language to be a language (e,g. fr-fr) that does not have a portal localization record for that language, then no data is returned and an error can occur. This was an oversight in the design that was missed as the capability to change the portal default language was only added in 5.3.1. We'll resolve this in the next release (5.4.1), probably by adding some additional logic around the enabling of a portal default language that ensures that a localized record always exist (i.e. a line exists in PortalLocalization for that culturecode and portalid).

You can avoid this happening by either not setting a non en-us portal default language. Alternatively if you need a non en-us portal default language, you can avoid an error occuring by going to site settings and selecting the culture you're using as the portal default language and pressing update - this will create an entry in PortalLocalization ensuring there is always a fallback.

Workaround for issues

If you've accidentally configured your site so that no valid fallback record exists you can resolve this manually in one of a few ways. First of all open the PortalLocalization table in your database and inspect the entries. In this case I'm having issue's as I don't have a record for de-AT, which has a fallback chain that doesn't include de-de or en-us.

To fix this I can simply copy the de-de record and change it's culture to de-AT.

Alternatively I could have updated the FallbackCulture to ensure I have a valid fallback . In this case I've updated the de-AT entry in Languages to set's it's fallbackculture to de-de, which I know has a valid localized record in PortalLocalization.

Please note, we always recommend you do a full database backup before doing direct database updates - and only using them in case of emergencies. Finally, if you make a direct database update you'll need to force cached data to expire so DotNetNuke is aware of the changes - if logged in as host go to host->host settings and click "restart application". If you can't access that page, you can edit web.config (e.g. add a space, delete the space and save the file) to force an app recycle.


Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Davies (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out