-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add support for Base Folder #7
Comments
This is now available in version 1.5.0. |
@thomasvantuycom, thank you so much! 👍 It seems like there's just a tiny error in
With this change, everything seems to work fine. I can preview, edit, delete and fetch any asset. 😃 |
Hi Valerie, I overlooked parsing the environment variable, but in a different location than you indicated. I'm unsure why your suggested fix is effective. The correction should involve modifying line 30 in $publicId = Craft::parseEnv($fs->baseFolder) . '/' . $publicId; Can you verify if it functions as expected and assure me that I'm hallucinating? |
Hi @thomasvantuycom , you're right I had changed it in both places for everything to function as expected! I just forgot about this one, oops. It definitely has to be parsed in the I'm just not sure why we wouldn't want to parse it in the query of the |
We do parse it there, only a couple more lines down. |
Oh I see! I thought that was the place I had changed it. So basically, it is just missing in the |
I still have one minor problem with the generated URL for the transformation to work.
In our Cloudinary setup, we do use the fixed folders structure. We have base folders for every environments we are using. I know there's a way for the Upload API to specify a
folder
name in the upload options, but I don't see any for the transformation.Could I suggest some more enhancements to the plugin to support base folder? I've modified the code on my side to make it work. Here's what I suggest:
CloudinaryFs
classgetTransformUrl
function, prepend thepublicId
with this base folder valueLet me know what you think!
Originally posted by @valboivin in #5 (comment)
The text was updated successfully, but these errors were encountered: