If the json file is on your private server, you have to allow the TView web application to access it.
In the browser console (Right mouse + Examine + Console) you will probably see the following error message:
"Cross-Origin Request Blocked: The same-source rule prohibits reading the external resource on https://???.json. (Reason: CORS header 'Access-Control-Allow-Origin' is missing). Status code: 200".
You can allow the files in this directory to be read by web applications, by placing an additional file named ".htaccess" in this directory. This file shall have the following content:
Header always set Access-Control-Allow-Origin: "*"
AddCharset Windows-1252 .json
The first line allows web applications (like TView) to access the files in this directory.
The second line specifies the character encoding for these files: For tournaments with the Tournament Manager use "Windows-1252" and "UTF-8" for tournaments with the Tournament App.
In the browser console (Right mouse + Examine + Console) you will probably see the following error message:
"Cross-Origin Request Blocked: The same-source rule prohibits reading the external resource on https://???.json. (Reason: CORS header 'Access-Control-Allow-Origin' is missing). Status code: 200".
You can allow the files in this directory to be read by web applications, by placing an additional file named ".htaccess" in this directory. This file shall have the following content:
Header always set Access-Control-Allow-Origin: "*"
AddCharset Windows-1252 .json
The first line allows web applications (like TView) to access the files in this directory.
The second line specifies the character encoding for these files: For tournaments with the Tournament Manager use "Windows-1252" and "UTF-8" for tournaments with the Tournament App.