Twig 1.22.0 was released. According to our composer.json definition, you get that automatically when running composer update, which is what you need to do when you are using composer_manager.
Since it seems to contain a possibly unexpected BC break (See http://d8status.md-systems.ch/build.log, tons of "Uncaught PHP Exception LogicException: "Cache can only be a string, false, or a Twig_CacheInterface implementation." at /home/projects/d8modulestatus/internal/vendor/twig/twig/lib/Twig/Environment.php line 269"), we need to update to it and fix that.
Or, if there's a problem with it, at least lock down our version to 1.21.* I guess.
Comment | File | Size | Author |
---|---|---|---|
#10 | vendor-twig_1.22-2568085-10.patch | 897 bytes | plach |
#2 | 2568085-2.patch | 50.5 KB | alexpott |
Comments
Comment #2
alexpottRan
composer update twig/twig
...Was the composer output.
Comment #3
anavarreComment #4
dawehnerYeah the BC layer of twig indeed doesn't work as expected.
#2555243: Upgrade path / plan to Twig 2.x aka 2.0 is an issue about updating to twig 2.0
We would need to implement some proper caching:
This is just a start.
Comment #6
dawehnerI'll try to work on that for a while.
Comment #8
dawehnerPosted my result on [#25552433-35]
For now we should just limit our dependencies.
Comment #9
star-szrI created #2568171: Upgrade to Twig 1.22 and implement our own cache class to upgrade to Twig 1.22.0 and add our own cache class.
Comment #10
plachThis locks Twig on 1.21.* until we do #2568171: Upgrade to Twig 1.22 and implement our own cache class.
Comment #11
plachComment #12
dawehner+1 for now!
Comment #13
plachComment #14
webchickCommitted and pushed to 8.0.x. Thanks!