Page 1 of 1

Cannot open archived files

Posted: 2019-12-29, 09:04 UTC
by 0v3rl0rd
Greetings all

I've been using Total Commander for years now, and all has been working perfectly.
But lately I've started to encounter some problems.
Whenever I try to open a file from a ZIP archive I get an error.
For example: I'm trying to open a TXT file (from a ZIP archive) with HTML viewer (Unpack+Open with).
And I get the following error:

Code: Select all

Webpage not available 
The webpage at 
file:///storage/emulated/0/.TotalCommander/temp/test.txt
could not be loaded becase: 
net::ERR_ACCESS_DENIED 
If I try to open the same file with any other archive programs it works normally.

Any help about this error?

Re: Cannot open archived files

Posted: 2019-12-29, 09:09 UTC
by ghisler(Author)
It means that the HTML viewer doesn't support file: URLs any more, only content: URLs.
Try creating an internal association in Total Commander with the option "content: url" checked.

Re: Cannot open archived files

Posted: 2019-12-29, 12:00 UTC
by 0v3rl0rd
As You suggested, I added a internal file association but the problem is still here.

When I try to open the same txt file (already extracted) - it opens normally.

I encounter the problem only when opening from archive :/
The archive itself is working well (I tried packing it again a few times, & with TC's internal archiver also).

Re: Cannot open archived files

Posted: 2019-12-30, 17:45 UTC
by ghisler(Author)
Do you get the same error with file: url?

Re: Cannot open archived files

Posted: 2019-12-30, 23:43 UTC
by 0v3rl0rd
I don't think I understand what You mean by "file: url"?

When I create internal association the only option available is the "content: url" checkbox...

Re: Cannot open archived files

Posted: 2019-12-31, 10:16 UTC
by ghisler(Author)
Yes, when you check this, TC will send the file to the called app as a content: url. If unchecked, it will send a file: url.
A file url points directly to the file system, e.g. file:///storage/emulated/0/subdir/file.txt
A content url points to a content provider where the caller (Total Commander) provides the data. Example:
content://com.ghisler.files/storage/emulated/0/subdir/file.txt

The difference is that with a file url, the called app needs to have access to the file system. With the second url, Total Commander provides the file contents to the app.