I installed the version 3.3.7 to 5.2.0 standard in a small web farm consisting of:
nr 4 server with IIS installed uan instance of DNN on all 4 servers;
nr 1 SQL server
nr 1 NAS that contains the files of Portals

I installed IIS 4 server in a virtual folder called "Portals"that points to the filesystem of theshared NAS.

Everything's fine until I decided to migrate from version 5.2.0 to 5.6.2 because the virtual folder no longer works properly. The virtual folder is no longer viewed by the system that continues to use this folder on each IIS to disqualify my web farm.

I do not know if this problem is a limitation added to the standard version or if it is a mistake, or just if I have to configure any new parameter?


thanks
Dr. Paul. Casadei
DNN Programmer since 2003
Forlì Local Health
Italy

I found the error! I compared the version 5.2.0 and version 5.6.1 and I noticed that in class "FolderController" particularly in the method "GetMappedDirectory" uses a new class method "FileSystemUtils" ie "FileSystemUtils.MapPath" instead the classic "HttpContext.Current.Server.MapPath (.." this means that if I configure in IIS, a virtual folder is not seen by the DNN.
In particular, the absolute address calculated starting from the absolute application of the "DotNetNuke.Common.Globals.ApplicationMapPath"concatenate the folder "HomeDirectory" we all know to be a relative address.
So the error is from this linkage between absolute address and the address on the application of HomeDirectory, which in my case it is virtual does not work.

seen that the problem is in my heart, I ask the development team if this problem will be fixed in future releases

thanks

Paolo
Forlì Local Health