I use config and resource files to define settings for my custom features, as described in the "Using The Installation System" topic of the developer documentation.

This works fine for the feature definitions; settings come in with their correct names and values.

However, when I add a feature to a page, the settings of the instance show the settings values as labels/names, along with the correct values. When the values are edited, the labels will have changed with them the next time the settings editor is openend. This happens both on my local development and the production site.

I immediately thought of unescaped, illegal characters in the XML file, but this happens with completely innocuous values such as integer numbers, and my XML file validates in IE.

Any suggestions why this might happen and how to fix it would be greatly appreciated.

Cheers, Hartmut

A follow up...

I traced this issue in the debugger and found a couple of lines in the AddSettingControl(CustomModuleSetting s, Panel groupPanel) method of ModuleSettings.aspx.cs that are causing this:

settingLabel = GetGlobalResourceObject(resourceFile, s.SettingName).ToString();
label.Text = "<label class='settinglabel' >" + settingLabel + "</label>";

This is assigning the setting value from the resource file rather than the setting name to the label's Text property. I changed it as follows and everything is fine:

label.Text = "<label class='settinglabel' >" + s.SettingName + "</label>";

The only question is: why would this not affect every site? The code quoted above is from 2.3.7.9 (MSSQL). I don't have another site using precisely that version of mojoPortal. Colleagues of mine use other versions and have never run into this issue.

Thanks,
Hartmut

Thanks for looking into this, Joe. I appreciate it.

I'm clearly missing something about regionalization. The resource file being read by the AddSettingControl method is the one I specify in the custom module's config file. That file contains a KeyValuePair resourceKey, resourceValue for each setting, where the resourceKey equals the SettingName. Accordingly, GetGlobalResourceObject(resourceFile, s.SettingName) does not come back as null (I checked in the debugger) but with the resourceValue and assigns that to the label. For example, a setting named "WmsUrl" appears in the resource file under the key "WmsUrl" with the value "http://62.197.41.154:8080/geoserver/SHINE/wms?service=WMS", and this value is what settingLabel = GetGlobalResourceObject(resourceFile, s.SettingName).ToString(); will retrieve from the resource file and assign to the label.

It was my understanding that regionalization was accomplished by having a language-specific resource file for each language, with language specific values, whereas the keys remained the same. That would not allow for translations of setting names. Your response seems to apply that there is yet another resource containing translations for each feature setting name. I am not aware of any such resource, and the AddSettingControl control only seems to read one resource file.

What am I missing?

Thanks again,
Hartmut