Okay, we loaded the patch for Tiny MCE. Had to make our own changes to it, and it worked for awhile in all browsers. However, now it doesn't work in IE.

Anyone have any ideas?

Matt Bittner
Software Engineer
Internet Modeler

Re: [mbittner] TCME WYSIWYG Editor Problem

Hi Matt

Could you give me a bit more detail about what's happening here? Maybe some screenshots, maybe a copy of any error messages you are getting.

Ross Fairbairn - Consulting

Hire me! Save time by getting our experts to help with your project.
Template changes, advanced features, full integration, whatever you
need. Whether you need one hour or fifty, get it done fast with
Priority Consulting: http://www.interactivetools.com/consulting/

Re: [ross] TCME WYSIWYG Editor Problem

In Firefox, the editor - TCME - shows up for both the summery and content sections where it's supposed to.

In IE, however, TCME does not show up. First attachment is how article editor looks in Firefox (ff_am.jpg) and the second in IE (ie_am.jpg).
Matt Bittner
Software Engineer
Internet Modeler

ff_am.jpg 105K

ie_am.jpg 77K

Re: [mbittner] TCME WYSIWYG Editor Problem

Hi Matt,

Does clearing the cache and refreshing help at all in IE?

And does it make a difference if you are in compatibility mode or not?

And are you getting any script errors in IE?

Let me know and we'll do our best to help.
Dave Edis - Senior Developer

Re: [Dave] TCME WYSIWYG Editor Problem

Refreshing didn't do anything, neither did clearing cache.

Same with compatibility mode. "On" or "off" doesn't matter.

The following error is displayed:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0)
Timestamp: Tue, 13 Oct 2009 00:12:59 UTC

Message: Object expected
Line: 1
Char: 95108
Code: 0
URI: http://www.internetmodeler.com/artman/wysiwyg/tiny_mce.js
Matt Bittner
Software Engineer
Internet Modeler

Re: [mbittner] TCME WYSIWYG Editor Problem

Hmm, everything looks good that I can check remotely.

The next step would be to send in a 2nd level support ticket here: https://www.interactivetools.com/support/email_support.cgi

Add a link to this thread and we'll test it in IE and see if we can resolve it.

Dave Edis - Senior Developer

Re: [mbittner] TCME WYSIWYG Editor Problem

I occasionally get the same problem in IE, the WYSIWYG editor and text field for body copy doesn't appear.

When I look at the source, the textarea is there, but for some strange reason AM set the textarea field to "hidden".

Re: [BillG] TCME WYSIWYG Editor Problem

Update - from looking at the tinyMCE source, it appears that when tinyMCE first loads, it is able set the editor textarea to "hidden".

I'll bet that becaue AM isn't properly integrated with tinyMCE, AM code is incorrectly setting the WYSIWYG to a hidden field. Until Interactive tools patches their patch (and I'm not holding my breath), some of us are going to occasionally see a missing Body field in the editor.

This is what happens when you don't understand your own code.

Re: [BillG] TCME WYSIWYG Editor Problem

Hi there,

That's actually on purpose -- when it's working, it should be set to hidden as well. The Javascript replaces the hidden field with the WYSIWYG editor, as it's not a standard input field. If you look at the unpatched version (ie, in the online demo) you'll see that the Innova editor was the same way, with the input field set to hidden.

That said, I haven't been able to duplicate that problem at all locally with the TinyMCE patch -- can you fill in a support request so I can see exactly what's going on with yours?



Re: [BillG] TCME WYSIWYG Editor Problem

Hi BillG,

>It hides the editor on purpose? Gee, that's reassuring

>Quite honestly, I don't trust you with that information - you'll probably make things worse.

We're happy to help out anyone who is having problems with the wysiwyg, or anything else for that matter. But it sounds like you're more interested in making us wrong than getting anything resolved. If that's the case, and you're just going to argue with everything we say, please don't bother posting here. There's no value in it for either of us.

Or... If you want our help, great, please just stick to the facts and provide us with information so we can help you (the 2nd level support form doesn't require FTP details).
Dave Edis - Senior Developer