-
Notifications
You must be signed in to change notification settings - Fork 725
Error after update to v2.2.3 #1621
Comments
Hi, |
The issue here is that the TranslationServiceProvider checks the implementation it should use based on Doing version checks on the kernel version does not work fine when installing components separately. |
I think class checks are better even if they look hacky as well. |
well, a class check is exactly what we need here: detecting the feature itself instead of trying to detect the version (frontend guys have learned this since years btw) |
current packet configuration (working)
|
@nictrace what would be interesting is the non-working list. |
completely the same, except silex version 2.2.3 |
as it breaks with a "Error: Class 'Symfony\Component\Translation\Formatter\MessageFormatter' not found", see silexphp/Silex#1621
We don't have a 2.2 branch. We are always fixing bug on the master branch. So, the fix should go on master and be part of the 2.3 series. That's how we also work on Twig, and that allows to reduce the maintenance workload. In any case, 2.3 is just about adding Symfony 4 support, so no big deal to jump to 2.3.0 when it's ready IMHO. |
... and now that I read the thread again, I understand the issue :) Let's say that we can to an exception here if that really important and create a 2.2.4 release with the bug fix. If someone can work on a patch, I will happily apply it locally and make a release. |
Is a patch like the following totally out of scope or not ?
If it doesn't fit, please do not bash me. |
thanks @jibundeyare , looks good (as an alternative there is #1627 if needed : ) ) |
@SpacePossum your PR looks much better to me. |
It has been merged and shipped by fabpot , enjoy the new release with the fix! |
After update to v2.2.3 I got a ClassNotFoundException, while class MessageFormatter was non found.
Rollback to 2.2.2 fixes it
screenshot
The text was updated successfully, but these errors were encountered: