-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Volumes with private filesystem don't appear in "Available Volumes" field setting #256
Comments
I will say that by default, Vizy will require volumes (and their filesystem) to have publicly accessible files in order to work. I see from your context explanation your unique way of handling your requirements. I'll need to look at how we can address this. |
@engram-design great, thanks! I'd like to add that the use-case described above has been a requirement for more than one of my company's projects already, so it'd be great if Vizy ends up handling this somehow. Let me know if I can help in any way :) ! |
Describe the bug
When setting up a Local Folder pointing to a path outside the public web folder (e.g.
storage/private-files
in the example folder structure below), it does not appear in Vizy fields’ "Advanced Settings > Available Volumes" setting. Surprisingly, it does appear as an option in the "Default Upload Location" setting, so Vizy does find the volume.Example Folder Structure:
Steps to reproduce
storage/private-files
andweb/public-files
directories from the example folder structure abovestorage/private-files
web/public-files
Craft CMS version
Craft Pro 4.4.17
Plugin version
2.1.9
Multi-site?
Yes
Additional context
The reason we need a "Private Assets" volume with a private filesystem is to allow content editors to upload images which are not publicly available until they are effectively used by the front-end. To make this work, we select the "Public Files" filesystem in the volume's "Transform Filesystem" setting, and the images become public when a transform is applied by the front-end code.
I tried switching the "Transform Filesystem" setting from "Public Files" to "Private Files" and that does not influence the issue described here. I did upload an image to the "Private Assets" Volume and confirm that Craft can read and write in the underlying
storage/private-files
directory.I have Craft's "allowAdminChanges" setting turned off, so I only tested this in local development environment:
The text was updated successfully, but these errors were encountered: