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

Raising Issues for confusing version compatibility #77

Closed
shahariaazam opened this Issue Feb 24, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@shahariaazam

shahariaazam commented Feb 24, 2017

PHP Parse error: syntax error, unexpected '.' in /base/data/home/apps/b~previewtechs-cloud/slim-app-skeleton:20170224t205746.399418087592248769/vendor/twig/twig/lib/Twig/Extension/Core.php on line 1552

"twig/twig": "^1.18|^2.0", I guess it is causing some trouble. Recently I just ran my application on my local machine with PHP 7.1. It works well but when I just deployed that app to Google App Engine (PHP 5.5.9 environment) then it raised error.

PHP Parse error:  syntax error, unexpected '.' in /base/data/home/apps/vendor/twig/twig/lib/Twig/Extension/Core.php on line 1552

So I am pretty sure it's because of PHP versioning. So if anybody want to avoid the issue, they need to manually add main "twig/twig" package in their installation. Otherwise, somebody can face compatibility issue after app deployment.

I think, we can add a small note in Readme.md file.

@akrabat

This comment has been minimized.

Member

akrabat commented Jun 27, 2017

I would prefer to see the platform setting documented in the README.

@stof

This comment has been minimized.

stof commented Aug 3, 2017

The issue is about the way you used Composer. If you run composer update on PHP 7.1, composer will not ensure compatibility with PHP 5.5 when installing dependencies.
If you want a lock file compatible with PHP 5.5, you have 2 options:

  • run composer update on PHP 5.5
  • use the platform configuration setting of composer to overwrite the PHP version being considered by Composer.

@akrabat akrabat closed this May 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment