Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bootstrap error: Unable to resolve plugin "useragent"; no corresponding plugin with that name #92

Closed
kstenschke opened this issue Jul 8, 2020 · 8 comments

Comments

@kstenschke
Copy link

Bootstrap fails with error Unable to resolve plugin "useragent"; no corresponding plugin with that name
this error occurs on our system with zf1-future versions > 1.17.2

I suspect d822ef1 being related to the issue (added a comment into that commit as well).

Probably additional change of the autoloader configuration must be done after this diff, related info within readme.md would be helpful.

kstenschke referenced this issue Jul 8, 2020
…standard. It will not autoload anymore in Composer v2.0.
@Jimbolino
Copy link
Collaborator

do you have example code, how i can trigger this error?

@Drivez
Copy link

Drivez commented Aug 11, 2020

$zf = new \Zend_Application( APP_ENV, APPLICATION_PATH . '/config/application.ini' );

in the application.ini we had this option:

resources.useragent.mobile.features.classname = "Zend_Http_UserAgent_Features_Adapter_Browscap"

after commenting this out, the application got bootstrapped and worked

@Drivez
Copy link

Drivez commented Aug 11, 2020

in the vendor/shardj/zf1-future/library/Zend/Application/Resource/UserAgent.php the class name is UserAgent, should it be Zend_Application_Resource_UserAgent?

The rename of the class name worked for me.

@Jimbolino
Copy link
Collaborator

yes, as you were typing i also found the offending commits and reverted them in dev-master :)

@Drivez
Copy link

Drivez commented Aug 11, 2020

nice great work, thanks for the quick response, a version bump so we can do a composer update?

@Jimbolino
Copy link
Collaborator

https:/Shardj/zf1-future/releases/tag/release-1.18.5

@kstenschke
Copy link
Author

kstenschke commented Sep 1, 2020

In our installation, this problem was caused by a WURFL API configuration nested in application.yaml (application.ini), under resources.useragent.wurflapi.

Configuration entry was: resources.useragent

The problem resolved by changing the entry into: resources.Zend_Application_Resource_UserAgent

@adli
Copy link

adli commented Mar 2, 2024

The problem still exists on Linux environment (case-sensitive filenames).

For Quick fix, please rename the file UserAgent.php to Useragent.php in /shardj/zf1-future/library/Zend/Application/Resource/
directory. (that's the filename in original Zend framework)

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants