-
Notifications
You must be signed in to change notification settings - Fork 9.4k
vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php on line 93 #7072
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
Comments
If somebody come across this error, you must have forgot to add the add to you htaccess file. AddType application/x-httpd-php76 .php Thanks |
I |
Ok, 2.1 doesn't work on PHP 5.5. 2.0 was the last release working with 5.5 |
doesn't work on PHP 7.0.8 |
Whats the solution then? |
whats the solution? |
Solved: The command "php bin/magento deploy:mode:show" was failing on PHP 5.5.9-1ubuntu4.20 (cli) but is succeeding with PHP 7.0.12 (cli) |
Got this error in my running Magento 2.1.4 one time in the middle of the night 0:00 as a cronjob error from:
PHP 7.0.15-0ubuntu0.16.04.4 (cli) ( NTS ) |
I'm having the same problem like this too.I'm using this Ubuntu 16.04 php 7.0xx. $ bin/magento setup:upgrade
$ bin/magento setup:di:compile Now the error is gone. But not sure why this is happen though. |
I had the same Problem, a new Magento 2.1.7 installation, php 7.0.2, mysql 5.6. in developer mode and the cronjob always send me an email with: But I had to get the shop online and changed to production mode, ignoring the error, because I found no solution (but updatin the system) into the www. But I had no more time for that. Now everything works fine. |
Magento use php 7.1
It's worked to me. |
Uh oh!
There was an error while loading. Please reload this page.
Preconditions
Steps to reproduce
Expected result
Actual result
Error:
Parse error: syntax error, unexpected '.' in /home/longstone/public_html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php on line 93
Everything in SSH works correctly, upgrade, compile, clear cache, reindex...
The text was updated successfully, but these errors were encountered: