Forum


HomeHomePremiumPremiumDevelopmentDevelopmentMissing Localization KeyMissing Localization Key
Previous
 
Next
New Post
12/9/2013 8:07 AM
 

I have asked Scott for his input Andy.

Aderson

 
New Post
12/9/2013 8:45 AM
 

Andy,

The exception appears to be coming from DotNetNuke.Services.Localization.Localization.LocalizeControlTitle()?

That method in the core looks at the Title you put for the module when adding it to the page.  If that is empty, it attempts to get it from the module control's resx file with key "ControlTitle"_[controlKey (toLower)].Text.  I think it needs a control title for Search Results and other things.

First re-check the path of your resx file.  If that's good, then see what the control key is set for the module control.  For simplicity, I like to make the control key the same as the control file name.  So if my control is named "EnterInfo.ascx", I would make the key "enterinfo".  Go to Host > Extensions, edit the module, select the module definition, edit the controls and make sure the key is "enterinfo".  Hopefully that will get rid of this error.

 
New Post
12/9/2013 9:14 AM
 

Scott,

Thanks for taking a look at this for me.  Your comments got me looking at the right location.  I am not using the default folder structure for views because I am creating multiple modules within a single package.  To manage the files I created a "Views" folder and create a sub-folder for each module to hold the views.  Since the location of the view is not the root, the project wants the resource file to be put in an App_LocalResources folder at the same level as the view.  I moved the App_LocalResources folder into the folder that contains the view for the module and everything lined up.

Thanks again,

Andy

 
Previous
 
Next
HomeHomePremiumPremiumDevelopmentDevelopmentMissing Localization KeyMissing Localization Key



Try FREE
30 days money back guaranteed