Bug #36718
clickenlarge not working on images inserted by FAL-enabled RTE
| Status: | Resolved | Start date: | 2012-04-30 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Stanislas Rolland | % Done: | 100% |
|
| Category: | rtehtmlarea | |||
| Target version: | - | |||
| TYPO3 Version: | 6.0 | Complexity: | ||
| PHP Version: | 5.3 | |||
| Votes: | 0 |
Description
When an image is inserted in RTE content by FAL-enabled RTE, rendering of clickenlarge fails.
Associated revisions
[BUGFIX] clickenlarge not working on images inserted by FAL-enabled RTE
Solution: Get original file from data-htmlarea-file-uid attribute
Change-Id: I5c4aef33bdcbe7c5badac9173480e33fb627b302
Releases: 6.0
Resolves: #36718
Reviewed-on: http://review.typo3.org/10894
Reviewed-by: Stanislas Rolland
Tested-by: Stanislas Rolland
[BUGFIX] clickenlarge not working on images inserted by FAL-enabled RTE
Solution: Get original file from data-htmlarea-file-uid attribute
Change-Id: I5c4aef33bdcbe7c5badac9173480e33fb627b302
Releases: 6.0
Resolves: #36718
Reviewed-on: http://review.typo3.org/10894
Reviewed-by: Stanislas Rolland
Tested-by: Stanislas Rolland
History
Updated by Gerrit Code Review about 1 year ago
- Status changed from New to Under Review
Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/10894
Updated by Stanislas Rolland about 1 year ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset ff884d02c549df9cdae8996a17f1bd6a674df8ec.
Updated by Stanislas Rolland about 1 year ago
- Subject changed from clickenlarge not working on images inertsed by FAL-enabled RTE to clickenlarge not working on images inserted by FAL-enabled RTE
Updated by Alban Cousinie 10 months ago
The click enlarge bug in the RTE is present in version 4.7.1 and it would be nice to fix it in this version as well, not only in Typo3 6.0
Updated by Ernesto Baschny 10 months ago
Makes no sense, Alban, as there is no FAL in TYPO3 4.7. If you have encountered a bug with it, it's probably something unrelated to this one. Please open up a new issue for it.
Also please consider testing the latest release (4.7.2) before posting a bug report.
Thanks!