|
Note! This Manual is for the "Windows authentication" version, which is designed to work with existing Windows server or Active Directory accounts and Windows authentication. If you want to create accounts by yourself and store their credentials in your own HTTP Commander XML database, you need to download the "Forms authentication" version! This Manual is for the Windows authentication version only! |
 Web file manager Free Installation assistance Manual Home page |
For general update instructions see How can I update my existing installation with latest version without losing config and settings?. This page contains notes about new functions you have to configure, compatibility breaking changes, security issues and other information you should be aware of in upgrading process.
Starting with version 4.6, the new LightGallery
image viewer is used. For it, you need to add a new mimetype to the web.config for fonts with the extension
.woff. For this:
If you used IIS6, see: how to add WOFF font MIME type.
If you used IIS7+, add to Web.config file in <system.webServer> following static content section:
<staticContent>
<remove fileExtension=".woff" />
<mimeMap fileExtension=".woff" mimeType="font/x-woff" />
</staticContent>
Starting from the version 4.5 we implemented support of SQLite database and most of the data from XML files are moved into DB.
Now the list of anonymous links (Links.xml), event log (Log.xml), watching the users,
list of recents, favorites are stored in an SQLite database file (Data\data.db).
After the upgrades procedure, the first time you run the application data are imported from XML files into the database. This procedure is absolutely automated and you should not do anything unless error occured .
In case you can't find your old data after upgrade, please check error details in Error Log at Admin Panel and contact support (do not forget to attach output of diagnostics.aspx page)
Attention! Before upgrade, make sure that you have made a backup copy of the XML files from Data folder.
All settings related to the public links functionality are moved to a new section PublicLinks (from Main and UI sections).
Attention! Before you upgrade, make sure that you have made a backup copy of the file HttpCommanderSettings.config.
In case you can't find your old settings related to Public Links after upgrade, please check error details in Data\debug.log file and send it to support team.
Starting from version 4.5, HTTP Commander support the search using the Windows Search Service (parameter SearchMethodOfFiles). It allow to perform full-text search in files and significantly increase search speed in compare to the build-into HTTP Commander a search method. In order to activate support of Windows Search you need to install and configure Windows Search Service and to add all shared folders to the list of indexed locations. See Windows Search Help for more details.
Dropped support for OAuth v1 authentication and API v1 for Dropbox
If you have configured integration with Dropbox (EnableDownloadToDropbox,
EnableUploadFromDropbox), and used OAuth v1 authentication,
and the value of the DropboxConsumerKey setting is set to default (Element-IT key),
then you need to get your own key and specify the value obtained. To do this, refer to the Integration with Dropbox instructions.
Also in Web.config file between </system.webServer> and </configuration> tags find
Newtonsoft.Json assembly at assemblybinding section of runtime section and if it does not exist, add it
<dependentassembly>
<assemblyidentity name="Newtonsoft.Json" publickeytoken="30ad4fe6b2a6aeed" culture="neutral" />
<bindingredirect oldversion="0.0.0.0-10.0.0.0" newversion="10.0.0.0" />
<dependentassembly>
If exists, replace 0.0.0.0-7.0.0.0 to 0.0.0.0-10.0.0.0 and 7.0.0.0 to 10.0.0.0If you are upgrading from version 2.0.5 (or below) to version 4.5+, in the file HttpCommanderSettings.config replace <UploadEmailNotification> on <EmailNotification> and </UploadEmailNotification> on </EmailNotification>.
<dependentassembly>
<assemblyidentity name="Newtonsoft.Json" publickeytoken="30ad4fe6b2a6aeed" culture="neutral" />
<bindingredirect oldversion="0.0.0.0-10.0.0.0" newversion="10.0.0.0" />
<dependentassembly>
If exists, replace 0.0.0.0-7.0.0.0 to 0.0.0.0-10.0.0.0 and 7.0.0.0 to 10.0.0.0
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-2.6.10.0" newVersion="2.6.10.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Threading.Tasks" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-2.6.10.0" newVersion="2.6.10.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-2.2.29.0" newVersion="2.2.29.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Net.Http.Primitives" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-2.2.29.0" newVersion="2.2.29.0"/>
</dependentAssembly>
<dependentassembly>
<assemblyidentity name="Newtonsoft.Json" publickeytoken="30ad4fe6b2a6aeed" culture="neutral" />
<bindingredirect oldversion="0.0.0.0-10.0.0.0" newversion="10.0.0.0" />
<dependentassembly>
</assemblyBinding>
</runtime>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-2.6.9.0" newVersion="2.6.9.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Threading.Tasks" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-2.6.9.0" newVersion="2.6.9.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-2.2.28.0" newVersion="2.2.28.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Nito.AsyncEx" publicKeyToken="09D695329CA273B7" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-2.1.3.0" newVersion="2.1.3.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Net.Http.Primitives" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-2.2.28.0" newVersion="2.2.28.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
Format of public links changed from version 2.0 .
After upgrade from version 2.x to any newer version, existing public links may not work.
The easiest way to make them work again is to:
Changed the settings to support WebDAV
If you are used to access folders via WebDAV necessarily refer to
Web folders mapping to properly configure.
If You enabled parameter AnonymousEditingOffice, the path to connect WebDAV folder begins with
http://yourdomain/HTCOMNET/hcwebdav/0/ (suffixed '0').
Integration with Box
If you plan to use the integration with Box
(see parameters EnableDownloadToBox,
EnableUploadFromBox),
necessarily verify whether the Update KB2468871 to .NET Framework 4
is installed, and if not, install it on the server with HTTP Commander (update details info: KB2468871).
Also, add to Web.config file between </system.webServer> and </configuration> tags following runtime section:
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-2.6.9.0" newVersion="2.6.9.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Threading.Tasks" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-2.6.9.0" newVersion="2.6.9.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-2.2.27.0" newVersion="2.2.27.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Nito.AsyncEx" publicKeyToken="09D695329CA273B7" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-3.0.0.0" newVersion="3.0.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Net.Http.Primitives" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-2.2.27.0" newVersion="2.2.27.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
New SVG icons
<staticContent>
<remove fileExtension=".svg" />
<mimeMap fileExtension=".svg" mimeType="image/svg+xml" />
</staticContent>
Changed authentication type with Google Drive, Dropbox, OneDrive to OAuth 2.0.
If you used work with Google Drive
(EnableDownloadToGoogle, EnableUploadFromGoogle),
please set value for GoogleClientId parameter.
If you used work with Dropbox
(EnableDownloadToDropbox, EnableUploadFromDropbox),
please set value for DropboxConsumerKey parameter.
If you used work with OneDrive
(EnableDownloadToSkyDrive,
EnableUploadFromSkyDrive,
EnableMsOfficeOnlineEditor),
please set value for LiveConnectAppClientID parameter.
For more info see article Integration with Clouds Storages.
Dropped support for .Net Framework 3.5. Now application requires .Net Framework 4.0 or 4.5.
Email notifications. In HttpCommanderSettings.config file rename UploadEmailNotification section to EmailNotification. See Email notifications settings.
New version slightly changes configuration file format breaking compatibility with older versions. Configuration files from earlier versions of application load to new version without problem, but updated files will not work correctly in legacy HTTP Commander.
Relax NTFS permissions to Data folder. Earlier versions required a number of accounts to have modify permissions to files of Data folder. Now only application pool identity requires modify access. See NTFS permissions for more details.
Enhanced "Force Logout" function — force the browser to forget user credentials of the current user at logout. See How to clear windows authentication on Log out to configure this option. If not configured, web browser will show logon dialog after logout. It is safe to ignore this prompt, however this behavior may be confusing.