Currently the application have symfony 2.8.42 and twig version 1.35.3.
Due to some security issue in twig we need to upgrade twig to 2.4.4 and above. But I am not sure as what else will be broken once I update the twig version ?
I cannot find anywhere for symfony 2.8 compatible twig versions or vice versa.
Can someone help me with the compatible version and what are the things that will break if I update twig to 2.4.4 ?
I tested myself by updating and was able to update to twig 2.4.4 without any issues. Changes the composer.lock file for the same and did the composer install again, the new twig version as created successfully.
Related
I'm supporting a project that has a version of the following package.
https://www.npmjs.com/package/vue-typeahead-bootstrap
the version in the package.json says we imported version 2.6.0 however the lastest version currently is 2.5.3 beta. I would have to assume someone manually changed this. So if the version specified is beyond the version that currently exists, is it smart enough to just take the latest version. and will it automatically update the the newest version until it hits 2.6.0?
I'm gonna just change it match the current version anyway, but I was curious if anyone knew the functionality of this.
Please look at versions of this package
The version 2.6.0 goes prior 2.5.x versions
I need to update PHPMailer on few servers if any old version was installed.
How to check installed version
How to update it to PHPMailer 5.2.20 (for example)
It depends on how you installed it. If you're using the recommended method of using composer, then a simple composer update will get you the latest version. Your composer.lock file will show you which version you currently have, or you can open the VERSION file which will show you the version number you've got - or if you have a very old version that predates the VERSION file, look in the source files instead - they will also say what version they are. If you've installed it manually, just download the latest version from Github and replace your current version.
Just upgraded the locomotivecms engine from an older 2.0.x version to 2.1.0
Everything worked great except for tags referencing .css and .js assets
Specifically: {{ 'bootstrap.css' | stylesheet_tag }} results in the following error on screen
Liquid error: bad component(expected relative path component): https://com.citrrus.locomotive.s3.amazonaws.com/sites/51970154b5dd470002000004/theme/stylesheets/bootstrap.css
I've confirmed this is not an issue related to upgrading the engine version by deploying a fresh install of 2.1.0. I created new pages, snippets, and assets from scratch and I still get the above error.
Any suggestions are greatly appreciated
This was a bug in Locomotive 2.1.0.
Didier and the NoCoffee team pushed a fix in version 2.1.1
https://github.com/locomotivecms/engine/issues/713
My project demands and upgrade from groovy 1.7.2 to 1.8.x stable release, there are several jar's are created using groovy 1.7.2 version, let me know whether these jar's will be compatible with 1.8.x also or not, or do i need to completely re-built it,
As it says on this mailing list entry:
A jar built with 1.7 will not run with a 1.8 runtime because two files were moved and one was removed.
I am running Ampps 4.9.3 on Mac, and I am trying to install Laravel 5.6, which has a dependency on PHP 7.1.3. The latest version of Ampps says it supports 7.1.8, but I can't figure out how to change it from 7.1.2. Sorry if I'm missing something obvious, thanks for your help!
As #IgnazioC said, you can replace the contents of the relevant php version with a new one. You can grab the latest PHP 7.1 windows builds from https://windows.php.net/download#php-7.1
Make sure you download the VC14 x86 Thread Safe build, because this is what Ampps uses. You can also download newer versions of ionCube, XDebug and Opcache, but this isn't usually required.
InstallationFolder\ampps\data\apps
Edit this file to change your PHP Version in Ampps. You can actually use this to upgrade or change any modules whether it be PHP or Apache or mysql, etc...