I have used the googiespell mod on several of my sites for years and have been essentially delighted with its functionality.
However, two weeks ago the feature stopped working on one of my sites. At first I noticed that it would always say that there were no errors even when there were obvious errors in the text. Finally, the spell check button simply disappeared.
It took a lot of time to track down what happened. It appears that the problem resulted from my upgrade from msxml4 to msxml6 on my server.
What I found was that multi-line comments in javascript were no longer being seen as comment lines so the text in those lines would cause exceptions and the scripts would simply fail.
That was easy to fix - simply change the multi-line comments to single line comments. That is, for every line that was included between one that started with '/*' and a line that ended with '*/', just prepend '//' to each line. There are only a few in googiespell.js and ajs.js.
The more difficult problem to pin down was that now there is a builtin 'getcookie()' function which gets control instead of any similarly named function in your own code. Cookiesupport.js defines that function as one which expects to receive a string variable while the built-in function expects to receive an object.
I fixed that by renaming getcookie() to mygetcookie() in that program and changed the single call to it in googiespell.js.
The feature now works again exactly as it used to.
Thought those of you who used this neat little mod would appreciate this feedback.
Edited by - jamesdavis on 11 November 2007 16:32:32
Argh this is frustrating! Mine just stopped working (but I can't pinpoint what is different now from before. Your changes didn't work, but I'm going to investigate my sites native JS based on your fix.
Topic Locked
Posted - 11 November 2007 : 16:32:11
