Since the latest versions of OpenWYSIWYG, I cannot get it to work with IE. When I try to create a new page or edit a page, I do not get any Icons - I get this error on page "Line 418 - Error: Expected ";" and "Line 41 - Error: 'WYSIWYG' is undefined' or something similar. Works just fine with firefox.

Comments

cbuetas’s picture

cbuetas commented

hi

I have the same problem...

know solution?

Error line:
<script type="text/javascript">WYSIWYG.attach('edit-body', mysettings);</script>

sbrooks’s picture

sbrooks commented

Same here. Works great in Firefox, but doesn't even show up in IE 6 or 7.

paolorizzi78’s picture

paolorizzi78 commented

I've exactly the same problem guys, anyone got any answer to this?

Thnks for yr help

onesimpleman’s picture

onesimpleman commented

I got the same issue, is there a work around
Regards
Onesimpleman

Leeteq’s picture

Leeteq commented

I dont experience any specific error messages, but the editor only shows up in Firefox, not in IE7 or Opera 9x.

leetamus’s picture

leetamus commented

same goes for Chrome.

drupalnesia’s picture

drupalnesia commented

Please try openWYSIWYG 6.x with Drupal 6. I'm working on 6.x version now.

drupalnesia’s picture

drupalnesia commented
Status: Active » Closed (fixed)

Closed. (Go to 6.x version)

leetamus’s picture

leetamus commented

o well guess i'll find another module. Not everyone can switch their entire site to v6... many needed modules still don't even have a v6 version so that's a none option. I've always found this to be a seriously debilitating factor when working with Drupal...

Leeteq’s picture

Leeteq commented

In my humble opinion, I think there is a significant risk in demotivating people from participating in this module if the issues are simply closed and not moved along to the new version, and not even with any comments on whether or not the issue has actually been fixed in the new version..

This way of dealing with the issues queue is a bit discouraging.

I agree with leetamus in #9;
- as long as there are still several important modules that has not made it into D6.x version yet, this is too early to write off D5 entirely.

I suggest announcing the need for more co-maintainers on the project's main page. Perhaps someone is interested in working on the D5 version a bit longer.

pyc’s picture

pyc commented

Just like that... If the 5.x version is so crippled that it can't work with IE6 or 7, why is it available at all...

hawkdrupal’s picture

hawkdrupal commented

Because it provides so much functionality, so has been used to build sophisticated sites, Drupal 5 is still the MOST IMPORTANT version. It's not even certain that Drupal 6 will ever be widely adopted, given the limited support by third-party modules. Whether Drupal 7 even matters is therefore unknown.

This phenomenon is widely known in software circles. Many app-dev products/platforms peak with a version that is "good enough", therefore gets widely adopted. Later versions, if they break ANYTHING, never succeed because the cost to migrate, vs. the business benefit, is unfavorable -- no business will spend money to migrate just because a new version exists, even if it is "cool", and there's zero change if the new version creates business problems that don't need to exist. Witness Windows Vista, Microsoft Access after 97, and many others. However, new versions that manage to support ALL prior code/modules often thrive -- witness Lotus Notes 8.5 which can run code from Notes 1 released 18 years ago. Oddly, the "peak" of many products is often "version 5" (Windows XP is 5, for instance).

Not that Drupal's makers are doing anything wrong, it's just a huge risk to require that critical modules be re-coded. It's that most users can't do it, the original coders have abandoned the project, and the whole notion of evolution hits a brick wall.

Too bad about this module, which had a chance to be very important but is obviously dead.