Module Setting Name

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
6/10/2009 10:12:41 AM
Gravatar
Total Posts 131

Module Setting Name

If you change the module setting name / label in admin / features / advance, any existing modules keep the old name.

Pretty low priority but thought I would log.

 

6/11/2009 5:47:48 AM
Gravatar
Total Posts 18439

Re: Module Setting Name

Hi David,

I don't consider this a bug, its a feature ;-)

Module setting names are defined by the feature developer in config files and the setup page updates them accordingly so that its possible to change default settings and add new ones by updating the config file. The UI for manually entering that stuff is for developer convenience for those who have not learned to use the installation system and its config files. You should not rename module settings for existing features that you did not develop. The feature relies on those names being what they were defined as by the developer. The labels for the settings are not the same as the settings themselves, the setting name is also the resource key to lookup the label in the resource file so that labels can be localized (but not customized). 

There is no reason for any user to change module setting names other than for the custom features they have developed themselves.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.