ieSpell for spellchecking is out of date

[durangod]

Hi,

 

I was typing an email to a client and has anyone ever noticed that the spell check option for the email text editor for WHMCS is a thing called ieSpell and it is totally outdated.

 

when you click the spell check button which is right next to the embeded media (it shows abc with a checkmark thru it) it tells you that ieSpell is not installed would you like to install it and then takes you here.

 

http://www.iespell.com/download.php and the latest version was in 2010...

 

We talk about security every day in this business, and yet WHMCS links to a script that is almost 4 years since it has been updated, seems to be we need something more current as i refuse to put a 4 year old program on my computer.

 

there has to be a better option!

 

 

thanks..

Edited November 17, 2013 by durangod

[SeanP]

It is the TinyMCE WYSIWYG editor (used by tons of web apps out there) that is linking to ieSpell. WHMCS is simply using the TinyMCE editor. Spell checkers don't have to be updated as often, if they still work correctly. This really wouldn't be a security type of issue, since it is just a spell check app being installed.

 

I believe IE 10 has a built-in spell checker if you can upgrade to that. If not, the Google Chrome and Firefox web browsers have built-in spell checking. For IE9, I use Speckie (http://www.speckie.com). It is a spell checker, for IE, that will check as you type (like the ones in Google Chrome and Firefox).

[durangod]

Thanks for the reply, good info I guess what i was thinking is that even with TinyMCE you can still edit the links for those editor buttons, i remember changing the links on CKEditor awhile back.. But im not aware of how to do that with this editor.

 

So i guess i was thinking that WHMCS maybe should provide a different link to something thats maybe a tad more current. Surely something that old needs to be dusted off and updated, look how much updating we do just with php and mysql and html and js, seems every day something gets deprecated, and i am sure the windows enviroment is no different. So surely it has some code changes that need to be upgraded after that long.

[SeanP]

TinyMCE is coded to use ieSpell, and ieSpell has not been updated since 2010. So, in short of changing core code of the TinyMCE editor, the only other option would be to remove the link. To me, it's easier to have the browser spell check as you type in any form field. A lot of times the spell check in WYSIWYG editors can be a little buggy, anyway.

[Infopro]

The ieSpell tool was for IE of course, back when it was needed. IE has spell check is built in, like other browsers now days.

 

I'd be interested to know the exact name and version of the browser you're using.

[durangod]

IE10 version 10.0.9200.16736

 

Here is the point i am trying to make folks. Any script is only as strong as its weakest link. What should happen for example if someone decided to use that button and use the install of ieSpell and something does goes wrong. Are they going to be upset with TinyMCE? No... they are going to be upset with WHMCS. Once you include anything in your software and sell it, you become liable for whatever you decide to include that may be sub par.

 

So if it is no longer needed then just remove the button on the next version.

[Damo]

Once you include anything in your software and sell it, you become liable for whatever you decide to include that may be sub par.

 

But ieSpell isn't included. It's something you install manually.

[durangod]

But ieSpell isn't included. It's something you install manually.

 

I was not referring to ieSpell i was referring to TinyMCE, MCE became liable when they added it to MCE and WHMCS became liable when they added MCE to WHMCS...

 

If something happens what is WHMCS going to do, tell their customer that just paid $200 for their software to go chase down someone at MCE and then MCE passes the buck to ieSPell. My point is that anything that old regardless should never be a part of a software that wants to be considered state of the art and current. There is no reason that a 4 year old script with no updates for that long should ever be given the opportunity to be used or executed as part of WHMCS.

 

The option button should be removed or something more current put in its place (which there is no need now i guess). Having that even as an optional download is no different than WHMCS saying that we support and recommend ieSpell.