Description of bug

When creating a portal template you can opt to include a resources file to localize content in that template. But it is not compulsory. And if you use the "copy" function in Sites to create a portal template, a resources file will not be created.

When DNN compiles a list of available templates it takes the list of found ".template" files and matches those with the available ".resx" files to see what localizations exist for the template. If none are found then it is assumed the locale is the running portal locale!?! With a reference to issue DNN-6544 in the past.

The end result is that if your main portal is running in let's say "en-US" and you've got a template for a portal in "fr-FR" without a resource file, then it will show up in the PortalTemplate list as "en-US". This is not accurate.

Provide a clear and concise description of the bug.

Steps to reproduce

1. Create DNN instance and include "nl-NL" language
2. Create a portal with just nl-NL as active (and hence default) language
3. Export this new portal from the sites PB module as a template
4. Go back to main en-US portal and now create new portal using this template. Note how it is labeled as en-US not nl-NL.