-
Notifications
You must be signed in to change notification settings - Fork 53
plugin by the name "exception_handler" was not found #97
Comments
Thanks for your bug report - I can reproduce this bug -> the bug was introduced in 2.6.0 /: @weierophinney @ezimuel I think is has something todo with the server manager v2 / v3 compatibility - see #22 #69 @Marat-Tanalin To fix your issue you should use camalCase or lower case but don't separate by |
@weierophinney @ezimuel Should we add also all underscore variants to the list of aliases? Current snipped just for 5 storage plugins: protected $aliases = [
'clearexpiredbyfactor' => Plugin\ClearExpiredByFactor::class,
'clearExpiredByFactor' => Plugin\ClearExpiredByFactor::class,
'ClearExpiredByFactor' => Plugin\ClearExpiredByFactor::class,
'exceptionhandler' => Plugin\ExceptionHandler::class,
'exceptionHandler' => Plugin\ExceptionHandler::class,
'ExceptionHandler' => Plugin\ExceptionHandler::class,
'ignoreuserabort' => Plugin\IgnoreUserAbort::class,
'ignoreUserAbort' => Plugin\IgnoreUserAbort::class,
'IgnoreUserAbort' => Plugin\IgnoreUserAbort::class,
'optimizebyfactor' => Plugin\OptimizeByFactor::class,
'optimizeByFactor' => Plugin\OptimizeByFactor::class,
'OptimizeByFactor' => Plugin\OptimizeByFactor::class,
'serializer' => Plugin\Serializer::class,
'Serializer' => Plugin\Serializer::class
]; |
If plugin names with underscore-separated words cannot be used anymore, documentation should probably account for this. Namely, |
If they're commonly used, yes, we should add aliases for them, @marc-mabe ; do you want to do this? @Marat-Tanalin it's not that they cannot be used, but that zend-servicemanager v3 no longer does normalization. v2 would strip out non-alphanumeric characters from the service name to perform lookups, while v3 does strict literal matching. As such, if we create aliases using the most common separator characters, we can still use them. |
fixed #97 by adding underline names to plugin manager
When trying to use zend-cache downloaded separately via Composer (under Windows 7, fwiw), the following exception is thrown:
The relevant part of the stack trace:
composer.json
used to download the package:In case of using zend-cache from ZF downloaded entirely (
"zendframework/zendframework": "^2.5"
), the issue is not reproduced.Thanks.
The text was updated successfully, but these errors were encountered: