CiviCRM Community Forums (archive)

would be great if you can investigate and figure out the code changes required to let views know that description is potentially an HTML field. If you do so, please file an issue along with the patch

most of views2 is contributed code, so our ability to debug/fix things is a bit limited

lobo

Looking at the code on that page, it seems that the symbols in the HTML are being escaped.

Is it Civi or Drupal that is converting < and > to &lt; and &gt; and so forth?  I don't know.

It must be views because it looks fine in Civi. http://www.ccdconline.org/drupal/civicrm/event/info?reset=1&id=1

Here's a piece of bad code you can add to a custom view template for a given field (ex. views-view-field--viewname--fieldname.tpl.php).


<?php
$output=str_replace('&lt;/', '</', $output);
?>
<?php
$output=str_replace('&lt;', '<', $output);
?>
<?php
$output=str_replace('&gt;', '>', $output);
?>
<?php
$output=str_replace('&nbsp;', ' ', $output);
?>
<?php
$output=str_replace('&quot;', '"', $output);
?>
<?php
print $output;
 ?>


If you go down this path, be careful of the order and it might be best that you only create a custom template for individual fields, not for the whole view.

I know there has to be a better solution; this will make the view 'work', but it's a total hack. Could someone create a decent array from my mess?