[19.0][IMP] fs_attachments: fix parsing of stored filenames when storing locally#638
[19.0][IMP] fs_attachments: fix parsing of stored filenames when storing locally#638CRogos wants to merge 1 commit into
Conversation
|
Hi @lmignon, |
40d07a9 to
e71df9a
Compare
e71df9a to
9083b3f
Compare
|
@CRogos Can you explain your use case? I can't imagine the context in which you're encountering this problem. How can I reproduce your issue? |
|
The error occurred when trying to post an expense in our staging system. Because we don't want that any attachment of the production system is deleted by accident from the staging server, we replace the read/write credentials with with readonly credentials by an neutralize.sql script. We also deactivate that new attachments are uploaded to the cloud storage from the staging system, by removing all models from the fs.storage setting. Instead they are stored the usual odoo.sh way on the server. All attachments which were copied from the production system are still accessible by the readonly connection. So the error occurs when the module is installed, but the new attachment is not stored in the cloud instead on the native story. |
Solves this error when new attachments should be stored locally: