DNN: 5.6.3
Scenario: In some cases, we need to use locales other than we desire to use. e.g some core & third party modules wouldn't work correctly with tr-TR or fr-CA locales.

An example logged by me here: http://www.smith-consulting.com/Forums/forumid/1/threadid/8863/scope/posts.aspx
In the example above, we need a workaround until a fix is provided by developers. As a workaround, I went ahead and enabled en-CA on site.

Before:
Default locale: fr-CA (en-US as fallback)
Other locales on server: en-US

Now:
Default locale: en-CA (fr-CA as fallback)
Other locales: en-US, fr-CA

The problem is: I only want to setup fallback language for specific module. What happens if i setup my environment like below:
Default locale: fr-CA (en-CA as fallback)
Other locales: en-US,en-CA
To make default locale work, I'll copy resx files of buggy module into en-CA (since it is fallback). So basically if a visitor goes to page where module is placed, DNN will revert back to en-CA for that module and end-user won't notice any difference.

This is just an experiment. I'll post results here. Please add your thoughts if you are interested in finding workarounds for bugs of modules when a developer couldn't provide the fix in required time.

---

Or-Rouge Team Or-Rouge
Personally recommend Hostgator for hosting single or multiple DotNetNuke Websites.
DotNetNuke Tips and Tutorials
Install DotNetNuke to Godaddy root
DotNetNuke Türkçe Hakkinda Hersey