CDATA content should not be HTML encoded

Created on 9 February 2015, about 10 years ago
Updated 14 November 2023, over 1 year ago

Problem: If you have a node title with "Star Trek & Star Wars" then the content in the XML export will be <title><![CDATA[Star Trek &amp; Star Wars]]></title>. That's because the Views field display will run check_plain() on the title. But for CDATA wrappings that is not necessary, so it should be just <title><![CDATA[Star Trek & Star Wars]]></title>.

Proposed solution: run html_entity_decode() on the CDATA content.

πŸ› Bug report
Status

Needs review

Version

3.0

Component

Code

Created by

πŸ‡¦πŸ‡ΉAustria klausi πŸ‡¦πŸ‡Ή Vienna

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Open in Jenkins β†’ Open on Drupal.org β†’
    Core: 7.x + Environment: PHP 5.6 & MySQL 5.5
    last update over 1 year ago
    22 pass
  • πŸ‡ΊπŸ‡¦Ukraine tibezh

    I think the patch should support PHP 8.1. The $content can be NULL and we can get a PHP deprecation error.

  • Status changed to Closed: won't fix 4 months ago
  • πŸ‡¬πŸ‡§United Kingdom steven jones

    Sorry for the lack of attention to your issue, please accept my apologies.

    Drupal 7 is going to be end-of-life'd by the community in approximately 1 month. β†’

    As such, I am closing all non-critical looking, non-PHP compatibility issues for Views Data Export to tidy up the issue queues and reduce the noise. You can read about this on #3492246: Close down Drupal 7 issues.

    If you feel like this issue has been closed by mistake, please do comment about re-opening it.
    If you feel like the ticket is still relevant for the 8.x-1.x version of the module, then please search for a duplicate issue first, and if there really isn't one (and you've looked properly) then change the version on the ticket and re-open.

    Thanks to everyone involved in this issue: for reporting it, and moving it along, it is truly appreciated.
    The Drupal community wouldn't be what it is today without your involvement and effort, so I'm sorry that we couldn't get this issue resolved. Hopefully we'll work together in a future issue though, and get that one resolved :)

Production build 0.71.5 2024