Magento

and how add the editor in the product pages (description)

ot is there a possibility for adding the hrnl codes directly in the content ?

Good morning,

I have tried all the changes in the thread but I do not get the WISSY. I have version Magento ver. 0.8.16100
I agree that having a WISSY on the CMS as well as the Product pages will be an excellent feature for my clients.

Thank you for the great work and excellent product,

FireSpire

firespire,

Try this:
1) Go to http://www.magentocommerce.com/boards/viewthread/420/#t4973 and follow what Moshe says.
2) See this post: http://www.magentocommerce.com/boards/viewthread/420/#t13492
The code that worked for me at line 52 is the following:

Good luck!
Zee

fzolee11 - 01 March 2008 08:17 PM

firespire,

Try this:
1) Go to http://www.magentocommerce.com/boards/viewthread/420/#t4973 and follow what Moshe says.
2) See this post: http://www.magentocommerce.com/boards/viewthread/420/#t13492
The code that worked for me at line 52 is the following:

<script language="javascript" type="text/javascript" src="/js/tiny_mce/tiny_mce.js"></script>

Good luck!
Zee

Thanks, the above works for me.

Has anyone tried the edit html button in the advanced wysiwyg editor? I tired, and I am only getting an empty window popup in firefox. It also appears that the {$lang_theme_code_title} and {$lang_theme_code_wordwrap} variables are not defined as well on this page. However, the page is only static html with some javascript, no php, so perhaps the variables weren’t set properly upon installation?

Any suggestions? I tied added the fq path to the javascript references just to see if it wasn’t picking up the scripts, but that doesn’t appear to be it.

Thanks

+1 for : and how add the editor in the product pages (description)

iblastoff - 16 February 2008 10:49 PM

this is for the latest version of magento (0.8.16100)

since the backend now incorporates /index.php as part of the url (presumably because a lot of ppl were having url issues), it also screws up the url for tiny_mce.js (now it reads as http://www.yoursite.com/index.php/js/tiny_mce/tiny_mce.js which is wrong)

open up /lib/Varien/Data/Form/Element/Editor.php and at around line 52, where it has the following:

<script language="javascript" type="text/javascript" src="'.$this->getForm()->getBaseUrl().'js/tiny_mce/tiny_mce.js"></script>

just change it to the path of your magento installation. for example this works for me:

<script language="javascript" type="text/javascript" src="/'js/tiny_mce/tiny_mce.js"></script>

then do the change moshe mentions in his post above and now you have tiny_mce for your cms pages (personally i don’t see how this is useful here but meh)

Did you set your base link ?

Unfortunately the instructions from Moshe and iblastoff don’t work with the latest version of Magento (0.8.17240). /lib/Varien/Data/Form/Element/Editor.php has the tinyMCE.init function commented out.  Uncommenting it results in a tinyMCE toolbar but no edit frame (as seen in the attached jpg). 

I’m working on it, but I’ve only just started exploring Magento properly after abandoning ZenCart for an coming project.

Click thumbnail to see full-size image

austinstorm - 11 September 2007 06:51 AM

An option to turn it off, once it exists, would also be appreciated.

+1

Yeah, I’ve got to the empty wysiwyg. And, there appears to be a js error related to it, “this.getDoc() is null”

I’ll be taking a look at it in more detail tomorrow.

You may also find this helpful:

How to use FCKeditor with Magento

I made a Wiki page for this topic located at:

WYSIWYG: A How-to.

It should be enough to get you started. Please feel free to add to the article.

Insert this code into the pages containing the textarea elements you wish to attach the WYSIWYG to

For products, add the code around line 54 of app/design/adminhtml/defaut/default/template/catalog/product/edit.phtml.

For the CMS add the code at around line 52 of lib/Varien/Data/Form/Element/Editor.php, inside the $html variable and after the the <textarea>.

actually,
I placed this block in the file ‘app/design/adminhtml/default/default/template/page/footer.phtml’
(at first I put it into the ‘head.phtml’ but then I thought putting it in the footer would make more sense sine the content would be in the textareas by that point, but perhaps I’m confused as to when JS actions are triggered. its probably moot as to head or footer.)

notice the ‘elements’:

anyways, I got this to work, the textareas are affected, however the contents of the textarea aren’t showing, and I get a js error saying

any clue as to why the JS wouldn’t see the textarea content object?

edit:  I get the same JS error when I do it the way you described. As in, the textarea affected but no content shows, just grey box like attachment

Click thumbnail to see full-size image