please log it at support.dotnetnuke.com (the more detail the better) - the QA team will then review it and can triage it for a release (or mark it as a duplicate if it already exists)

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

It was a duplicate report indeed / extending the use case Sebastiamn commented.

The description I gave is really the bug in its most simple occurrence: clean installation, 1 portal, only host resource files edited, 1 language.Add to that resource files edited by administrator, resource files from other portals and multiply all that for different languages - for each localized ascx file, that leads to a confusing list. I know by now it is the ascx file you must select to edit.  Other DNN users trying to translate static resources will have to learn through trial and error and who knows, how many resource files that DNN will never read will litter the App_LocalResources folders, files like EditHtml.ascx.Portal-0.Host.Portal-1.Host.resx ?

While I am at it, I would like to comment on that resource file selector. The file you select is an ascx file, yet the selector makes you browse until the App_LocalResource folder (the location of the resx files). It would save one step and it would be more logical / intuitive if one were to browse till the folder where the ascx file is located.

I do not want to write this down as a possible improvement because it is my opinion the whole static translation procedure needs to be re-thought and I see my suggestions more as general ideas for improvement that need to be judged against other considerations. Removing App_LocalResources from the folders in the resource selector would only be a very limited improvement,  I can just as well wait for 5.7 or 5.8 or 5.9 whatever when DNN thinks it's time to tackle this part of its UI.

---

____________________________________
The one-eyed in the land of the blind.