WYMEditor for EE2

Aaah glad to see I’m not the only one!

Yes, it breaks the admin area js as well.

I’ve attached a screenshot of what it’s doing.

I also installed Firebug Lite into Chrome, to see what it’s doing there, but when Firebug is on, it doesn’t generate the errors! 😊 It just shows a standard textarea….

Hope we can get it sorted out!

Cheers, Jacob

There really isn’t a way to fix this without moving the JS files out of the third_party folder, and into a web-accessible one, like themes.

I’m working on adding a pretty cool feature to it right now, and I’ll also add some support for moving the JS directory. I’m thinking of adding a config variable to define the path to the JS files, and if it’s set it’ll look at the defined path, otherwise it’ll look in the main third_party folder. This should let you put the files somewhere like: themes/third_party/wymeditor/javascript/, then it should load properly. This is a pretty crappy solution because it defeats the purpose of having a single third_party folder with add-on packages, but it’s the best work around I can think of for now unless EllisLabs adds some more flexibility to the location of the third_party folder (I put in a feature request for this).

For now, you’ll have to hack the file yourself and change the path to the JS files, or wait until I release the next version.

Litzinger, I’m creating a fieldtype for markItUp! and had a look at your code to use it as a starting point - and found a bug 😊

In the function display_settings() you use $prefix = “textarea” … I think you need to specify something unique here (for example “wymeditor”) .. or else EE will output duplicate form fields with the same name (one for EE’s standard textarea and one for wymeditor which also uses “textarea” as prefix) .. this will result in settings not being saved.

Ah, OK. Yeah, this is part of the learning experience for the new API. Thanks!

On a side note, is anyone else using FF 3.6, and noticing that the cursor disappears sometimes when focused on a WYSIWYM/WYMeditor field?

This suddenly started happening for me when updating to 3.6, and it doesn’t happen in any other browser… just seems to be a FF/iframe issue?

Ok, it appears to be a known issue: http://trac.wymeditor.org/trac/ticket/201

Ah, OK. Yeah, this is part of the learning experience for the new API. Thanks!

thanks yourself for putting this one out there 😊 .. the docs are pretty scarce some places atm, so anything we can do to help eachother out is a good thing.

I set up my client’s site in EE 2.0. Populated it with content. Everything was fine. Now entries to the “blog” channel won’t submit. The publish form just seems to reload. Other channels work.

I suspect the problem was WYMEditor because the Blog channel was the only channel that was assigned that fieldtype. I’ve removed all addons anyway but still nothing.

I do have rights to post there, I am a super admin.

Help?!

We find WYMEditor dosen’t work when we edit another site with Multi-Site Manager because $system_path and EE are in different domains. Now we force $system_path to EE with hardcoding in order to make it work. But we think there should be a better way to resolve this problem.

I’ve never actually tested it with a multi-site setup… I can look into this though.

@Mike Mella, are you still having problems with it? I’ve made some updates since the first version and haven’t had any reports like yours.

Sorry I forgot to update this post…

My problem was related to the native EE publish form and editing the tabs therein. it’s a known bug. It’s resolved and had nothing to do with this add-on.

Ah, good to hear. Thanks for the info.

@Mike Mella, in the latest version I added 2 hidden config variables to define the path to the JavaScript files so you can move them to a different location. It was intended to allow the editor to work if your entire system folder is below the web root, but it may help with your specific problem too.

I’m somewhat new to expression engine. I was able to install the add-on according to previous posts in this topic, but I’m getting a php error when I try to edit or create a page in the channel with the assigned field type. This is the error I’m getting:

Parse error: syntax error, unexpected T_STATIC, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /path to expression engine/admin/expressionengine/third_party/wymeditor/libraries/pages_nested_menu.php on line 25

I didn’t want to mess with the code. Any thoughts?

That class was written with PHP 5 specific code… I’m betting you’re on a PHP 4 server?