[Bug]: Opening an image file shows the wrong file
⚠️ This issue respects the following points: ⚠️
- [x] This is a bug, not a question or a configuration/webserver/proxy issue.
- [x] This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- [x] Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- [x] I agree to follow Nextcloud's Code of Conduct.
Bug description
This is limited to image files. When I try to open an image file to view it, it will load the wrong file or sometimes even show parts of 2 files. This behavior also affects Photos and Talk image previews.
This is happening on c.nc.c. Started after v30 upgrade.
Quick GIF showing 2 images being opened and 2 wrong images shown.
Steps to reproduce
- Try to open/preview an image file (JPG, PNG, etc.).
- When opened, you should see the wrong image from what you opened.
Expected behavior
Opening an image file should show the correct image file.
Nextcloud Server version
30
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 28 to 29)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- [ ] Default user-backend (database)
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
Clear your browser cache and try again.
I tried a clean install (30.0.1) , but images other than the target image are loaded at the same time. I have the same problem with movies as well as images.
@viktorix can you still reproduce the issue?
@miyakejun I still can't reproduce the issue. My first guess would be a conflicting app or plugin that breaks the css 🤔
Can you right click the image, click inspect; search the parent div viewer__content and screenshot the entire devtools like this
I'm really sorry. After reloading (Ctrl+Shift+R) as mentioned in the previous comment, it is now displayed correctly.
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.
Cannot reproduce anymore. The issue is a cache miss on some browsers, please force refresh if you experience this 🤷