-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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 Preview is not working for Media #9993
Comments
Please add a reproduction in order for us to be able to investigate. Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided. Why was this issue marked with the
|
@vaibhav0524, where are you deploying to? I'm having a similar issue (#9880) when deploying to CloudFront, using S3 storage for Media. I wonder if this might also apply to other deployment environments. It's working on |
Hey @lc-51, we are using Azure Blob storage to store the Medias. I'm also facing same issue, Media is visible properly in the list view in collection but while editing or uploading new media in the edit view it's thumbnail is not working. |
Hey @vaibhav0524 I've created a new issue with a reproducer in #10139 . Edit: @PatrikKozak didn't see you were assigned already. Well… can't have too many reproducers, right? :D |
Describe the Bug
I have a Media collection in that Image Preview is not working after we upload the image. We are using blob storage, once we upload the image then url is generated but at the end of the url string ?date-time is appended. I saw in the API tab, our thumbnail url is also correct but in the img src url somehow due to ?date-time appended string img is not visible.
You can see the img url in the dev tools, due to that highlighted green one. Image Preview is not working.
How that ?date-time is appending in the src url is the issue. Please have a look to it.
Link to the code that reproduces this issue
NA
Reproduction Steps
Which area(s) are affected? (Select all that apply)
area: ui
Environment Info
The text was updated successfully, but these errors were encountered: