HTML entities in the item title are double encoded for feeds using fields

Similar issue in 6.x-1.x #779760: check_plain runs twice on title. A workaround could be hook_views_rss_item_elements_alter(). However this patch fixes it properly.

This patch is correct, the other have wrong pathes.

#3 is basically #2 with -p1 instead of -p6, I'm marking it as RTBC because I think pbusch also tested that patch.

I am experiencing this exact issue, however the patch provided does not solve the problem. I believe this post is on the right track. The one extra thing I have is the rss feed - itunes also enabled.

I have also tried using 7.x-2.x-dev and get the same results.

I'm not sure what to do next.

This patch solved this issue for me. I'm also using view_rss:itunes. I had to flush the cache after applying.

I bumped into this problem where i wanted to remove html tags and html special characters so i wrote a small article
Views Rss html special characters problem

Thanks! That solved the problem for me perfectly.

This is a larger issue that affects more than just node title. The double escape happens for any views field handler that sanitizes it's output - ie node title, term name, text fields, node body, etc.

Below is a short term workaround that I have used until a permanent fix is available:

/**
 * Implements hook_preprocess_views_view_views_rss().
 * - Hack to fix double escaped values when using a Views RSS which is a
 *   views field based output. Ex. node title gets sanitized in views_handler_field_node
 */
function MYMODULE_preprocess_views_view_views_rss(&$vars) {
  if (!empty($vars['rss_feed'])) {
    $vars['rss_feed'] = strtr($vars['rss_feed'], array(
      ''' => ''',
      '"' => '"',
      '<' => '<',
      '>' => '>',
      '&' => '&',
    ));
  }
}

#9 is working for me. Thank you.

Here's another workaround for those who prefer to do this in the theme rather than a custom module. Create a template file for the title field in all views: views-view-field--title.tpl.php:

<?php
 /**
  * This template is used to print a single field in a view. It is not
  * actually used in default Views, as this is registered as a theme
  * function which has better performance. For single overrides, the
  * template is perfectly okay.
  *
  * Variables available:
  * - $view: The view object
  * - $field: The field handler object that can process the input
  * - $row: The raw SQL result that can be used
  * - $output: The processed output that will normally be used.
  *
  * When fetching output from the $row, this construct should be used:
  * $data = $row->{$field->field_alias}
  *
  * The above will guarantee that you'll always get the correct data,
  * regardless of any changes in the aliasing that might happen if
  * the view is modified.
  */
?>
<?php
  $output = htmlspecialchars_decode($output, ENT_QUOTES);
  print $output;
?>

Naturally you could tweak the name of the tpl.php file if you needed it to affect something other than the title, or override a particular view. Refer to Theme: Information in the Advanced fieldset within your view for a list of options.

Brilliant! That worked perfectly and is quite simple. Thank you for posting this solution.

This should be now fixed in the most recent 7.x-2.x-dev version, just pushed to d.o. Please clone from git repo or wait till the dev package is rebuild.

Is there a .patch file that can be used to apply the fix that is listed in comment #13? I did see this link on the referenced site: http://cgit.drupalcode.org/views_rss/patch/?id=5ab174a44775808a35f552b9c... but it's not an actual .patch file I can run with drush or apply with the patch command. Should I just use that to make my own file or am I missing something obvious?

> This should be now fixed in the most recent 7.x-2.x-dev version

I'm using the most recent 7.x-2.x-dev version and I get this issue.