-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Error after upgrade from 2.0.7 to 2.1.0 #5223
Comments
@Krapulat Then run: |
@andimov Same problem after:
The output with -vvv is:
|
@Krapulat |
@andimov The permissions are correct. I attach composer.lock and this is composer.json:
|
@andimov In exception.log it appears:
|
I am getting the exact same error with an identical exception trace. Here is my composer.json {
"name": "magento/project-community-edition",
"description": "eCommerce Platform for Growth (Community Edition)",
"type": "project",
"version": "2.0.7",
"license": [
"OSL-3.0",
"AFL-3.0"
],
"repositories": [
{
"type": "composer",
"url": "https://repo.magento.com/"
}
],
"require": {
"magento/product-community-edition": "2.1.0",
"composer/composer": "@alpha"
},
"require-dev": {
"phpunit/phpunit": "4.1.0",
"squizlabs/php_codesniffer": "1.5.3",
"phpmd/phpmd": "2.3.*",
"pdepend/pdepend": "2.2.2",
"sjparkinson/static-review": "~4.1",
"fabpot/php-cs-fixer": "~1.2",
"lusitanian/oauth": "~0.3 <=0.7.0"
},
"config": {
"use-include-path": true
},
"autoload": {
"psr-4": {
"Magento\\Framework\\": "lib/internal/Magento/Framework/",
"Magento\\Setup\\": "setup/src/Magento/Setup/",
"Magento\\": "app/code/Magento/"
},
"psr-0": {
"": "app/code/"
},
"files": [
"app/etc/NonComposerComponentRegistration.php"
]
},
"autoload-dev": {
"psr-4": {
"Magento\\Sniffs\\": "dev/tests/static/framework/Magento/Sniffs/",
"Magento\\Tools\\": "dev/tools/Magento/Tools/",
"Magento\\Tools\\Sanity\\": "dev/build/publication/sanity/Magento/Tools/Sanity/",
"Magento\\TestFramework\\Inspection\\": "dev/tests/static/framework/Magento/TestFramework/Inspection/",
"Magento\\TestFramework\\Utility\\": "dev/tests/static/framework/Magento/TestFramework/Utility/"
}
},
"minimum-stability": "alpha",
"prefer-stable": true,
"extra": {
"magento-force": "override"
}
} |
I retried the upgrade without installing the sample data patch and it seems to have worked fine. There is also a possibility that I hadn't changed the document root to the base directory instead of pub before running the upgrade. |
I'm getting a different error:
composer.json:
|
Editing composer.json and manually modify to
and then 'composer update' it seems to work. Is anything wrong to do this @andimov ? |
Any update here? Do i have to reinstall everything just because of an upgrade from 2.0.7 to 2.1.0? |
@Krapulat |
@andimov Frontend + Backend just shows:
I got it running under 2.0.7 already with PHP 7.0.6... Command Line shows Exception as mentioned above. |
@developer-lindner |
No problems when updating composer - manually changed to 2.1.0 from 2.0.7. However, when I try to run setup:upgrade I get the same exception: [ReflectionException] I'm using php 7.0.7. |
Comparing my installation to a fresh install, there was an extra line in env.php. I added this and the issue went away:
This gets added at the end of the following list:
|
@maderlock |
For me, the |
@jldmn |
The "[Reflection Exception] Class Magento\Framework\App\Cache\Webapi does not exist" error |
@jldmn Then run: |
Did the trick for me! Thanks a lot! |
Ok, but now i got My Server runs Ubuntu 14.04 with php 5.6.23 |
The check should pass for php 5.6 as the relevant part of the condition in bootstrap is: PHP_VERSION_ID >= 50600 && PHP_VERSION_ID < 50700. It also fails if PHP for some reason fails to report its version number. I would first use phpinfo() to check that the version of PHP used to serve your pages is the one you think it is. |
@jldmn Do you have >1 version of PHP installed? What does |
I got that error! |
Clearing the cache (in my case Redis, not var/cache/) helped. |
@Krapulat |
After I upgrade magento from 2.0.7 to 2.1.0 via command line doing:
When I type "php bin/magento setup:upgrade" I get
Any ideas why is this happening?
The text was updated successfully, but these errors were encountered: