| Author |
 Topic  |
|
AnonJr
Moderator
United States
5768 Posts |
 Posted - 18 August 2006 : 10:30:59
|
Good question... off hand I'd say no since all the MOD does is pass the text to the Google Spell Checker - unless you can convince Google that they need to add those words.. 
I'd be happy to be proved wrong though.< |
 |
|
|
leatherlips
Senior Member
USA
1838 Posts |
|
|
bobby131313
Senior Member
USA
1163 Posts |
Posted - 18 August 2006 : 11:27:10
|
Well, it was just a matter of time before I pushed it too far.
LL did you see the review I wrote for you at SnitzBitz? <<< subtle hint to everyone else
< |
Switch the order of your title tags |
|
|
|
leatherlips
Senior Member
USA
1838 Posts |
|
|
bobby131313
Senior Member
USA
1163 Posts |
Posted - 18 August 2006 : 14:44:57
|
quote:
bobby131313, Did you notice the button style I added?
Not yet, been playing with my new photo gallery today. Learning PHP now a little at a time. 
I'll check it out though, I just have the generic button no.
< |
Switch the order of your title tags |
|
|
|
dayve
Forum Moderator
USA
5820 Posts |
Posted - 20 August 2006 : 21:41:58
|
quote:
Originally posted by Shaggy
I meant srtip the forum code from the string you want to spellcheck. To see what I mean, try entering something like [b]test[/b] in the textarea and hitting your spellcheck button.
That doesn't seem to cause a problem at all. The spell checker does indeed recognize the words between forum tags.< |
 |
|
|
|
Shaggy
Support Moderator
Ireland
6780 Posts |
Posted - 21 August 2006 : 06:14:12
|
quote:
Originally posted by dayvequote:
Originally posted by Shaggy
I meant srtip the forum code from the string you want to spellcheck. To see what I mean, try entering something like [b]test[/b] in the textarea and hitting your spellcheck button.
That doesn't seem to cause a problem at all. The spell checker does indeed recognize the words between forum tags.
Oops, meant to say try [b]tst[/b].
< |
 Search is your friend
“I was having a mildly paranoid day, mostly due to the
fact that the mad priest lady from over the river had
taken to nailing weasels to my front door again.” |
|
|
|
Pull My Finger
Starting Member
43 Posts |
Posted - 21 August 2006 : 10:33:28
|
quote:
Originally posted by Shaggy
quote:
Originally posted by dayvequote:
Originally posted by Shaggy
I meant srtip the forum code from the string you want to spellcheck. To see what I mean, try entering something like [b]test[/b] in the textarea and hitting your spellcheck button.
That doesn't seem to cause a problem at all. The spell checker does indeed recognize the words between forum tags.
Oops, meant to say try [b]tst[/b].
Here is what I have on my end......
 < |
|
|
|
Eric Coleman
Starting Member
USA
10 Posts |
Posted - 23 August 2006 : 16:26:13
|
Normal use of Google APIs require you to obtain a license key.
http://www.google.com/apis/index.html
Here is a page that details how to use the Google API to check spelling:
http://www.asp101.com/articles/jeremy/googlespell/default.asp
As you can see you need to provide your own license key. I didn't see any mention in the readme or anywhere else of this mod of where to put your license key.
After noticing the method used in this mod is completely different from the license way of spell checking I did some research. It appears this method is a reverse engineer of the google toolbar spell check. I also found out that "leatherlips" isn't the original author of this either. The original can be found here: http://amix.dk/googiespell
Since google places limits on the number of spell checks you can do in a day, as per their normal license agreement, you might want to be carefull about using this toolbar hack. If your site is popular and google notices a large number of spell checks coming from a single IP address you might get blacklisted.< |
|
|
|
Pull My Finger
Starting Member
43 Posts |
Posted - 23 August 2006 : 18:22:17
|
Found a Bug!
When adding a New Forum Category or editing a Forum Category I get a popup message when clicking the "Create New Category" or "Edit Category Name" admin icons........
Popup Message--> "Text Area Not Found"
Before I installed this mod I installed the usergroups mod, so at first I didn't know which one caused the bug.
First I ran My post.asp backup before installing usergroup code. No Bug!
Then I ran post.asp with usergroup code. Again No Bug!
Then I ran post.asp with usergroup and googlespell code. Now I have Bug!
To be double sure I took the post.asp file backup without usergroup and googlespell code. Then added the googlespell code only. Had the Bug!
On My site IM running SHN code
Heres My SHN post.asp with my last 2 mods installed (UserGroups and GoogleSpell)
http://www.yankeewaterfowler.com/temp/post.txt
< |
Edited by - Pull My Finger on 23 August 2006 18:23:35 |
|
|
|
leatherlips
Senior Member
USA
1838 Posts |
Posted - 23 August 2006 : 19:07:19
|
quote:
Originally posted by Eric Coleman
I also found out that "leatherlips" isn't the original author of this either.
I give credit to the author of Googiespell in the readme. I simply implemented it in Snitz as a MOD for others to use if they wanted. I have an earlier post that clearly posts my interest about the googiespell and asked if anyone knew how to make it work for Snitz.quote:
Originally posted by Pull My Finger
Found a Bug!
When adding a New Forum Category or editing a Forum Category I get a popup message when clicking the "Create New Category" or "Edit Category Name" admin icons........
Popup Message--> "Text Area Not Found"
This actually is not a bug. In the googiespell.js file, there is a script that causes this alert to appear. When you are creating or editing a new category, the googiespell is noticing that there isn't a textarea that is requiring to be spell checked. You can click the alert box's OK and then create/edit as normal. However, I do agree that it is annoying.
To prevent the Text Area Alert you can do this:
Open the googiespell.js file and look for:
else
if(this.report_ta_not_found)
alert("Text area not found");
Add the part in red shown below:
// else
// if(this.report_ta_not_found)
// alert("Text area not found");
Or you can simply remove those three lines completely.< |
Mangione Magic Forum - The Music of Chuck Mangione
My Mods: Googiespell MOD | Link To Reply MOD | Petition MOD | Contact Page MOD | Share This Topic MOD | MP3 MOD | PageEar MOD | Google Viewer MOD |
Edited by - leatherlips on 23 August 2006 20:56:53 |
|
|
|
Pull My Finger
Starting Member
43 Posts |
Posted - 23 August 2006 : 22:43:45
|
quote:
Originally posted by leatherlips
To prevent the Text Area Alert you can do this:
Open the googiespell.js file and look for:
else
if(this.report_ta_not_found)
alert("Text area not found");
Add the part in red shown below:
// else
// if(this.report_ta_not_found)
// alert("Text area not found");
Or you can simply remove those three lines completely.
Thanks! That did the trick!
Thanks For the Great Mod!< |
|
|
|
dayve
Forum Moderator
USA
5820 Posts |
Posted - 23 August 2006 : 23:53:31
|
quote:
Originally posted by Pull My Finger
quote:
Originally posted by leatherlips
To prevent the Text Area Alert you can do this:
Open the googiespell.js file and look for:
else
if(this.report_ta_not_found)
alert("Text area not found");
Add the part in red shown below:
// else
// if(this.report_ta_not_found)
// alert("Text area not found");
Or you can simply remove those three lines completely.
Thanks! That did the trick!
Thanks For the Great Mod!
Actually, I would not recommend commenting out the lines because there is a boolean type variable for preventing this message from appearing. Modify this variable in googiespell.js:
this.report_ta_not_found = true;
to
this.report_ta_not_found = false;< |
|
|
|
|
leatherlips
Senior Member
USA
1838 Posts |
|
|
Pull My Finger
Starting Member
43 Posts |
Posted - 24 August 2006 : 18:23:24
|
quote:
Originally posted by dayve
quote:
Originally posted by Pull My Finger
quote:
Originally posted by leatherlips
To prevent the Text Area Alert you can do this:
Open the googiespell.js file and look for:
else
if(this.report_ta_not_found)
alert("Text area not found");
Add the part in red shown below:
// else
// if(this.report_ta_not_found)
// alert("Text area not found");
Or you can simply remove those three lines completely.
Thanks! That did the trick!
Thanks For the Great Mod!
Actually, I would not recommend commenting out the lines because there is a boolean type variable for preventing this message from appearing. Modify this variable in googiespell.js:
this.report_ta_not_found = true;
to
this.report_ta_not_found = false;
Done! Thanks dayve for pointing that out!< |
|
|
|
Topic |
|
Googiespell MOD
