Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0DNN 5 - Breaking changes to Profile.ascx.resx pathDNN 5 - Breaking changes to Profile.ascx.resx path
Previous
 
Next
New Post
11/28/2008 8:24 PM
 

In a module settings control I need to populate a DropDownList with the localized names of both standard and custom profile properties and in a GridView in a module edit control need to set a column heading to the localized name of the selected custom profile property. In DNN 4.7 to 4.9, I had this working well by pulling the localized profile property names from the base localization resx file of either:

"admin/Users/App_LocalResources/Profile.ascx.resx" for the standard profile properties or

"admin/Users/App_LocalResources/Profile.ascx.Portal-x.resx" for the custom profile properties of Portal x.

As I was testing this module against DNN 5.0 RC2 I found that the localization was broken with the change to a non-admin only user accounts/user management module. In DNN 5.0, the profile property resx files are located on the path:

"DesktopModules/Admin/Security/App_LocalResources/"

Although I could check DNN major version # and hard-code the paths, I'm reluctant to do so. The other possibility is to obtain the path from the ControlSrc field of one of the user accounts/user account module controls but I find that the ModuleName of the that module has changed from "User Account" in DNN 4.x to "Security" in DNN 5.0 - which unfortunately gets me back to a DNN major version # check again to obtain the ModuleName. I could lookup one of the module controls via the ModuleDefinitionName which is the same (UserAccount) in both DNN versions but a ModuleDefinitionName can be changed by the host.

Any suggestions as how best to handle this change? Am I missing an easier way to obtain this path or otherwise localize the profile property names?


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
11/29/2008 4:53 AM
 

William,

with all respect, supported interfaces are limited and location of files as well as database structure cannot be part of the contract, developers of extensions can rely on. Without having looked into the code for your specific example, there are generally 2 options:

  • rely on core business objects only
  • if this does not fulfil your needs, submit an enhancement request for an additional interface, e.g. a class returning all localized titles.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0DNN 5 - Breaking changes to Profile.ascx.resx pathDNN 5 - Breaking changes to Profile.ascx.resx path


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:

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