Close [x]

Release Notes

Edit this page on GitHub

Known issues

This page discusses known issues in all Magento 2 releases starting with Developer Beta in December, 2014.

We have identified the following known issues in this release:

You might need to clear your Composer cache

We introduced a change on packages.magento.com that had the unintended result of causing errors with certain Magento packages.

This affects only users who used composer create-project to create their Magento project between the dates of August 13 and August 17, 2015.

A user reported one symptom on GitHub about an error that occurred during the installation:

[UnexpectedValueException]
The checksum verification of the file failed (downloaded from https://packages.magento.com/_packages/magento_framework-1.0.0-beta.zip)

The cause is a conflict between packages on packages.magento.com compared to the local Composer cache. To resolve the issue, clear your Composer cache as follows:

  1. Log in to your Magento server as a user with permissions to run composer in the Magento installation directory.
  2. cd <your Magento install dir>
  3. Enter composer clear-cache

Known issue with timezone in certain PHP versions

This issue affects builds earlier than 0.74-beta10 only. If you have a later build, you can ignore this issue.

There is a known PHP issue with versions:

  • 5.5.10–5.5.16
  • 5.6.0

This issue prevents users from being able to set their timezones to Greenwich time and several other time zones.

To work around this issue, after installing the Magento 2 software, edit the following files:

  • app/code/Magento/Config/Model/Config/Backend/Locale/Timezone.php
  • lib/internal/Magento/Framework/Locale/Lists.php
  • setup/src/Magento/Setup/Model/Lists.php

In each file, change the value of $zones as follows:

from

$zones = \DateTimeZone::listIdentifiers(\DateTimeZone::ALL_WITH_BC);

to

$zones = \DateTimeZone::listIdentifiers(\DateTimeZone::ALL);

Known issue with xdebug

If you use the optional PHP extension xdebug, you can encounter exceptions:

  • During installation
  • Accessing either the Magento Admin or storefront after a successful installation

Sample exception:

Fatal error: Maximum function nesting level of '100' reached, aborting!

To resolve this issue, you can:

  • Disable the xdebug extension.
  • Set the value of xdebug.max_nesting_level to a value of 200 or more. For more information, see xdebug documentation.

After you change the configuration of or disable xdebug, restart Apache:

  • CentOS: sudo service httpd restart
  • Ubuntu: sudo service apache2 restart

Access errors

Errors might display when you attempt to access the Magento storefront or Magento Admin after installation:

Storefront:

"Can't create directory /var/www/html/m/var/generation/Magento/Framework/App/PageCache/Identifier/."
#0 /var/www/html/m/lib/internal/Magento/Framework/Code/Generator/Autoloader.php(34): Magento\Framework\Code\Generator->generateClass('Magento\\Framewo...')
#1 [internal function]: Magento\Framework\Code\Generator\Autoloader->load('Magento\\Framewo...')
#2 [internal function]: spl_autoload_call('Magento\\Framewo...')
... more

Magento Admin:

"Class Magento\Logging\Model\FlagFactory does not exist"
"#0 /var/www/html/ui/lib/internal/Magento/Framework/ObjectManager/Definition/Runtime.php(46): Magento\Framework\Code\Reader\ClassReader->getConstructor('Magento\\Logging...')
#1 /var/www/html/ui/lib/internal/Magento/Framework/ObjectManager/Factory/Factory.php(170): Magento\Framework\ObjectManager\Definition\Runtime->getParameters('Magento\\Logging...')
#2 /var/www/html/ui/lib/internal/Magento/Framework/ObjectManager/ObjectManager.php(71): Magento\Framework\ObjectManager\Factory\Factory->create('Magento\\Logging...')
... more

In either case, try accessing the storefront or Magento Admin again.

Setup Wizard reports failure falsely

In some cases, the Setup Wizard appears to have failed when it has not failed.

Symptoms:

  • The following message displays at the top of your browser on the last page: Installation is incomplete. Check the console log for errors before trying again.
  • If you open the console, a success message displays at the bottom with no errors or exceptions.

In this case, the installation was successful. You can access the storefront and Magento Admin as discussed in Verify the installation.

To access your Magento-created encryption key:

  1. Log in to your Magento server as a user with root privileges.

  2. Do any of the following:

    • Build 0.74-beta9 or earlier: Open <your Magento install dir>/app/etc/config.php in a text editor.
    • Build 0.74-beta10 or later: Open <your Magento install dir>/app/etc/env.php in a text editor.
  3. Locate the value of 'key' =>.

This is your encryption key.

Setup Wizard fails because of no installation log

In some cases (such as running the Setup Wizard in two browser windows or tab pages at the same time), the installation fails because it cannot create install.log.

To work around this issue, see Installation fails; cannot create install.log