Bug #64593 [Csd]: Enchant fails to load any backends.

Edit report at https://bugs.php.net/bug.php?id=64593&edit=1 ID: 64593 User updated by: wschalle at gmail dot com Reported by: wschalle at gmail dot com Summary: Enchant fails to load any backends. Status: Closed Type: Bug Package: Enchant related Operating System: Windows 7, Windows Server 2008R2 PHP Version: 5.3.23 Assigned To: ab Block user comment: N Private report: N New Comment: That makes sense, but where was this change even made? Public releases of PHP should have the libs in the right places when you unzip them... Previous Comments: ------------------------------------------------------------------------ [2013-04-09 15:26:50] ab@php.net libenchant loads all the *.dll it can find in the plugin dir and discards those being not a plugin. That's why one could see some startup warnings in previous versions, as it was <php dir>. Now it loads from a separate path where only the plugins should be. I'd see it more like an improvement. That should be documented though, mood for that? :) ------------------------------------------------------------------------ [2013-04-09 15:05:29] wschalle at gmail dot com Any idea why this broke between 5.3.22 and 5.3.23? We tend to put dict files in the app, because some instances use different dictionaries. ------------------------------------------------------------------------ [2013-04-09 14:01:47] ab@php.net Great, thanks for checking. With the dicts you could also use the enchant_broker_set_dict_path() or just put the dicts into <php dir>share\myspell\dicts. ------------------------------------------------------------------------ [2013-04-09 13:40:16] wschalle at gmail dot com Putting the DLLs in <php_dir>\lib\enchant works. ------------------------------------------------------------------------ [2013-04-09 13:07:29] ab@php.net Put the plugin dlls should load if you put them into <php dir>\lib\enchant. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=64593 -- Edit this bug report at https://bugs.php.net/bug.php?id=64593&edit=1