eeyui – a YUI rich text editor for Expression Engine
Posted August 27, 2008
on:- In: JavaScript | PHP | web applications
- 9 Comments
Being frustrated with the tinymce plugin for Expression Engine, I decided to create a rich text editor plugin for Expression Engine using the YUI library simple editor.
Due to a magic combination of:
- the awesomeness of the YUI library
- the thoroughness of the YUI documentation
- the simplicity of creating extensions for Expression Engine
it was surprisingly straightforward.
If you’re using Expression Engine and are either sick of fighting with tinymce or aren’t using a rich text editor, you can download it from http://code.google.com/p/ee-yui/.
9 Responses to "eeyui – a YUI rich text editor for Expression Engine"
Actually, my previous comment refers to the full editor, not the simple – not sure if it matters. Thanks!
Thanks for the support paul, but I’m still not able to get this going. I found 3 instances of ‘field_id_2’ and replaced them all.
In editor-loader.js:
ta = document.getElementById(‘my_field’).value = html;
var Editor2 = new YAHOO.widget.SimpleEditor(‘my_field’, myConfig);
Should all of these be changed?
and in broswer.php:
myEditor = window.opener.YAHOO.widget.EditorInfo.getEditorById(‘my_field’);
Great! I’m brand new to EE and need a text editor for my users to update their pages.
I’ve replaced all occurrences of id_field_2 with id_field_5.
When I enter text and then click Submit, I keep seeing the error that “The following field is required: pageText”. pageText is the name of id_field_5. Any ideas there?
Jeremy
Alas, I had already changed that one.
Jeremy
1 | Shana
December 12, 2008 at 1:45 pm
Hi!
I’m really excited about this extension. I just installed it. I am having a problem which is that when I click on the images button, i get a window that just says “index.html” – it looks like there is some directory that the button is trying to access that has an index.html but shouldn’t. Do you know what this is? I’d really like to use yui editor in ee, and this seems like the way to do it. Thanks for writing the extension!