When creating a story, IE7 pops up a warning with this error. It has been tracked down to wysiwyg.js line 162. The error prevents the editor from showing (the default textarea is shown).

System setup is: Drupal 6.9, Wysiwyg 6.x-0.5, IE7 on Vista and XP

The offending line is
var parts = classes[i].split('-');

When doing this over two lines like this:
var aClass = classes[i];
var parts = aClass.split('-');

the error occurs in the first line (the assignment of classes[i]). Verified by inserting comments above that line and seeing IE7 refer to the assignment line every time (after purging the IE cache).

Error is present in Garland theme. Error is not present if no editor is enabled, but is present as soon as one is selected for the input format used.

To reproduce:
- Install wysiwyg 6.x-0.5 module
- Add one or more editors (e.g. jWysiwyg and TinyMCE)
- Enable an editor for Filtered HTML
- Purge IE7 cache, create a story

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Active » Fixed

Please update to the latest development snapshot.

schetle’s picture

schetle commented

I have a similar issue.

Object doesn't support this property or method in wysiwyg.js line 177

This points to:
if (classes[i].substr(0, 8) == 'wysiwyg-') {

In addition: I get object doesn't support this property or method in tiny_mce.js line 1 char 87055
Pointing to:
if(u.indexOf('/')!=0&&u.indexOf('://')==-1)

Using:
All plugins disabled. Drupal 6.9, Latest Wysiwyg API 2.x-dev Snapshot (released 2/12/09), TinyMCE 3.2.1.1

simenro’s picture

simenro commented
Status: Fixed » Active

The js method is the same in the dev snapshots. Testing them gave the same error in IE7, with these line numbers:

6.x-2.x-dev: line 178
6.x-1.x-dev: line 169

which is the same line as in 6.x-0.5:

var parts = classes[i].split('-');

EDIT: Seems to work on a different site with same setup, with all other contrib modules disabled. Setting this back to fixed.

simenro’s picture

simenro commented
Status: Active » Fixed
sun’s picture

sun
Primary language German
Location Karlsruhe
commented

You might be interested in #359936-11: FAQ. Please DO NOT follow-up over there with support questions, because that's a dedicated issue for frequently asked questions.

simenro’s picture

simenro commented

By enabling modules one by one, I found the culprit to be Chatblock. I added this FAQ entry about this.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

@simenro: Thanks! :)

schetle’s picture

schetle commented

I wanted to note that Chatblock isn't the only thing that causes this issue. In my case, Lootz (an input filter that uses Javascript) was causing it -- even when that filter was not selected for the Wysiwyg Input format.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

@schetle: Please add this info to the FAQ instead, as this issue will be closed soon.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

zcferres’s picture

zcferres commented

This fixed it for me:
http://drupal.org/node/593008