MetlignFire .. Good Job indeed .. and many thanks.
Clickable smiles and all the buttons now work .

Im going to try to make it hide the php-code buttnons if the browser supports htmlArea...

I think a simple javascript with a if-statement would fix it...
but im not a master of javascripts =) i just know programming in general ;)

Meltingfire .. now that would be an excellent idea.

I have disabled the buttons and i am currently using a pop-window with pulldown menu instead of the buttons.
if you wanna see that get the attached 2 files : (overwrite your editor.js and upload select_phrase.html

i love this product .. i am using it with my VBulletin, guest book, PhpNuke and other places where i use an online editor.

Cool.... I bet my members are gonna love this one.. :banana:

This looks great. Sorry to resurrect an old thread, but this is exactly what we've been searching for. I'm going to attempt over the next few days to write a function that will allow this to work without enabling HTML which is a major security risk.

It should be fairly simple to accomplish by simply converting the output with a few replacements (<B> to [B], <a href= to [url=, etc...)

I'll post an update as we examine the feasibilty of this. I especially like that they've developed a version compatible with mozilla on all platforms (not just windows).

There is a hack out that does this already without needing to enable HTML. Search for it.

Hi Erwin,

Thanks for the tip. We've been aware of eiSecure's hack for quite some time, however did not like it's heavy reliance on javascript, which it uses to convert the html to bbcode.

Thanks,
Paul

I have this installed according to the instructions here and I can't seem to get it to show up. The example file works great, just not in the message areas. Any ideas what I might have missed?

Make sure you put the javascript that calls the editor BELOW the textarea code. That one got me for a while. :)

I'm still working on this and have gotten basic functionality to work. Right now I'm trying to figure out the best way to get the info into the database. I was leaning towards a solution that didn't modify the php files themselves, since this hack will automatically turn itself off if the browser is incapable of displaying the wysiwyg editor.

It's converting from bbcode to html in editpost that's going to be tricky (and seems to be one of the big issues with eiSecure's hack).

I did have it below the textarea code. I had the javascript right after </textarea> but could still not get it to show. I'm sure I missed something somewhere.