6.0.0-beta1
9/14/25

[#6036] ASpell spell check not using correct path
Summary ASpell spell check not using correct path
Queue IMP
Queue Version 4.2-RC1
Type Bug
State Resolved
Priority 2. Medium
Owners slusarz (at) horde (dot) org
Requester matt1 (at) clara (dot) co (dot) uk
Created 12/24/2007 (6474 days ago)
Due
Updated 12/26/2007 (6472 days ago)
Assigned 12/26/2007 (6472 days ago)
Resolved 12/26/2007 (6472 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
12/26/2007 06:23:37 PM Michael Slusarz Comment #4
State ⇒ Resolved
Reply to this comment
Fixed in 4.2.
12/26/2007 05:51:54 PM Jan Schneider Assigned to Michael Slusarz
State ⇒ Assigned
 
12/24/2007 09:39:30 PM matt1 (at) clara (dot) co (dot) uk Comment #3 Reply to this comment
i have two versions of aspell, 1. /usr/bin/aspell (version 5)   2. 
/usr/local/bin/aspell  (version 6) i need it to use the SECOND one 
because Horde now requires the newer version.. When i set it in the 
SETUP, it didnt have any effect.. it still used the old version 5.. 
unless i set it manually in the spellchecker class itself.
12/24/2007 08:04:56 PM Chuck Hagenbuch Comment #2
State ⇒ Not A Bug
Reply to this comment
That's just the default - it gets overridden in setParams() (of the 
parent SpellChecker class), assuming you've configured it.
12/24/2007 06:13:56 PM matt1 (at) clara (dot) co (dot) uk Comment #1
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ ASpell spell check not using correct path
Queue ⇒ IMP
State ⇒ Unconfirmed
Reply to this comment
When using aspell as spell check driver the "path" set in the conf.php 
is not used when executing the aspell binary from 
imp/lib/SpellChecker/aspell.php.  Instead it is hard coded. in $_path 
at the top of the aspell.php

Saved Queries