schmittjoh / JMSTranslationBundle

Puts the Symfony2 Translation Component on steroids
http://jmsyst.com/bundles/JMSTranslationBundle
426 stars 292 forks source link

Installing web UI provoke error 500 #458

Open artandor opened 7 years ago

artandor commented 7 years ago
Q A
Bundle version 1.3.1
Symfony version 3.3
PHP version 7.1.9

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

stephanfo commented 7 years ago

I have exactly the same issue. Is it possible to have support ? If you need I have a commit on gitHub with this issue.

joshas commented 6 years ago

Same issue here. Reverted jms/di-extra-bundle to 1.7.0 - no errors. Other versions (1.7.1 and up) throws same exception.

gabrielmustiere commented 6 years ago

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

joshas commented 6 years ago

@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

Reflex14 commented 6 years ago

I have the same error on a clean Symfony 3.3 install.

    "jms/di-extra-bundle": "1.7.0",

Going back to this version solved it. Thanks @joshas !