I have an unusual issue with a live portal, the Host Settings and greyed out text boxes.

On my development portal which is on WinXP with SQL2005 everything works perfectly. However on the live server, WinServer2003 with SQL2005, under the Module Definitions when I select a Module the text boxes are greyed out, as if I don't have permission to edit them.

Here is an image of the Host Definitions for the Dev. Server: http://media.indonegal.com/odd1.gif

Here is an image of the Host Definitions for the Live Server: http://media.indonegal.com/odd2.gif

This is what the rendered HTML is for the Liver Server Text Box:

textarea style="width: 390px;" class="NormalTextBox" disabled="disabled" id="dnn_ctr322_EditModuleDefinition_txtDependencies" cols="30" rows="2" name="dnn$ctr322$EditModuleDefinition$txtDependencies"/

On the Dev Server the ' disabled="disabled" ' attribute is not present. Ther Windows File and Folder permssions are much the same with some variance due to the difference between XP and Server2003.

Would anybody have any suggestions as to why this would be different, why it is including the 'disabled' attribute in the Module Definitions and if I have missed something while moving the Dev. Server copy to the Live Server.

I'm not sure why this is happening, does it happen for all modules on the live server?

Have you tried installing a separate fresh installation to the live server - does this version have the same problem?

Lee,

I posted this on Mitchel Sellers and here is the reply I got from him. It would seem that the issue is related to a difference in a Localhost installation compared to a live server installation. It is the same with all modules. I tried different installations on various servers with Windows Server 2000 and 2008 and MSSQL Express and 2005 and its the same each time. I also changed the permissions on the DNN folders with no luck.

http://www.mitchelsellers.com/forum...topic.aspx

Usheen

OK, I read this. I take it that you are trying to alter module settings on the host's Module Definitions page. I am aware that there are several items that can be changed only on a local site. One of them is creating a module package.

I also think that this is easy to fix, by commenting out one line in an aspx file. Basically, that removes the limitation that the function will work only in local environments. I'm travelling this week, but I'll try to look for the solution and post it here.

Joe,

You are correct, I was trying to change the Portable option in the Module Defintions for some of the modules that I have installed on my live server. This issue never arose when I was doing the same thing on my local/development server for the exact same modules.

Usheen

Joe,

Have you been able to look at this issue ?

Usheen

Look in admin\ModuleDefinitions\PrivateAssembly.ascx.vb. There you will see this code:

If Upgrade.Upgrade.UpgradeIndicator(glbAppVersion, Request.IsLocal, Request.IsSecureConnection) = "" Then
lblUpdate.Visible = False
grdDefinitions.Columns(4).HeaderText = ""
End If

I'm assuming that the Requests.IsLocal is the culprit. If I were playing, I would replace that with "True" and see what happens.