Bug #37200
Issue when adding multiple colorboxes on the same page
| Status: | Accepted | Start date: | 2012-05-15 | |
|---|---|---|---|---|
| Priority: | Could have | Due date: | ||
| Assignee: | Raphael Zschorsch | % Done: | 0% |
|
| Category: | Frontend | Spent time: | - | |
| Target version: | - | |||
| Branch: | v4 | |||
| Votes: | 0 |
Description
Hi,
I just tried upgrading from 1.4.1 to 1.5.4 and I noticed that 1.5.4 does not correctly handle multiple colorboxes on the same page.
For example, let's say you have a page with 2 separate picture elements, both with colorbox activated. With 1.4.1, when you click on one of the pictures you get a light box with only the picture you clicked on. With 1.5.4, the lightbox contains both pictures (permitting you to jump back and forth between them, that is), even though they're totally unrelated.
The cause of this behaviour seems to be that the rel attribute is missing the element id, meaning all images on the page end up having rel="rzcolorbox", instead of - for example - rel="rzcolorbox[cb1377]", as it used to be in 1.4.1.
Downgrading to 1.4.1 restored the proper behaviour.
TYPO3 version is 4.5.15.
History
Updated by Raphael Zschorsch about 1 year ago
- Category set to Frontend
- Status changed from New to Accepted
- Assignee set to Raphael Zschorsch
- Priority changed from Should have to Could have
- Branch set to v4
This is a known "issue". It's not really an issue, because a lot of people asked if it could be done, that all the images on one page are opened in one lightbox, the "issue" you're referring to. Since the removal of the rel tag, this is possible; unfortunately all the images on one page have the same "rel" tag. You see, that it's really a matter of what you want or don't want :) So I'll look into this to make an option available, to either open all the images on a page in the same lightbox or seperate it for each image content element.
Updated by John Doe 12 months ago
Thanks - if there was an option to switch between both types of behaviour, that would be great :)
Updated by John Doe 9 months ago
Hi,
is there any chance you could point me to the specific commit/diff which changed this behaviour - then I'll try to modify the new version locally, if possible.
Thanks.
Updated by Raphael Zschorsch 7 months ago
Sorry, not much time lately to work on the extension!