Path to no-poster.jpg and user-profile thumb image 404's when using base path
See original GitHub issueDescribe the bug
Path to no-poster.jpg
, no-poster-person.jpg
and user-profile thumb image 404’s when using base path
To Reproduce* Steps to reproduce the behavior:
- add a base path
- See error
Expected behavior no 404 😛
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: docker
- Browser chrome
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
how to fix 404 warnings for images during karma unit testing
I'm unit testing one of my directives (angularjs) using grunt/karma/phantomjs/jasmine. My ...
Read more >next/image component can't find image when using basePath
Trying to use next/image while setting the basePath property in the next.config.js file, causing the image to break with the following error ...
Read more >How to handle loading of images that may not exist?
Another way to handle this issue is by listening to the error event that gets fired when the image fails to load. In...
Read more >Image404 plugin - ASP.NET Image resizing for IIS
You can create a named path by adding an attribute to the image404 ... We somehow got a different image entirely when using...
Read more >404 when viewing assets - Craft CMS Stack Exchange
Name: Images Handle: images File System Path: {basePath}media/images/ URL: /media/images/. Note that I am using my environment variable in ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was just making sure. You know I love you 😘
Fix coming in next patch, fix referenced in #243