Book Image

Magento 2 Development Cookbook

Book Image

Magento 2 Development Cookbook

Overview of this book

With the challenges of growing an online business, Magento 2 is an open source e-commerce platform with innumerable functionalities that gives you the freedom to make on-the-fly decisions. It allows you to customize multiple levels of security permissions and enhance the look and feel of your website, and thus gives you a personalized experience in promoting your business.

Related Content you might be interested in

Current Title:

Small book image
Magento 2 Development Cookbook
Dec, 2015 | 304 pages
No titles found
Table of Contents (18 chapters)
Magento 2 Development Cookbook
Magento 2 Development Cookbook
Credits
Credits
About the Author
About the Author
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Upgrading from Magento 1
Upgrading from Magento 1
Introduction
Creating a Magento 1 website with sample data
Creating a Magento 2 website
Preparing an upgrade from Magento 1
Upgrading the database
Using an IDE
Writing clean code with PHP MD and PHP CS
2
Working with Products
Working with Products
Introduction
Configuring the catalog defaults
Working with attribute sets
Working with product types
Adding social media buttons
Embedding an HTML object
Changing the URL of a product page
3
Theming
Theming
Introduction
Exploring the default Magento 2 themes
Creating a Magento 2 theme
Customizing the HTML output
Adding extra files to the theme
Working with LESS
Changing a page title
Working with translations
Adding widgets to the layout
Customizing email templates
4
Creating a Module
Creating a Module
Introduction
Creating the module files
Creating a controller
Adding layout updates
Adding a translation file
Adding a block of new products
Adding an interceptor
Adding a console command
5
Databases and Modules
Databases and Modules
Introduction
Creating an install and upgrade script
Creating a flat table with models
Working with Magento collections
Programmatically adding product attributes
Repairing the database
6
Magento Backend
Magento Backend
Introduction
Registering a backend controller
Extending the menu
Adding an ACL
Adding configuration parameters
Creating a grid of a database table
Working with backend components
Adding customer attributes
Working with source models
7
Event Handlers and Cronjobs
Event Handlers and Cronjobs
Introduction
Understanding event types
Creating your own event
Adding an event observer
Introducing cronjobs
Creating and testing a new cronjob
8
Creating a Shipping Module
Creating a Shipping Module
Introduction
Initializing module configurations
Writing an adapter model
Extending the shipping method features
Adding the module in the frontend
9
Creating a Product Slider Widget
Creating a Product Slider Widget
Introduction
Creating an empty module
Creating a widget configuration file
Creating the block and template files
Creating a custom configuration parameter
Finalizing the theming
10
Performance Optimization
Performance Optimization
Introduction
Benchmarking a website
Optimizing the frontend of the website
Optimizing the database and MySQL configurations
Optimizing the Apache web server
Finding performance leaks in Magento
Configuring OPcache, Redis, and Memcached
Optimizing the PHP configurations
11
Debugging and Unit Testing
Debugging and Unit Testing
Introduction
Logging into Magento 2
Getting started with Xdebug
Running automated tests from Magento
Creating a Magento test case
Index
Index

Upgrading the database

In the previous recipe, we configured the database migration tool. In this recipe, we will run the migration tool so that we can migrate parts from a Magento 1 shop to a Magento 2 shop.

Getting ready

You need a Magento 1 website and a Magento 2 website. The Magento 2 website needs to have the database migration tool installed and configured as described in the previous recipe.

In this recipe, we will do a migration from a clean Magento 1 site, to a Magento 2 site without sample data.

We did a migration from a clean Magento 1 database with some test products. Make sure you have a cleanly installed Magento 1 shop with some test data (products, orders, and so on) in it.

How to do it...

  1. First we need to make sure that the database settings are correct in the vendor/magento/data-migration-tool/etc/ce-to-ce/packt-migration/config.xml file. Open that file and check that the database credentials are correct. We created this file in the previous recipe:

    <source version="1.9.1">
<database host="localhost" name="magento1_migration" user="root"/>
</source>
<destination version="2.0.0.0">
<database host="localhost" name="magento2_migration" user="root"/>
</destination>

    Note

    If you have a database prefix in your source or destination database, you can optionally configure source_prefix and dest_prefix in the <options> section of the same configuration file.

    Tip

    Test the migration first with a clean Magento 1.9 database. The mapping that we will use in this recipe is for a clean Magento 1.9 installation. With an existing shop, you will have custom attributes and entities that need more configuration to make the migration work.

  2. If these settings are correct, we can run the upgrade tool. Run the following command:

    php bin/magento migrate:data --help

  3. This gives us the following output:

  4. To start or test a migration, we have to run the following command:

    php bin/magento migrate:data vendor/magento/data-migration-tool/etc/ce-to-ce/packt-migration/config.xml

  5. The migration will start and will give the following output:

  6. The migration is now complete. If you check your database for the Magento 2 website, you will see that the data (products, categories, and so on) is migrated from Magento 1.

    Tip

    If you want to rerun the migration tool, you have to remove the var/migration-tool-progress.lock file.

  7. We can also migrate the settings from the Magento 1 website. To do this, you have to replace the data parameter in the command using settings.

  8. To check if the upgrade works, you have to look at the data of the Magento 2 installation. We can check the following things in the backend:

    • The orders (Sales | Orders)

    • The products (Products | Catalog)

    • The customers (Customers | All Customers)

  9. You can also check in the database if you look at the following tables:

    • sales_order

    • customer_entity

    • catalog_product_entity

    • url_rewrite

How it works...

When the migration tool starts, it starts checking all the configurations that are in the configuration files of the migration tool. If there are more things available in the Magento 1 database than the things that are configured, the migration tool will give a notification and stop the migration.

It's likely that every existing Magento 1 shop works with custom attributes, custom entities, and so on. Each entity, attribute, and so on needs to be declared in the configuration files.

The most time-consuming part of a migration is to create a good configuration file so that the migration tool won't fail on missing stuff. It is on you to decide what to ignore and what to migrate. If the configuration files are valid, the migration will start and the data will come into the Magento 2 database. The same principle applies when migrating the settings, but you have to think about whether you want it.

Note

With the migration tool, it is only possible to migrate data and settings. The code of Magento 1 modules will not work in Magento 2. So for your modules, you need to see if there is a Magento 2 version/alternative available.

There's more...

In this recipe, we did a migration of a clean Magento 1 installation to a clean Magento 2 installation. However almost every running Magento 1 shop is not clean. It contains custom attributes, custom modules, and a custom configuration.

When migrating such a shop to a new shop, the migration is a bit more complex. The first question is: What needs to be migrated? With the tool, you can migrate every entity, from products, customers, and orders to reviews, settings, and more.

If you want to skip data that must be migrated, you can use the map.xml file. If you open the file vendor/magento/data-migration-tool/etc/ce-to-ce/packt-migration/map.xml, you see that a lot of entities are ignored in the map/source/document_rules tag.

Tip

If you want to change something in the map.xml file, you have to make sure that the right map.xml file is loaded. This file is configured in the config.xml file (where you did your database configuration). In that file, you have to look for the XML tag config/options/map_file.

If you have an error such as Source documents not mapped, you have to add the configuration for these entities in the map/source/document_rules tag of the map.xml file. If the error is something like Destination documents not mapped, you have to add configuration in the map/destination/document tag of the map.xml file.

To solve errors such as Source fields not mapped you have to add configuration in the map-eav.xml file.

See also

Migrating configuration files is the most time consuming part of a data migration. If you want more information on the migration tool, you can have a look at the Magento Migration Whitepaper, available at http://magento.com/resources/magento-2-migration-whitepaper.

Previous Section
End of Section 6
Next Section