MXWest@westwideweb.com

Introduction

I’m using the Fontis-Wysiwyg Extension v1.0.4, and it’s been performing well for our item descriptions. There is a warning on the extension page that “Pages loaded through AJAX calls will not display the WYSIWYG editor” – I took that to mean that the WYSIWYG editor just won’t be used. Maybe I’m wrong? In any case, I’m running into some problems with the editor in my CMS (Home) Page.

Raw

Here’s a snippet of the first few lines of the page, raw:

1
2
3
4
5

<div class="col-left side-col">
<p class="home-callout">
   <a href="{{store url=""}}contacts">
      <img src="{{skin url='images/njSuperStore.gif'}}" border="0" /></a>
</p>

FCKeditor

Using FCKeditor, all images show as “broken”:

Problem Using FCKeditor

When I reveal source, only some of my Magento {{variables}} have survived intact. Examine line 3, and compare to raw example above. The }}contacts"> bit has gone bye-bye, Egon.

1
2
3
4
5

<div class="col-left side-col">
<p class="home-callout">
  <a href="{{store url=">
    <img border="0" alt="" src="{{skin url='images/njSuperStore.gif'}}" /></a>
</p>

TinyMCE

Similarly, TinyMCE also shows images as “broken”:

TinyMCE in Magento CMS

Revealing source reveals a different flavor of mangling; notice that /e/index.php/admin/cms_page/edit/page_id/5// has been prepended to each url.

1
2
3
4
5

<div class="col-left side-col">
<p class="home-callout">
   <a href="/e/index.php/admin/cms_page/edit/page_id/5/{{store url=">
      <img src="/e/index.php/admin/cms_page/edit/page_id/5/{{skin url='images/njSuperStore.gif'}}" border="0" alt="" /></a>
</p>

Summary

I’ve seen this on Magento versions 1.2.0.3, 1.2.1 and 1.2.1.2. I doubt it’s magento-specific, but rather that the editors are parsing a language they don’t really understand. My guess is without the Magento {{variables}} it would be just fine (as it is with item descriptions, etc.).

However, please do take care. Clearly YMMV, but … keep your eyes on the road and your hands upon the wheel.