- Issue created by @thomas.frobieter
Tested my theory with a Paragraphs Layout + .photoswipe-gallery class and two image Paragraphs, one with PSWP link, on without. No problem.
So we need to debug the JS to figure out what's accidentally added to the gallery.
- 🇩🇪Germany Anybody Porta Westfalica
Sounds a bit like an AJAX context issue and multi-initialization. Like the once() doesn't work correctly. That would explain why there are four as admin. Each AJAX requests adds another one.
@Grevil could you check that via JS Debugging in the browser in the project @thomas.frobieter mentioned?
- Assigned to Grevil
- 🇩🇪Germany Anybody Porta Westfalica
PS @thomas.frobieter that would also explain why it doesn't happen in your test. Try something like AJAX filtering and I think the same will happen. For admins the administration menu might cause this.
Yes, that was my suspicion too, I had already talked to Grevil about it.
- 🇩🇪Germany Anybody Porta Westfalica
@thomas.frobieter just found another case logged out on the GS frontpage. I don't think there's AJAX running, but we can simply check that by logging the context calls.
Let's increase the priority.
- Assigned to Anybody
- 🇩🇪Germany Anybody Porta Westfalica
Found it! The reasons are additional (non PS-intended) links in photoswipe-galeries, that should not be photoswipe links, but are handled as such.
We're using class "
photoswipe
" on all links that should open a photoswipe layer but forgot to use it in the initialization. Due to how PS5 works.Without this fix
- All inks in a photoswipe-gallery are triggering photoswipe
- For each of this wrong link a broken photoswipe modal slide exists with "The image could not be loaded." message
I'll prepare a fix!
- 🇩🇪Germany Anybody Porta Westfalica
I also created an issue over at photoswipe: https://github.com/dimsemenov/PhotoSwipe/issues/2064
- last update
over 1 year ago 21 pass - @anybody opened merge request.
- last update
over 1 year ago 21 pass - Assigned to thomas.frobieter
- Status changed to Needs review
over 1 year ago 7:52am 15 September 2023 - Status changed to RTBC
over 1 year ago 8:16am 15 September 2023 - Status changed to Fixed
over 1 year ago 8:29am 15 September 2023 - Issue was unassigned.
Automatically closed - issue fixed for 2 weeks with no activity.