- Issue created by @Thony
- Status changed to Postponed: needs info
about 2 years ago 4:59pm 2 February 2023 - πΊπΈUnited States cmlara
Drupal\system\FileDownloadController->download() (line 80 of /opt/drupal/web/core/modules/system/src/FileDownloadController.php
This is the Drupal Core provider controller and is not provided by s3fs. Line 80 corresponds to the scenario where no module has granted access to the file or that a module has specifically rejected access.
Normally Core will grant access to the file uploader while it is unsaved however it is possible contrib modules may be overriding that behavior.
Iβm not really sure here of the scenario. Since this is the FileDownloadController path it sounds like we are not discussing image styles (as those go through ImageStyleDownloadController but still subject to core ACLβs).
At the moment this sounds like this may be an issue outside of s3fs, postponing on more information being provided on how to reproduce this.
- Status changed to Active
about 2 years ago 5:22pm 13 February 2023 - πΊπΈUnited States chucksimply
Same issue here... image preview on upload is broken. Saving the node, then re-editing, the preview shows correctly.
All worked fine on 8.x-3.0-rc2. The issue only started after the update to 8.x-3.1
- Status changed to Postponed: needs info
about 2 years ago 8:34pm 13 February 2023 - πΊπΈUnited States cmlara
This issue needs steps to reproduce as it does not appear in my lab when using a standard install profile, an image field with the default thumbnail image style display and the file path set to private:// with s3 takeover.
If you can provide the steps to reproduce from a vanilla standard Drupal with s3fs installed this can be investigated more.
- πΊπΈUnited States chucksimply
Turns out my issue is with the File Field Path module... see the attached issue. This may be the same problem for the issue creator as well.
- Status changed to Closed: cannot reproduce
almost 2 years ago 8:04pm 7 April 2023 - πΊπΈUnited States cmlara
As the OP has not given additional details on being able to narrow this down to s3fs, and an alternative theory has been shown for outside of s3fs, Iβm going to close this as could mo reproduce.
If the OP or another can reproduce this and determine a fault inside of s3fs it may be re-opened.