We use .bdoc .ddoc and .asice idcard digitally signed document file types
These files will upload no problem, but when you try to download them PHPMaker throws this error:Slim Application Error
A website error has occurred. Sorry for the temporary inconvenience.I have tested, and can confirm that the error occurs only with encrypted file types such as those mentioned.v2020.
have you tried to add the extensions to the DOWNLOAD_ALLOWED_FILE_EXT:“DOWNLOAD_ALLOWED_FILE_EXT” => “extensions_here”, // Allowed file extensions for download (non-image)
the extensions are already there
This was working in v2019, only stopped working in v2020
You may check the network response during download (F12 → Network), also see https://developers.google.com/web/tools/chrome-devtools/network/reference#response.
Couldn’t figure out how to analyse the response data.
Is anyone else able to test this?I also discovered that trying to uplaod these same encrypted file types causes max execution_time_errorsThe problem goes away when i turn off Advanced settings > Encrypt file pathSo, I’m back to my original assumption that the file path encryption causes errors when the file itself is of an encrypted file type.
philmills wrote:
We use .bdoc .ddoc and .asice idcard digitally signed document file typesMake sure your web server can serve those file types.(“Encrypt file path” only encrypt the file path, regardless of the file types.)
of course it can. the problem arose only with upgrade from v2019 to v2020 - webserver hasn’t changed.
I turned off encrypted file path, and the files download and upload no problem. So the problem lies with the file path encryption method and whatever changes to it were made between v2019 and v2020
.bdoc .ddoc and .asice are unknown mime types to PHPMaker, you may try to add mime type by global code, e.g.Config(“MIME_TYPES.bdoc”, “application/vnd.etsi.asic-e+zip”);
…
that doesn’t explain why it worked it v2019, and doesn’t work in v2020
are you using the built in functions for encrypting the field?you may want to contact support, i had a similar issue, field level encryption of a file isn’t supported.
No, the field itself is not encrypted, only the file path