Closed (fixed)
Project:
Wysiwyg SpellCheck
Version:
6.x-1.1
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
9 Jun 2009 at 08:22 UTC
Updated:
2 Jul 2009 at 14:50 UTC
Drupal 6.12
Wysiwyg SpellCheck 6.x-1.1
Wysiwyg API 6.x-2.x-dev
TinyMCE 3.2.4.1
Followed your instructions, TinyMCE works, Spellchecking is selectable but don't show up in editor
Comments
Comment #1
iva2k commentedCan you confirm that spellcheker plugin is installed in:
sites/all/modules/wysiwyg_spellcheck/tinymce/spellcheker
directory,
so there is a file
sites/all/modules/wysiwyg_spellcheck/tinymce/spellcheker/editor_plugin.js
?
Comment #2
glueckskind commentedThanks for your reply.
Yes, editor_plugin.js is where it should be.
Comment #3
iva2k commentedI confirm that newest WysiwygAPI 6.x-2.0 that was released June 10 and also 6.x-2.x-dev posted few days earlier breaks AsciiMath plugin and TinyMCE spellcheck plugin, so it has something to do with latest WysiwygAPI changes. I'm working on it.
Comment #4
iva2k commentedTry new release of Wysiwyg SpellCheck 6.x-1.2
Comment #5
jefflocke commentedComment #6
xaviviena commentedWhen I click on the new 'ABC' button in my tinymce editor both Firefox and ID crash. It shows an error about scripts.
I'm using:
- wysiwyg_spellcheck-6.x-1.2
- tinymce_spellchecker_php_2_0_2
- Wysiwyg 6.x-1.0 and 6.x-2.0 with no improvement
- TinyMCE 3.2.4.1
Any idea about it?
Thanks!
Comment #7
iva2k commented@xaviviena
I was not able to reproduce your problem - works here with Google Chrome 2.0.172.31, FF 3.0.11 and IE 8.0.6001.18702. Peculiar part is that both IE (did you mean IE, BTW?) and FF crash for you - it is hard to design a webpage that crashes both browsers the same way.
Can you get the error details for the error you mention about scripts?
Things to try (just thoughts):
- Clear all drupal caches
- Turn off performance optimization for .js
- Turn off all other TinyMCE plugins
Can you give a URL that I can try (maybe in private message)?
Comment #8
glueckskind commentedFor me your fix worked. Thanks a lot.
Comment #9
iva2k commented@glueckskind
Great! Can you share details what fix of the 3 worked for you? That may indicate some problem with the code.
@xaviviena
I suggest we move your problem to a different bug. Yours seems unrelated to the original problem. Please repost as a new issue.
Comment #10
iva2k commented