Hey all, some of you may have hopped on the JM jWYSIWYG editor band wagon, and i’m hoping it works well for you. The original project is a big slow moving and some global problems seemed to go unfixed (Safari support, toggling issues, etc..). So i decided to see what editor everyone really wanted.

And behold, i give you JM WYM Editor. This is probably the cleanest output code in any WYSIWYG editor i’ve seen yet. It has the ability to use classes in the editor as well (which will soon be tied to CP Settings—for now you’ll have to edit the javascript), so plus factor.

I built this as a Fieldframe extension, so if anyone would really have a standalone, let me know and i can port it back out.

So, commence the support issues!
Note: WYSIWYG Editors work sporadically in FF Matrix fields. I’ll be working to find a solution for the 1.0 release. Until then, use cautiously.

VERSION 0.9 [8/11/09]
Download Now

This sounds great Jack.  Thanks so much. Can’t wait to try it out.

Oh wow! This is just awesome. I’m going to download this immediately!

I forgot to ask: Is this MSM-safe and if so, does it allow different settings per site (like different CSS files for each)?

Hey Jack,

great minds think alike

I’ve been toying with Fieldframe for the last couple days, and have also run into some issues with integrating WYMeditor,

have a look at how i’ve done it here at google code

I reckon its going to need some jquery power to assign new ids to new matrix rows to stop the double editor issue… Too much for my simple brain though…

iso100 - 11 August 2009 09:21 AM

I forgot to ask: Is this MSM-safe and if so, does it allow different settings per site (like different CSS files for each)?

Most likely not, i have to set up my MSM environment again to test to confirm. Definitely not multiple CSS files as currently it would be set my editing the js. Once i wrap that into an extension setting, that should be MSM compatible.

iain - 11 August 2009 09:30 AM

have a look at how i’ve done it here at google code

I reckon its going to need some jquery power to assign new ids to new matrix rows to stop the double editor issue… Too much for my simple brain though…

So you’ve done this already then huh? Interesting. What problem are you having with a double editor issue?

Jack McDade - 11 August 2009 09:42 AM

What problem are you having with a double editor issue?

adding more than one row in to the matrix at a time, without saving after every row…

For some reason I get a WYMeditor in each row, for the number of rows since last save -1… strange one I know….

You don’t get that?

and also when you hit preview, quick save and update does your content get stored?

I had to add

to make it work, though someone said they were getting errors with that, seems to work for me on firefox and safari.

iain - 11 August 2009 09:52 AM

adding more than one row in to the matrix at a time, without saving after every row…
i.

Ah yes, same issue for me. I asked Brandon if there is a function or hook i can tap to fire off the appropriate jQuery. Didn’t get much of a response. As for storing the data—i had the same problem. I actually just went into the WYM javascript and told it to look for .submit instead of .wymupdate. It now works with preview, quick save and update. I don’t like using jQuery to add classes the functionality depends on.. it seems unreliable to me. I might tap into an EE hook and rewrite those submit buttons to include the class, but it’s not completely necessary.

Jack McDade - 11 August 2009 10:04 AM

I don’t like using jQuery to add classes the functionality depends on.. it seems unreliable to me.

Yeah, I thought the method was a bit dirty but hey, its a jQuery editor… Personally I use the publish tweeks extension so probably worth digging around in there for a wee tweek…

I’m still fumbling around with php and EE dev, I’m sure you’ll make the editor sing

You & Iain should work together and really turn this into something!

Seem to work fine in Safari & Ff - I get a funky JS error on the custom field editing page in FF w/ this version, but not w/ Iain’s:

Doesn’t seem to cause a problem, though.

Check the css feature that Iain worked up - nice.

I’ve got the same conflict w/ Primary Category that occurs w/ Iain’s version, essentially.

With yours, it get a JS error on page load:

Primary Cat seems to function okay, but no editor loads.

Does WYM Editor have the ability to include an image/file manager like TinyBrowser?

Probably wouldn’t be hard… but I’ve since abondoned these types of tools in favor of more strict control

I use LG Replace to do it like you’ll see in the screenshot below.

Steps to produce this type of control for any textarea/wysiwyg are on this thread.

Tyssen - 11 August 2009 10:08 PM

Does WYM Editor have the ability to include an image/file manager like TinyBrowser?

Browser, no. You can paste in a url path. I also use the LG Replace method as it lets me get fancier with my image replacement (lightboxes, dyanmic resize, etc..).

Just as a sidenote for anyone using the LG Replace method of adding images/assets into content, I’ve whipped up a FF Celltype that you might be interested in:

http://expressionengine.com/forums/viewthread/126430/

Hey guys, I’m having some problems.

I have 2 custom fields, {main_content} and {main_extended}. I’m using LG Replace, and FF Matrix with my {main_content} and {main_extended} custom fields set to use the JM WYMEditor fieldframe.

Here’s the issue: If {main_extended} is set to use WYMEditor, the whole page crashes and burns quite spectacularly: http://www.easterlydev.com/about/community-involvement/. It does the same if both {main_content} and {main_extended} use WYMEditor. However, if I set the field type of {main_extended} to straight textarea, all is well.

With the help of Kurt Deutscher (thanks Kurt!) we were able to determine that SOMETHING doesn’t like a closing curly brace in the {main_extended} custom field. Whether that something is LG Replace or WYMEditor, I’m not sure. I’ve posted this in both the LG Replace thread and the JM WYMEditor thread in hopes that someone cleverer than me can figure this out.

Not sure if you’re aware of this, but the zip file is incomplete.

2) Copy the language/english/lang.sf_jwysiwyg.php file to your [system directory] language/english directory

That folder, and file does not exist.

there also is no ext file in the extensions folder (based on instructions) to even show an extension exists, so it cannot be enabled.

The attachment shows the contents of the zip file, sorted by type. I highlighted the only php files in the archive

JT’s right in that the readme is incorrect. It looks like the readme for the standalone version of this. However, JT this is the Fieldframe version of the editor, and so all you have to do is upload the jm_wym_editor folder to your fieldtypes folder in extensions and enable it.

Hope that helps.

Edited to add: On a second look, the readme is actually from a completely different extension - namely the jWYSIWYG extension.

well i did do some other stuff. I really wanted to try this WYSIWYG for my contributors as there were things about TinyMCE i didn’t like. I actually did have the fieldframe stuff installed when i tried to get it working, but didn’t realize to put the folder in the fieldtypes. Since it didn’t work I removed it all.

I ended up using the LG tinymce module. but I really do want to try this new one badly.

Maybe i’ll start over and try it again.

The output looks good, but it’s not very easy to customise is it? I don’t just mean the extension, WYMeditor itself doesn’t seem to have a config file; you have to edit the main editor file if you want to add/remove buttons. And I’ve tried to get the WYSIWYG area to pick up the site’s stylesheet by editing the extension file:

but it’s not being applied.

It’d be good if the different settings could be applied via the extension settings:

a) for convenience, and
b) so I can see how it should be done.