-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Image url broken when I integrate with strapi-provider-upload-google-cloud-storage #72
Comments
@ahsetiaki Hi, |
@nshenderov unfortunately that url is needed if you deploy Strapi on remote server so Strapi will be able to locate API url. |
@ahsetiaki Yeah, I missed it, that is a problem. We need a fix for that. For now, it always adds this prefix from server.js if it exists. I use strapi with docker and traefik so haven't faced this issue. I'm tired of it, they change their API like every month, previously it worked through baseurl in api.js. |
I've opened a PR #78 to fix this issue as it is also present when @provider-upload-aws-s3 is configured. |
@ovieokeh thank you very much for your PR! I hope it can be released soon because my project is still on progress haha cc @nshenderov |
Hi @nshenderov, first of all, thanks for the great work.
I create a Strapi app, deploy it into Google Cloud Run and store the images/media to Google Cloud Storage by integrating @strapi-community/strapi-provider-upload-google-cloud-storage plugin.
For image that I uploaded into image field, I got no problem. But when I upload image inside CKEditor, the image failed to be rendered
I tried to save it and when I check the url on get detail response. I got different url
I am aware this is because:
url
field on/config/server.ts
to generate image url/uploads/cat.jpeg
intohttps://storage.googleapis.com/{redacted bucket}/cat.jpeg
How I can remove the prefix
url
from generated url so I can use only the url that generated by @strapi-community/strapi-provider-upload-google-cloud-storage?Thanks in advance for your response!
The text was updated successfully, but these errors were encountered: