From 43c880d4bc713ee367c36e69f07bed340b272147 Mon Sep 17 00:00:00 2001 From: mage2-team Date: Wed, 17 Dec 2014 11:22:46 -0800 Subject: [PATCH] 0.42.0-beta1 * Fixed bugs: * Fixed an issue with incorrect price index rounding on bundle product * Fixed an issue with product price not being updated when clicking the downloadable link on the downloadable product page * Fixed an issue with exception appearing when clicking the Compare button for selected products * Added backend UI improvements * Fixed an issue with the Compare Products block appearing on mobile devices * Fixed an issue with inability to add conditions to the Catalog Products List widget * Fixed an issue with a customer redirected to page 404 when trying to unsubscribe from a newsletter * Fixed an issue with showing a warning when customer tried to change billing address during multiple address checkout * Fixed an issue with redirecting a customer to the Admin panel when clicking the Reset customer password link * Fixed an issue with inability of a newly registered customer to select product quantity and shipping addresses during multiple checkout * Fixed an issue with showing Zend_Date_Exception and Zend_Locale_Exception exceptions after a customer placed an order * Fixed an issue with inability to rename a subcategory on a store view level * Fixed an issue with not saving the changed parameters in the Admin section of the backend configuration * Fixed an issue with fatal error appearing when trying to enter a new address on multi-address checkout * Fixed an issue with inability to delete a product in the customers wishlist in the Admin panel * Fixed an issue with inability to change product configuration in the customers wishlist in the Admin panel * Fixed an issue with showing errors when customer with no addresses tried to checkout a product via Check out With Multiple Addresses * Fixed an issue with fatal errors appearing in the Recently Viewed Products frontend widget block * Fixed an issue with the ability of an authenticated RSS admin user to access all RSS feeds * Fixed an issue with widgets losing their options and part of their layout references if more than11 layout references are added and saved * Fixed an issue with the Privacy Policy link missing in the frontend * Fixed an issue with inability to place an order during multiple checkout * Fixed an issue with store views switching in the frontend * Fixed an issue with incorrect work of the CSS minificator * Fixed an issue with inability to open the edit page for a CMS page after filtering in the grid * Fixed an issue with inability to expand customer menu if it doesn't contain the categories, if responsive * Fixed an issue with the absence of JS validation for the Zip/Postal code field * Fixed an issue with a 1 cent difference in the tax summary and detail on an invoice and a credit memo for a partial invoice when a discount and fixed product tax are applied * Fixed an issue with throwing validation error for the State field when saving a product with FPT * Fixed an issue with throwing an error when trying to save a timezone * Fixed an issue with Exploited Session ID in second browser leading to Error * Fixed an issue with session loss on page 404 when using the Varnish caching * Fixed an issue with integration test not resetting static properties to correct default values after each test suite * Fixed an issue with PDO exception during an installation when MySQL does not meet minimum version requirement * Removed hardcoded PHP version requirement in the setup module. Validation of PHP version during installation now uses the Composer information * Fixed an issue with not redirecting to the setup page when Magento is not installed * Fixed an issue with missing of some languages in the dropdown list on the Customize Your Store page of the Web installation * Merged and updated data and SQL install scripts to 2.0.0 * Merged user reported patch to fix fetching headers for APIs when PHP is run as fast CGI * Removed the @deprecated methods from the code base * Fixed an issue with the fatal error when enabling Website Restrictions in the frontend * Fixed an issue with showing incorrect message for view files population tool when the application is not installed * Fixed certain customer APIs to be accessed anonymously * Fixed integration tests to avoid sending emails * Fixed an issue with the Continue button losing its style after returning to the Shipping Information step during one-page checkout in Luma, IE11, FF * Fixed an issue with incorrect spaces removal * Fixed an issue with broken responsive design of the Compare Products functionality in the Blank Theme * Fixed an issue with showing the No such entity with cartId' message error appearing during creating a new order for a new customer on non-default website * Fixed an issue with inability to reselect the File Permission on the Readiness Check step during the installation * Fixed an issue with inability to find by name simple and virtual products in the customer wishlist grid * Fixed integration test fail after DbStatusValidatorTest modifies schema version of the Core module * Fixed an issue with inability to install Magento without the ConfigurableProduct module * Fixed an issue with fatal error appearing on the grouped product page if the GroupedProduct module is disabled * Fixed an issue with no validation for assigning an attribute to an attribute group (API) * Fixed an issue with inability to place an order with the registration method and different billing and shipping address * Fixed an issue with broken footer layout on some Admin panel pages (product creation, order creation, catalog etc.) in IE11 * Fixed an issue with countries previously selected in the Ship to specific countries field not visible when the parameter is changed to showing all allowed countries and set back again to specific countries in the flat rate shipping method IE11 * Fixed an issue with not showing admin tax and cache warning notifications in IE11 * Fixed an issue with product alerts not working * Fixed an issue with incorrect URL rewrite for category with two stores after renaming category for one store * Fixed an issue with inability to save a bundle product with a re-created bundle option * Fixed an issue with inability to add conditions to the Catalog Products List widget * Fixed an issue with export not available if modules for Products Import/Export are removed * Fixed an issue with the Use Layered Navigation for custom product attributes leading to an error on an anchor category page in the frontend * Fixed an issue with the broken export product file on environment SampleData * Fixed an issue with cache not invalidating after categories are moved in tree * Fixed an issue with last five orders showing 0 items quantity after invoices are created * Fixed an issue with an exception appearing on a category page if installing Magento without LayeredNavigation module * Fixed an issue with tax rate not being saved if all states were chosen for any non-default country * Fixed an issue with multi-select fail on the Customer add/edit form * Added exception handling for required fields for REST APIs * Fixed an issue with success message missing after the signup for price alert * Fixed an issue with inability to create a return order from the Admin panel * Fixed an issue with incorrect work of the Default Value for Disable Automatic Group Changes Based on VAT ID setting * Fixed an issue with fatal error on the I18n tools launch due to incorrect bootstrap/autoload * Stabilized functional tests for products in the Catalog module * Stabilized functional tests for product attribute in the Catalog module * Created installation test * Updated functional tests for the new customer form * Updated Magento to follow the new tagging mechanism * Removed incomplete in functional tests for fixed bugs * Fixed an issue with missing theme preview images * Fixed broken SOAP tests * Fixed an issue with invalid online status on the Edit Product page in the Admin panel * Fixed an issue with incorrect location of an error message "Incorrect CAPTCHA" in the frontend * Fixed an issue with showing endless JS loader on the View Configurable Product page in the frontend page, IE, Google Chrome * Fixed a JavaScript error that occurred on the Create Admin Account step during Magento web installation * Fixed an issue where a product remained in stock after saving it with the Out of Stock inventory value * Fixed an issue where the JS loader was not disappearing on the View Product page on the frontend if a customer closed the gallery * Fixed an issue where the JS loader was absent while CAPTCHA was being reloaded * Fixed an incorrect alignment of fields on the Create Packages popup * Fixed an issue where Google Content Experiments was not available for CMS pages * Fixed the broken design of the New Product Attribute popup * Fixed an issue where product page was not found if an incorrect image URL was inserted through using the WYSISYG editor * Fixed an issue where the Search Term Report and Search Term list in backend did not work * Fixed an issue where downloadable links and samples were not saved because of the JavaScript error * Fixed an issue where Magento Installation Guide was not accessible via the 'Getting Started' link if installing Magento through using web installer with custom locale and custom encryption key * Fixed an issue with the code style * Fixed an issue where changes made in tax configuration did not appear in the backend on the Create New Order page * Fixed an issue where it was impossible to update options of bundle products from the mini shopping cart * Fixed an issue where layered navigation worked incorrectly with the Automatic (equalize product counts) setting * Fixed an issue with the incorrect error message appearing when running 'php -f setup/index.php help * Fixed an issue where URLs for subcategories were incorrect after editing URL of a subcategory * Fixed an issue where attribute labels were loaded from cache after updating product attributes * Fixed an issue where form data was not preserved when product form did not pass server side validation * Fixed an issue with static files missing in the Production mode * Fixed issues with errors appearing after View Files Population Tool was run * Processed GitHub requests: * [#683](https://github.com/magento/magento2/pull/683) -- CMS Router not routing correctly * [#786](https://github.com/magento/magento2/pull/786) -- Fix Travis CI builds * Various improvements: * Improved error message when DB schema or data was not up-to-date * Added nginx configuration to code base * Removed online payment methods for the Dev Beta release * Sample Data: * Implemented Luma Sample Data * Framework improvements: * Updated ZF1 dependency to 1.12.9-patch1 * Documentation update: * Covered the Sales module with API documentation --- README.md | 841 ++------------------------------------------------ composer.json | 8 +- 2 files changed, 29 insertions(+), 820 deletions(-) diff --git a/README.md b/README.md index 5a4d5604..c9608767 100644 --- a/README.md +++ b/README.md @@ -1,71 +1,22 @@ [![Build Status](https://travis-ci.org/magento/magento2.svg?branch=master)](https://travis-ci.org/magento/magento2) - +

Welcome

Welcome to Magento 2 installation! We're glad you chose to install Magento 2, a cutting edge, feature-rich eCommerce solution that gets results. -#### Contents - -* Magento 2 system requirements -* Composer and Magento -* High-level installation roadmap -* Required server permissions -* Prerequisites -* Installing Composer -* Cloning the Magento 2 GitHub repository -* Installing or reinstalling the Magento software -* Verifying the installation -* Troubleshooting - -

Magento 2 system requirements

- -Before you install Magento 2, make sure your system meets or exceeds the following requirements: - -* Operating systems - - Linux distributions such as RedHat Enterprise Linux (RHEL), CentOS, Ubuntu, Debian, and so on - -* Composer (latest stable version) -* Apache 2.2 or later -* PHP 5.4.11 or 5.5.x -* Required PHP extensions: - - * PDO/MySQL - * mbstring - * mcrypt - * mhash - * simplexml - * curl - * gd2, ImageMagick 6.3.7 (or later) or both - * soap - -* MySQL 5.6.x -* Mail Transfer Agent (MTA) or an SMTP server -* Optional but recommended: - - * php_xdebug2.2.0 or later (development environments only; can have an adverse effect on performance) - * PHPUnit (as a command-line tool) 4.1 or later - -

Composer and Magento

- -We now use Composer to install the Magento 2 software. Composer enables us to manage Magento 2, extensions, and their dependencies. +The installation instructions that used to be here are now published on our GitHub site. Use the information on this page to get started or go directly to the guide. -Composer provides you with the following advantages: +

New to Magento? Need some help?

+If you're not sure about the following, you probably need a little help before you start installing the Magento software: -* Enables you to reuse third-party libraries without bundling them with source code -* Component-based architecture with robust dependency management -* Manages dependencies to reduce extension conflicts and compatibility issues -* Versioned dependencies -* Semantic versioning -* Supports PHP Framework Interoperability standards +* Is the Magento software installed already? +* What's a terminal, command prompt, or Secure Shell (ssh)? +* Where's my Magento server and how do I access it? +* What's PHP? +* What's Apache? +* What's MySQL? -We'll have more information soon on how developers can use Composer to package extensions to distribute to Magento merchants and to other developers. +

Step 1: Verify your prerequisites

-

High-level installation roadmap

- -Following is a brief overview of how to install the Magento 2 software. - -

Step 1: Verify your prerequisites

- -Use the following table to verify you have the correct prerequisites to install the Magento 2 software. +Use the following table to verify you have the correct prerequisites to install the Magento software. @@ -75,772 +26,34 @@ Use the following table to verify you have the correct prerequisites to install - + - + - + - + - +
For more information
Apache 2.2 or laterApache 2.2 or 2.4 Ubuntu: apache -v
CentOS: httpd -v		ApacheApache
PHP 5.4.11 or 5.5.xPHP 5.4.x (where x = 11 or later) or 5.5.x php -vPHPPHP Ubuntu
PHP CentOS
MySQL 5.6.x mysql -u [root user name] -pMySQLMySQL
-

Step 2: Prepare to install

- -After verifying your prerequisites, perform the following tasks in order to prepare to install the Magento 2 software. - -1. Installing Composer -2. Cloning the Magento 2 GitHub repository - -

Step 3: Install and verify

- -1. Installing or reinstalling the Magento software -2. Verifying the installation - -

Required server permissions

- -Unless otherwise noted, all commands in this Readme must be entered as a user with `root` privileges and permission to write to the web server docroot. Depending on your system, that might mean you must use different user accounts or add users to the web server user group—provided that group has sufficient privileges. - -Installing software on Linux typically requires `root` privileges. You should generally not install the Magento 2 software in the web server docroot using `root` privileges; however, that is up to you. - -

Prerequisites

- -This section discusses how to install software required to install Magento 2. - -See one of the following sections: - -* Before you begin -* Apache -* PHP -* MySQL - - -

Before you begin

- -Before you install Magento, you must do all of the following: - -* Set up one or more hosts that meet the Magento 2 system requirements. -* Make sure you can back up your entire system at various points during the installation so you can roll back in the event of issues. - -

Apache

- -

Installing Apache on Ubuntu

- -
  1. Install Apache using the guidelines on the Ubuntu site.
    2. -
  2. Enable server rewrites: -
    • Apache 2.2: Use the guidelines on askubuntu.
      • -
    • Apache 2.4: Enter the following command: a2enmod rewrite
    -
    3. -
  3. Specify the type of directives that can be used in .htaccess. Magento uses .htaccess for redirects. For guidelines, see: -
    • Apache 2.2: The Apache 2.2 documentation.
      • -
    • Apache 2.4: The Apache 2.4 documentation.
      -Note that in Apache 2.4, the server's default site configuration file is /etc/apache2/sites-available/000-default.conf
      -For example, you can add the following to the bottom of 000-default.conf:
      -
      <Directory "/var/www">
-AllowOverride [value from Apache site]
-</Directory>
      -Note: You must change the value of AllowOverride in the directive for the directory to which you expect to install the Magento software. For example, to install in the web server docroot, edit the directive in <Directory /var/www>.
    -
    4. -
  4. Restart Apache: service apache2 restart
- -

Installing Apache on CentOS

- -1. Install Apache: - - `yum -y install httpd` - - For additional information, see the Apache site. - -2. Enable server rewrites. - - **Note**: You must change the value of Allow Override in the directive for the directory to which you expect to install the Magento software. For example, to install in the web server docroot, edit the directive in <Directory "/var/www/html">. - -2. Set the type of directives that can be used in `.htaccess`. Magento uses `.htaccess` for redirects. Apache documentation. - -3. Restart Apache: `service httpd restart` - -

MySQL

- -

Installing MySQL on Ubuntu

- -1. Install MySQL on Ubuntu 12 or Ubuntu 14. -2. Configure the database instance. - -

Installing and configuring MySQL on CentOS

- -The following procedure is based on Install MySQL Server 5.6 in CentOS 6.x and Red Hat 6.x Linux. - -1. Install the MySQL database: - - 
cd /tmp
-wget http://repo.mysql.com/mysql-community-release-el6-5.noarch.rpm
-rpm -ivh mysql-community-release-el6-5.noarch.rpm
-yum -y install mysql-server
- -2. Start MySQL. - - `service mysqld start` - -3. Set a password for the root user and set other security-related options. Enter the following command and follow the prompts on your screen to complete the configuration. - - `mysql_secure_installation` - -

Configuring the Magento database instance

- -This section discusses how to create a new database instance for Magento. Although a new database instance is recommended, you can optionally install Magento into an existing database instance. - -To configure a MySQL database instance: - -1. Log in to your database server as any user. -2. Enter the following command to get to a MySQL command prompt: - - `mysql -u root -p` - -3. Enter the MySQL `root` user's password when prompted. -4. Enter the following commands in the order shown to create a database instance named `magento` with user name `magento`: - 
create database magento;
-GRANT ALL ON magento.* TO magento@localhost IDENTIFIED BY 'magento';
- -5. Enter `exit` to quit the command prompt. - -

PHP

- -Magento 2 requires PHP 5.4.11 or later or PHP 5.5.x. - -**Note**: Magento 2 does *not* support PHP 5.6. - -

PHP 5.5 or 5.4 on Ubuntu

- -
Install PHP 5.5 on Ubuntu 14
- -To install PHP 5.5 on Ubuntu 14: - -1. Enter the following command: - - `apt-get -y install php5` - -2. Verify the PHP version by entering `php -v`. Messages similar to the following should display: - - 
PHP 5.5.9-1ubuntu4.4 (cli) (built: Sep  4 2014 06:56:34)
-	Copyright (c) 1997-2014 The PHP Group
-	Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies
-    with Zend OPcache v7.0.3, Copyright (c) 1999-2014, by Zend Technologies
- -
Install PHP 5.5 on Ubuntu 12
- -1. Use the following commands from dev-metal: - - 
add-apt-repository ppa:ondrej/php5
-	apt-get update
-	sudo apt-get install php5
- -2. Verify the PHP version by entering `php -v`. Messages similar to the following should display: - - 
PHP 5.5.18-1+deb.sury.org~precise+1 (cli) (built: Oct 17 2014 15:11:34)
-	Copyright (c) 1997-2014 The PHP Group
-	Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies
-    with Zend OPcache v7.0.4-dev, Copyright (c) 1999-2014, by Zend Technologies
- -
Install PHP 5.4 on Ubuntu 12
- -To install PHP 5.4 on Ubuntu 12: - -1. Use the following instructions from askubuntu: - - 
add-apt-repository ppa:ondrej/php5-oldstable
-	apt-get update
-	apt-get upgrade
-	apt-get install php5
- -2. Verify the PHP version by entering `php -v`. Messages similar to the following should display: - - 
PHP 5.4.33-2+deb.sury.org~precise+1 (cli) (built: Sep 25 2014 09:06:25)
-	Copyright (c) 1997-2014 The PHP Group
-	Zend Engine v2.4.0, Copyright (c) 1998-2014 Zend Technologies
- -3. Restart Apache: `service apache2 restart` - -
Upgrade to PHP 5.4 on Ubuntu
- -To upgrade to PHP 5.4 on Ubuntu: - -1. Use the instructions on phpave. -2. After upgrading, verify the PHP version by entering `php -v`. Messages similar to the following should display: - - 
PHP 5.4.33-2+deb.sury.org~precise+1 (cli) (built: Sep 25 2014 09:06:25)
-	Copyright (c) 1997-2014 The PHP Group
-	Zend Engine v2.4.0, Copyright (c) 1998-2014 Zend Technologies
- -3. Restart Apache: `service apache2 restart` - -

Install required PHP extensions on Ubuntu

- -Enter the following command to install required PHP extensions: - -
apt-get -y install php5 php5-mhash php5-mcrypt php5-curl php5-cli php5-mysql php5-gd
- -

Ubuntu 14 only: workaround for mcrypt issue

- -There is a known issue in Ubuntu 14 with the `mcrypt` PHP extension. To work around the issue, see askubuntu. - -

PHP 5.5 or 5.4 on CentOS

- -PHP 5.3 is the default PHP version on CentOS distributions. Upgrade to PHP 5.4 using a repository like remi. - -The following resources are also available: - -* kb.parallels -* stackoverflow -* remi repository - -To verify if PHP is installed already, enter `php -v`. If PHP is *not* installed, install it by entering the following command: - -
yum -y install php php-xml
- -
PHP 5.5 on CentOS
- -To upgrade to PHP 5.5: - -There is more than one way to upgrade CentOS 6.5 to PHP 5.5; the following is a suggestion only. Consult a reference for additional options. - -Enter the following commands in the order shown. - -
cd /tmp
-rpm -Uvh https://mirror.webtatic.com/yum/el6/latest.rpm
-yum -y remove php-common-5.3.3-40.el6_6.x86_64
-yum -y install php55w php55w-opcache
- -Restart Apache: `service httpd restart` - -
PHP 5.4 on CentOS
- -To upgrade to PHP 5.4: - -1. Enter the following commands: - - 
cd /tmp
-	rpm -Uvh http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
-	rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-6.rpm
-	yum -y --enablerepo=remi install httpd php php-common
- -2. To verify PHP 5.4 is installed, enter `php -v`. The command displays results similar to the following: - - 
PHP 5.4.33 (cli) (built: Sep 20 2014 16:20:03)
-	Copyright (c) 1997-2014 The PHP Group
-	Zend Engine v2.4.0, Copyright (c) 1998-2014 Zend Technologies
- -3. Restart Apache: `service httpd restart` - -

Install required PHP extensions on CentOS

- -Enter the following command to install required PHP extensions: - -`yum -y --enablerepo=remi install php-xml php-mcrypt.x86_64 gd gd-devel php-gd php-mysql` - -

Setting the PHP timezone (all operating systems)

- -Before you install Magento, you might need to set the system time zone for PHP; otherwise, errors like the following display during the installation and time-related operations like cron might not work: - -`PHP Warning: date(): It is not safe to rely on the system's timezone settings.` [more messages follow] - -To set your time zone: - -1. Locate your server's time zone in the available time zone settings. -2. Locate `php.ini` by entering the following command: - - `php -i | grep "Loaded Configuration File"` - - Typical locations follow: - - Ubuntu: `/etc/php5/cli/php.ini` - - CentOS: `/etc/php.ini` - -3. Open `php.ini` in a text editor. - -4. Locate the following setting and uncomment it if necessary: - - `date.timezone =` - -5. Add the time zone setting you found in step 1. -6. Save your changes to `php.ini` and exit the text editor. - -

Setting the PHP memory limit (all operating systems)

- -Increase `memory_limit` in `php.ini` to at least 512MB for normal operation or 2GB for testing: - -1. Open one of the following in a text editor: - - * Ubuntu: `/etc/php5/apache2/php.ini` - * CentOS: `/etc/php.ini` -2. Change `memory_limit` to: - - `memory_limit = 512M` or more for normal operation - - `memory_limit = 2G` or more for testing - -3. Save your changes and exit the text editor. - -4. Restart Apache: - - Ubuntu: `service apache2 restart` - - CentOS: `service httpd restart` - - -

Installing Composer

- -To install Composer: - -1. Change to or create an empty directory on your Magento server. - -2. Enter the following commands: - - 
curl -sS https://getcomposer.org/installer | php
-	mv composer.phar /usr/local/bin/composer
- - For additional installation options, see the Composer installation documentation. - -

Cloning the Magento 2 GitHub repository

- -To clone the Magento 2 GitHub repository: - -1. Change to your web server's docroot directory. - - Typically, for Ubuntu, it's `/var/www` and for CentOS it's `/var/www/html`. - -2. Enter any of the following commands as a user with privileges to write to the web server docroot: - - To clone using HTTPS, use either of the following: - - `git clone https://github.com/magento/magento2.git` - - `git clone https://[your github.com user name]:[password]@github.com/magento/magento2.git` - - To clone using SSH: `git clone git@github.com:magento/magento2.git` - -3. Wait for the repository to clone on your server. - -**Note**: If you get an error that includes `Permission denied (publickey)`, see Troubleshooting. - -

Installing or reinstalling the Magento 2 software

- -Before you begin, make sure that: - -1. Your system meets the requirements discussed in Magento 2 system requirements. -2. You completed all prerequisite tasks discussed in Prerequisites. -3. You installed Composer. -4. You cloned the Magento 2 GitHub repository. - -

Setting file system permissions and ownership before you install

- -To make sure the installation completes successfully, we suggest the following file system permissions and ownership: - -* All files and directories owned by the web server user -* Certain directories must be writable - -

Finding the web server user

- -To find the web server user, enter one of the following commands: - -* Ubuntu: `ps -ef | grep apache2` -* CentOS: `grep User /etc/httpd/conf/httpd.conf` - -

Pre-installation permissions and ownership

- -Before the installation, set the following permissions: - -* All directories have 700 permissions `(drwx------)`. - - 700 permissions give full control (that is, read/write/execute) to the owner and no permissions to anyone else. - -* All files have 600 permissions `(-rw-------)`. - - 600 permissions mean the owner can read and write but other users have no permissions. - -

Setting permissions and ownership

- -1. To set ownership, enter the following commands as a user with `root` privileges: - - 
cd [your Magento installation directory]
-	chown -R [web server user name] .
- - CentOS example: - - 
cd /var/www/html/magento2
-	chown -R apache .
- - Ubuntu example: - - 
cd /var/www/magento2
-	chown -R www-data .
- -2. Set file and directory permissions: - - 
find . -type d -exec chmod 700 {} \;
-	find . -type f -exec chmod 600 {} \;
- -

Getting started with your installation

- -After you complete the tasks discussed in the preceding section, update Composer and run the installer: - -1. Log in to your Magento server as a user with `root` privileges. -2. Change to the Magento 2 installation directory. For example, - - `cd /var/www/html/magento2` - - **Note**: On Ubuntu, you might have to use the `sudo -s` or equivalent command to access this directory. - -3. As user with privileges to write to the web server docroot, enter `composer install` - - This command updates package dependencies and can take a few minutes to complete. - -4. Change to the Magento 2 `setup` subdirectory and enter `composer install`. - -**Note**: You must run `composer install` from *both* directories. - -

Running the Magento 2 installer

- -This section discusses how to run the command-line installer for Magento 2. - -**Note**: You must install Magento from its `setup` subdirectory. - -The installer is designed to be run multiple times if necessary so you can: - -* Provide different values - - For example, after you configure your web server for Secure Sockets Layer (SSL), you can run the installer to set SSL options. -* Correct mistakes in previous installations -* Install Magento in a different database instance - -**Note**: By default, the installer doesn't overwrite the Magento database if you install the Magento software in the same database instance. You can use the optional clean_database parameter to change this behavior. - -**Note**: If you get errors during the installation, see Troubleshooting. - -Before you begin, you can run the following commands to find values for some required options: - - - - - - - - - - - - - - - - - - - - -
Installer optionCommand
Languagephp -f index.php help languages
Time zonephp -f index.php help timezones
Currencyphp -f index.php help currencies
- -

The format of the command follows:

- - php -f index.php install [--[installation option name]=[installation option value] ... - -

The following table discusses the meanings of installation option names and values. An example is provided in Sample localhost installation.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameValueRequired?
base_url

Base URL to use to access your Magento Admin and storefront in the format http[s]://[host or ip]/[your Magento base dir]/.

-

Note: The scheme (http:// or https://) and a trailing slash are both required.

-

[your Magento base dir] is the docroot-relative path in which to install the Magento 2 software. Depending on how you set up your web server and virtual hosts, the path might be magento2 or it might be blank.

-

To access Magento on localhost, you can use either http://localhost/[your Magento base dir]/ or http://127.0.0.1/[your Magento base dir]/.

- 		Yes
backend_frontnamePath to access the Magento Admin. This path is appended to Base URL. -For example, if Base URL is http://www.example.com and Admin Path is admin, the Admin Panel's URL is http://www.example.com/admin—provided you configured your web server for server rewrites.Yes
db_host

Use any of the following:

-
  • The database server's fully qualified host name or IP address.
    • -
  • localhost if your database serve is on the same host as your web server.
    • -
  • UNIX socket; for example, /var/run/mysqld/mysqld.sock
-

Note: You can optionally specify the database server port in its host name like www.example.com:9000

-		Yes
db_nameName of the Magento database instance in which you want to install the Magento database tables.Yes
db_userUser name of the Magento database instance owner.Yes
db_passMagento database instance owner's password.No
db_prefix

Use only if you're installing the Magento database tables in a database instance that has Magento tables in it already.

-

In that case, use a prefix to identify the Magento tables for this installation. Some customers have more than one Magento instance running on a server with all tables in the same database.

-

This option enables those customers to share the database server with more than one Magento installation.

No
admin_firstnameMagento administrator user's first name.Yes
admin_lastnameMagento administrator user's last name.Yes
admin_emailMagento administrator user's e-mail address.Yes
admin_usernameMagento administrator user name.Yes
admin_passwordMagento administrator user password.Yes
languageLanguage code to use in the Admin and storefront. (If you have not done so already, you can view the list of language codes by entering php -f index.php help languages from the setup directory.)Yes
currencyDefault currency to use in the storefront. (If you have not done so already, you can view the list of currencies by entering php -f index.php help currencies from the setup directory.)Yes
timezoneDefault time zone to use in the Admin and storefront. (If you have not done so already, you can view the list of time zones by entering php -f index.php help timezones from the setup directory.)Yes
use_secure

1 enables the use of Secure Sockets Layer (SSL) in all URLs (both Admin and storefront). Make sure your web server supports SSL before you select this option.

-

0 disables the use of SSL with Magento. In this case, all other secure URL options are assumed to also be 0.

No
base_secure_url

1 means SSL is preferred in Magento URLs designed to use it (for example, the checkout page). Make sure your web server supports SSL before you select this option.

-

0 means SSL is not used.

No
use_secure_admin

1 means you use SSL to access the Magento Admin. Make sure your web server supports SSL before you select this option.

-

0 means you do not use SSL with the Admin.

No
admin_use_security_key

1 causes the Magento software to use a randomly generated key value to access pages in the Magento Admin and in forms. These key values help prevent cross-site script forgery attacks.

-

0 disables the use of the key.

No
session_save

Use any of the following:

-
  • files to store session data in the file system. File-based session storage is appropriate unless the Magento file system access is slow or you have a clustered database.
    • -
  • db.files to store session data in the database. Choose database storage if you have a clustered database; otherwise, there might not be much benefit over file-based storage.
No
keyIf you have one, specify a key to encrypt sensitive data in the Magento database. (This includes passwords and personally identifiable customer information.) If you don't have one, Magento generates one for you.No
cleanup_databaseTo drop database tables before installing the Magento 2 software, specify this parameter without a value. Otherwise, the Magento database is left intact.No
db_init_statementsAdvanced MySQL configuration parameter. Uses database initialization statements to run when connecting to the MySQL database. Consult a reference similar to this one before you set any values.No
sales_order_increment_prefixSpecify a string value to use as a prefix for sales orders. Typically, this is used to guarantee unique order numbers for payment processors.No
- -

Sample localhost installation

- -The following example installs Magento with the following options: - -* The Magento software is installed in the `magento2` directory relative to the web server docroot on `localhost` and the path to the Magento Admin is `admin`; therefore: - - Your storefront URL is `http://localhost` and you can access the Magento Admin at `http://localhost/admin` - -* The database server is on the same host as the web server. - - The database name is `magento`, and the user name and password are both `magento` - -* The Magento administrator has the following properties: - - * First and last name are is `Magento User` - * User name is `admin` and the password is `iamtheadmin` - * E-mail address is `user@example.com` - -* Default language is `en_US` (U.S. English) -* Default currency is U.S. dollars -* Default time zone is U.S. Central (America/Chicago) - -
php -f index.php install --base_url=http://localhost/magento2/
-	--backend_frontname=admin 
-	--db_host=localhost --db_name=magento 
-	--db_user=magento --db_pass=magento 
-	--admin_firstname=Magento --admin_lastname=User 
-	--admin_email=user@example.com 	--admin_username=admin 
-	--admin_password=iamtheadmin --language=en_US
-	--currency=USD --timezone=America/Chicago
- -

Reinstalling the Magento 2 software

- -This section discusses how to install the Magento 2 software after you installed it previously. You might do this in an development environment especially to get all the latest code changes. - -To reinstall the Magento 2 software: - -1. Optionally delete and re-create the database instance. -2. Log in to your Magento server as a user with permissions to modify files in the Magento file system. -3. Enter the following commands in the order shown: - - 
cd [your Magento install dir]
-git pull
-composer install
-cd setup
-composer install
- -4. Repeat the tasks discussed in Installing or reinstalling the Magento 2 software. - -

Verifying the installation

- -

Verifying the storefront

- -Go to the storefront in a web browser. For example, if your Magento 2 installation base URL is `http://www.example.com`, enter it in your browser's address or location bar. - -The following figure shows a sample storefront page. If it displays as follows, your installation was a success! - -

Magento storefront which verifies a successful installation

- -If the page appears unconfigured (no styles, only text), see Troubleshooting. - -

Verifying the Magento Admin

- -Go to the Magento Admin in a web browser. For example, if your Magento 2 installation base URL is `http://www.example.com`, and the Admin URL is `admin`, enter `http://www.example.com/admin` in your browser's address or location bar. - -(The Admin URL is specified by the value of the `backend_frontname` installation parameter.) - -When prompted, log in as a Magento Administrator. - -The following figure shows a sample Magento Admin page. If it displays as follows, your installation was a success! - -

Magento Admin which verifies a successful installation

- -If the page appears unconfigured (no styles, only text), see Troubleshooting. - -If you get a 404 (Not Found) error similar to the following, see Troubleshooting: - -`The requested URL /magento2index.php/admin/admin/dashboard/index/key/0c81957145a968b697c32a846598dc2e/ was not found on this server.` - -

Troubleshooting

- -### Problem: Cannot clone the Magento 2 GitHub repository - -**Detail**: Error is similar to the following: - -
Cloning into 'magento2'...
-Permission denied (publickey).
-fatal: The remote end hung up unexpectedly
- -**Solution**: Upload your SSH key to GitHub as discussed in the GitHub help page. - -### Problem: Cannot run 'composer install' - -**Suggestion**: Change to the directory in which you installed Composer and enter the following command: - -`mv composer.phar /usr/local/bin/composer` - -### Problem: During installation, PHP date warning - -**Details**: During the installation, the following message displays: - -`PHP Warning: date(): It is not safe to rely on the system's timezone settings. [more]` - -**Solution**: Set the PHP timezone properly. - -### Problem: During installation, the following fatal error displays: - -`PHP Fatal error: Class 'PDO' not found in /var/www/html/magento2/setup/module/Magento/Setup/src/Module/Setup/ConnectionFactory.php on line 44` - -**Solution**: Make sure you installed all required PHP extensions. - -### Problem: You cannot access Magento in a web browser - -**Details**: The following message displays when you try to access the Magento storefront or Admin: - -
Whoops, it looks like you have an invalid PHP version.
-Magento supports PHP 5.4.11 or newer.
- -**Solution**: Either upgrade PHP or restart Apache (Apache might not be using the same PHP version as is on the file system). - -To restart Apache: - -* Ubuntu: `service apache2 restart` -* CentOS: `service httpd restart` - -### Problem: Error after logging in to the Magento Admin: - -`The requested URL /magento2index.php/admin/admin/dashboard/index/key/0c81957145a968b697c32a846598dc2e/ was not found on this server.` - -Note the lack of a slash character between magento2 and index.php in the URL. - -**Solution**: The base URL is not correct. The base URL must start with http:// or https:// *and* it must end with a slash (/). Run the installation again with a valid value. +

Step 2: Prepare to install

-### Problem: After installing, images and stylesheets do not load; only text displays, no graphics. +After verifying your prerequisites, perform the following tasks in order to prepare to install the Magento software. -**Details**: The path to images and stylesheets is not correct, either because of an incorrect base URL or because server rewrites are not set up properly. To confirm this is the case, use a web browser inspector to check the paths to static assets and verify those assets are located on the Magento file system. +1. Install Composer +2. Clone the Magento repository -Magento 2 static assets should be located under `[your Magento install dir]/pub/static/` (there should be `frontend` and `adminhtml` directories). +

Step 3: Install and verify the installation

-Verify your server rewrites setting and your base URL and try again. +1. Update installation dependencies +2. Install Magento: + * Install Magento software using the web interface + * Install Magento software using the command line +2. Verify the installation diff --git a/composer.json b/composer.json index 3abe5585..d40271bf 100644 --- a/composer.json +++ b/composer.json @@ -2,7 +2,7 @@ "name": "magento/product-community-edition", "description": "eCommerce Platform for Growth (Community Edition)", "type": "project", - "version": "0.1.0-alpha108", + "version": "0.42.0-beta1", "license": [ "OSL-3.0", "AFL-3.0" @@ -29,12 +29,11 @@ "zendframework/zend-serializer": "2.3.1", "zendframework/zend-log": "2.3.1", "zendframework/zend-http": "2.3.1", - "magento/zendframework1": "1.12.9", + "magento/zendframework1": "1.12.9-patch1", "composer/composer": "1.0.0-alpha8", "magento/magento2-base": "self.version", "magento/module-admin-notification": "self.version", "magento/module-authorization": "self.version", - "magento/module-authorizenet": "self.version", "magento/module-backend": "self.version", "magento/module-backup": "self.version", "magento/module-bundle": "self.version", @@ -83,10 +82,8 @@ "magento/module-newsletter": "self.version", "magento/module-offline-payments": "self.version", "magento/module-offline-shipping": "self.version", - "magento/module-ogone": "self.version", "magento/module-page-cache": "self.version", "magento/module-payment": "self.version", - "magento/module-paypal": "self.version", "magento/module-persistent": "self.version", "magento/module-product-alert": "self.version", "magento/module-reports": "self.version", @@ -155,7 +152,6 @@ "psr-4": { "Magento\\Sniffs\\": "dev/tests/static/framework/Magento/Sniffs/", "Magento\\Tools\\": "dev/tools/Magento/Tools/", - "Magento\\Tools\\License\\": "dev/build/publication/license/", "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/",