Am I just going to have to add in my own JS to remove/prevent the -tmp from being added?
Hi @ballzerker! I just tried recreating this set up, and I can see the same thing as you. I’ve never tried this before and I don’t know an immediate fix off the top. The behavior comes from the underlying fancybox lightbox script. Even if I correct the id of the first modal, I find the second link also doesn’t work.
So I’d need some time to troubleshoot the issue. I may not get to it this week.
As a side note, I also tried using the Pro Lightbox in this situation (it is based on Fancybox V5, which is much newer), and it does not have this problem. The first lightbox opens, then the second lightbox opens. When you close the second lightbox, the first lightbox is still there/open and needs to be closed separately. I assume the reason it works is that any logic that fancybox runs during close is being properly executed (vs the free version of the lightbox in your original example, where you never actually close the first lightbox). In any case, if the pro sequence above works for you, that’s also a solution.
Update: Here is a quick demo of how it works with the Pro Lightbox: https://firelightwp.com/modal-within-modal/
-
This reply was modified 9 months, 2 weeks ago by
FirelightWP.
Thanks a bunch, honestly good to know it isnt something theme or custom js related causing an issue. Will try and push for the group to get the pro plugin if we cant figure out a solution with the current version.
Thanks for the help and have a great day,
Daniel