Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
In features_admin_form() some markup is actually injected into the description to add information on conflicts, dependencies and requirements, however the description is later being outputted using check_plain() which escapes the markup and just looks weird. Simple patch on its way.
Comment | File | Size | Author |
---|---|---|---|
#2 | features-escape-markup-1885482-2.patch | 1.86 KB | alexweber |
#1 | features-escape-markup-1885482-1.patch | 1004 bytes | alexweber |
Screen Shot 2013-01-10 at 5.08.42 PM.png | 109.92 KB | alexweber |
Comments
Comment #1
alexweber CreditAttribution: alexweber commentedSince the information comes from a module's .info file its safe to avoid running check_plain() on it IMO.
Comment #2
alexweber CreditAttribution: alexweber commentedAfter looking at the 2.x branch I realised I had missed two more unneeded check_plains() in the string substitutions from l()
Comment #3
hefox CreditAttribution: hefox commentedIs this 1.x only?