The version of WYSIWYG Filter included in Panopoly is one behind the latest. The latest version includes the patch that is present in the panopoly_wysiwyg.make file. It also includes a patch that allows altering of WYSIWYG Filter's blacklist, something we need in order to allow embedding iframes by trusted users. There are a few other updates as well.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | panopoly_wysiwyg-update-wysiwyg-filter-2882771-11.patch | 765 bytes | dsnopek |
Comments
Comment #2
byronveale commentedAnd here's a patch to do so.
Comment #3
byronveale commentedComment #4
byronveale commentedComment #5
byronveale commentedFWIW, we've been using this patch on production for about a month now, no issues…
Comment #6
byronveale commentedFYI, we've been using this on production for about three months now, for approximately 160 sites; don't suppose that counts as "reviewed and tested by the community"?
(Sorry for all the nagging…)
Comment #7
cboyden commentedWYSIWYG filter has had a flurry of updates recently - here's an updated patch and interdiff to get onto the latest RC7.
Comment #8
cboyden commentedSorry, interdiff was empty. See updated file.
Comment #9
cboyden commentedSomewhere in between RC3 and RC7, entities such as >"< started getting encoded in image alt/title text again. There's a test for this in Panopoly's wysiwyg_media.feature, and it's going to fail. Until it's fixed, it's probably best to do the minimal update and go with RC3 for Panopoly.
Comment #10
cboyden commentedSee #2570715: Wrong behaviour if alt or title attribute contains colon - this looks like the update that caused the problem. The commit is http://cgit.drupalcode.org/wysiwyg_filter/commit/?id=ea7aa1f
Comment #11
dsnopekIt looks like #2570715: Wrong behaviour if alt or title attribute contains colon has been reverted and now there's an -rc9. I haven't tested it, but here's a patch so we can test on Travis.
EDIT: Here's a Travis build: https://travis-ci.org/panopoly/panopoly/builds/323070147
Comment #12
bkosborneOK - We've been using the patch from #11 in prod for a few weeks without reports of issue.
Comment #14
dsnopekThanks, Everyone! Committed, finally :-)