-
Notifications
You must be signed in to change notification settings - Fork 292
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
Installing web UI provoke error 500 #458
Comments
I have exactly the same issue. Is it possible to have support ? If you need I have a commit on gitHub with this issue. |
Same issue here. Reverted jms/di-extra-bundle to 1.7.0 - no errors. Other versions (1.7.1 and up) throws same exception. |
hi @joshas , i have the same issue, but the refert for jms/di-extra-bundle not work form me. Can you give your composer.json/.lock. Ty |
@gabrielmustiere Here you go, it's from sample testing application, so there should be minimal set of packages only to get JMSTranslationBundle working: https://gist.github.com/joshas/32799378c252f2f8e06b76a060ab8b6a |
I have the same error on a clean Symfony 3.3 install.
Going back to this version solved it. Thanks @joshas ! |
Expected behavior
After installing the different bundles (JMSTranslationBundle, JMSDIExtraBundle, checking if i had sensio/framework-extra-bundle), and after i made the right configuration in config.yml and routing_dev.yml, the right behavior should be that the /_trans lead me to a translation interface (working), and change nothing else.
Actual behavior
Getting on a route different from /_trans return
Call to a member function has() on null
with error 500. Therefore, the whole site is dead, except the translation UI.Steps to reproduce
Install JMSTranslationBundle, then when asked, install JMSDIExtraBundle to get the web ui
After that, test the /_trans. This should work. But when you get to your others routes, they return 500 error
Stack Overflow referring to this : https://stackoverflow.com/questions/46416830/jms-call-to-a-member-function-has-on-null
The text was updated successfully, but these errors were encountered: