Due to security restrictions, launching the WebModel from the local file system or from a file server (address starts with file://) is no longer allowed by most browsers. To work around this behavior, the WebModel must be stored on a web server and be accessed via an HTTP(s) link*.
There is the possibility to allow the WebModel to be accessed from the local file system or a file server, but the respective browser must either be started with additional parameters or configured later.
The following browsers can call the WebModel from the local file system or from a file server, assuming you configure them afterwards:
- Firefox (from version 68.0) > How to access the local WebModel with Firefox (version 68.0 or higher) (KB10393)
These browsers currently only allow the WebModel to be called via a web server:
- Opera
- Safari
- Edge (Chromium Basis)
- Google Chrome
The following browsers allow the WebModel to be called from the local file system or from a file server as standard:
- Internet Explorer Version 10 or higher (you may have to allow "blocked content")
*Note: If the WebModel is stored on a web server and the linked files are still stored on a file server, it is possible that the linked files on the file server cannot be accessed via the WebModel.
This is because there is a zone change (web server = Internet zone; file server = local intranet/computer). There are two ways to avoid this behavior.
Option 1:
When exporting the WebModel you choose the option "copy linked files into the target folder". This ensures that all linked files are copied to a folder in the WebModel directory and the files are then also located on the web server.
The only disadvantage of this procedure is that you will have to perform a new WebModel export as soon as the file is updated.
Option 2:
Also store the documents on a web server, for example in a Document Management System (DMS).