This issue has been brought up for Magento 1.4.0.1.
One of my clients sent me a support email asking why the custom (Text Area type) attribute they created is not rendering the HTML that came from the WYSIWYG enabled for that attribute. Instead, the attribute was showing all it’s HTML undies on the product page.
Upon closer inspection, it transpired that the allow_html_tags_on_frontend flag for that attribute was set to 0 – ie. don’t allow HTML. So what was happening and what can we do to work this issue out?
There are two workarounds for this issue.
Workaround 1
Updating this flag directly in the database table catalog_eav_attribute fixed the issue immediately.
Just find your attribute_id in eav_attributes for the given attribute code and locate it in the above table. Use PHPMyAdmin or similar to update the database manually.
But you can hardly tell your clients to do this every time they add a new text type attribute.
Workaround 2
Going into the attribute edit page, revealed nothing useful:
Default Frontend Properties display
But when we select “No” for “Enable WYSIWYG”, the “Allow HTML-tags on Front-end” drop-down becomes available.
So the second workaround is to save the attribute with the following settings first:
Then, set Enable WYSIWYG to “Yes” and save again.
It seems that even though the hidden Allow HTML tags drop-down has the correct value set, it’s not being saved with the form when just creating a new attribute. Also there seems to be a bug with the drop-down even when Enable WYSIWYG is set to “No” the Allow HTML drop-down isn’t showing immediately, we have to toggle the WYSIWYG drop-down to see it.
Originally published on magebase.com. Copyright © 2010 Magebase - All Rights Reserved.
Proud members of the 
Neat trick…and much appreciated. Is there a similar workaround for v1.3.4.2 without having to edit the db? Evidently WYSIWYG is a new feature.
If not, are the db edits the same as 1.4.0.1?
Thanks!
As you rightly say, the WYSIWYG feature has been introduced in Magento 1.4 so this tutorial is not applicable to Magento 1.3.4.2 since there is no native WYSIWYG support for attribute text fields.
OK, so I tested out workaround #1 and there’s partial victory. I was able to edit the attribute for ‘Product_options’ (is_html_allowed_on_front = 1), but the attribute still shows this ghosted out and NO (after refreshing the cache and rebuilding the indexes).
The descriptions (row Name) for Options now supports HTML, but the Title does not. In fact, it stubbornly just displays the raw HTML.
I’m still not clear what Magento version you are applying this on?
1.3.x supports only the “Allow HTML tags on Frontend” setting. If this is set to Yes, then HTML tags are rendered correctly on the front end. This works for you, by the sound of you comment.
When you say the Title doesn’t render the HTML, do you refer to the title of the attribute? In that case, it won’t work since the title is htmlEscaped in the template code. You could try editing the template/catalog/product/view/attributes.phtml template to adjust this (remove the htmlEscape call) maybe.
Easier to show you…
http://www.besthotwater.com/index.php/3d-hot-water-heater.html
OK, I think this is a different area in Magento. You are looking at custom product options in your case. For this, you might need to look into the following template:
template/catalog/product/view/options/type/select.phtmland remove the $this->htmlEscape() call from $_option->getTitle().
Ooops:
OLD: htmlEscape($_option->getTitle())) ?>
NEW: ($_option->getTitle())) ?>
Result:
Parse error: syntax error, unexpected ‘(‘, expecting T_STRING or T_VARIABLE or ‘{‘ or ‘$’ in
/public_html/app/design/frontend/default/proclean_black/template/catalog/product/view/options/type/select.phtml on line 30
Yes, you need to also remove the enclosing parenteses so you should end up with:
$_option->getTitle()Success (again, partial). Sorry for my code faux pas!
Now we’ve hit a wall in that we can edit custom options titles to include HTML, but, when we try to add HTML via MageWorx Advanced Product Options extension, the title ignores the HTML altogether!
I’ve already placed an urgent support request to Antoine…hopefully he’ll have a quick & easy fix. He’s generally been pretty supportive in the past.
We thought, perhaps, to apply the same edit (remove escapeHTML) to a file within the /public_html/app/design/adminhtml/default/default/template/customoptions/ folder (such as “catalog-product-edit-options.phtml”, but I will let MageWorx give us their thoughts.
I’m glad you had (partial) success. Your further issues, as you say, should be directed toward MageWorx.
Well this post is a little old, but helpful, so thanks.