PungoSpell Spell Checker for vB3.5 WYSIWYG and Standard mode

PungoSpell for vB 3.5 WYSIWYG and Standard mode

Intro: PungoSpell supports WYSIWYG mode disply using DHTML on the spell check popup window. It uses PHP's buitin PSPELL module. Many have this already compiled in, but if not, it's easy to add.

What this hack does This hack modifies the PungoSpell software package from PungoSpell to allow spell checking on vBulletin for both modes, WYSIWYG and standard mode.

Change Log:
v2.4 December 25, 2005: Security fix for cases where you allow HTML posts and they contain malicious code (Credit goes to Brendan Donahue for finding the issue and alerting TechGuy, and to TechGuy for alerting me to it)

v2.3 Bug fix standard mode.
v2.2 Bugfix
v2.1 Changed JS to handle vB 3.5 beta 4
v2.0 Initial release for vB 3.5 beta Features, no more config edits, uses admin panel for settings


Note: There's another hack for spell checker for vBulletin3 using PHPSpell. (I plan to port it to vB 3.5 shortly) You might want to compare both to decide which one you like best.
https://vborg.vbsupport.ru/showthrea...threadid=65723

Credit PungoSpell Is a free software using the MIT license. By default, it will work fine in standard mode. This hack will allow it to work for both standard and WYSIWYG.

Requirements: You will need to have PSPELL compiled into your PHP setup. Many have this by default. To find out if you already have it, check your PHP info from the vBulletin Admin Panel: Import & Maintenance > View PHP Info. Search for "pspell". If it's there, you're fine. If not, you can recompile PHP with the "--with-pspell" paramater.

You also need aspell software installed on your server with a dictionary setup.

Please check with your server admin if not sure


Installation Instructions

1. Download the attached file, and unpack into your main forum directory, except for pungo_install.php which should go into your admincp directory. Make sure the file "custom.pws" is writable by apache, otherwise the "Learn" function will not work.

2. Run pungo_install.php in the admincp directory. Once you're done, edit the options in the vB options menu under the title "PungoSpell".

3. It has English setup by default. If you want it to use any other language, it's easy. Just edit the language setting from your control panel.

"en" stands for English. Change it to the code of the language you want. Like "fr" for French, for example. Make sure your system has the required dictionary. You see the dictionary config by typing "aspell config" at the command line, to see which dictionaries you have.

4. Edit each template where you'd like to have the spell checker. For example:

newreply template

A. Find

</head>

Add above

<script src="pungospell.js"></script>

B. Add somewhere the followin (below $navbar for example)g:

      <form name="spell_form" id="spell_form" method="POST" target="spellWindow" action="pungospell.php">
                <input type="hidden" name="spell_formname" value="">
                <input type="hidden" name="spell_fieldname" value="">
                <input type="hidden" name="spellstring" value="">
             </form>

C. Find the submit and preview buttons:

				<input type="submit" class="button" name="sbutton" value="$vbphrase[save_changes]" accesskey="s" tabindex="1" />
		<input type="submit" class="button" name="preview" value="$vbphrase[preview_changes]" accesskey="p" tabindex="1" />

Add below:

<input type="button" class="button" value="Spell Check" onClick="spellCheck('vbform', '$editorid', '2');" />

And repeat the same steps for other templates like newthread etc.


Trouble shooting:

1. Learn doesn't work: Try this: Change the first line from custom.pws:

personal_ws-1.1 en 0

To:

personal_ws-1.1 english 0

en worked fine for me on Fedora and Gentoo, but I had to change to english on RHE.


2. Change language If you have learning enabled, affter you change the language from the admincp, you also, in the file custom.pws, the first line reads something like:

personal_ws-1.1 en 0

You will need to change en to the language you use, like fr


Please click Install if you have installed this mod.

[Snake]

Oh right, sorry my bad. Just ignore my message.

[Snake]

Uh I got a problem here. I have done the template edits for this hack but I still cannot view the spell check button. I have edited the newthread, newpost, and newpoll template bits. O.o Any idea?

[tamarian]

Originally Posted by Snake

Uh I got a problem here. I have done the template edits for this hack but I still cannot view the spell check button. O.o Any idea?

You might not be using the style you have edited

[Snake]

Actually I donn't. I have just got the default vB skin installed on my forums so...

[tamarian]

Originally Posted by Snake

Actually I donn't. I have just got the default vB skin installed on my forums so...

Well, the button is just HTML code. If it doesn't show up, you must have misplaced it.

[safiel]

Hey there.

I'm getting a javascript error in Firefox, on VB3.5RC2

Error: document.getElementById(fieldName + "_textarea") has no properties
Source File: http://www.bashanything.com/pungospell.js
Line: 27

Any advice?

[tamarian]

Originally Posted by safiel

Hey there.

I'm getting a javascript error in Firefox, on VB3.5RC2

Error: document.getElementById(fieldName + "_textarea") has no properties
Source File: http://www.bashanything.com/pungospell.js
Line: 27

Any advice?

Ah, I forgot to update the instructions to match the code changes.

Re-do step C in the template edits, which I have just updated. Let me know how it goes.

[Snake]

Okay I can view the buttons now. I missed a few template edits. My bad. I'm having another problem though. When clicking on the 'Spell Check' button, nothing happens to me. :\

[tamarian]

Originally Posted by Snake

Okay I can view the buttons now. I missed a few template edits. My bad. I'm having another problem though. When clicking on the 'Spell Check' button, nothing happens to me. :\

Have you updated the template edits with the new step C?

[safiel]

Originally Posted by tamarian

Ah, I forgot to update the instructions to match the code changes.

Re-do step C in the template edits, which I have just updated. Let me know how it goes.

That was it

Thanks for the quick reply and the wonderful hack.