How to configure an existing Magento 2.1.7 project in another PC and Database?How to setup magento 2.1 from existing projectMagento 2 Version Update Dilemma (Cloned from Git Repo)Magento > 2.1.7 admin 404 (2.1.8 and 2.1.9)Magento 2 failed database rollback cannot add foreign key constraintsClone Magento 2 respository from git causing installing new project not loading existingMagento 2 InvalidArgumentException Could not find a matching version of packageUpgrading Magento 2.1.7 to 2.1.14Magento 2 How to added languages packs to git repo?magento 2 lost code for EAV attributesThe table Customer_grid_flat is deleted magento 2
Is it acceptable to use working hours to read general interest books?
I preordered a game on my Xbox while on the home screen of my friend's account. Which of us owns the game?
Why did Rep. Omar conclude her criticism of US troops with the phrase "NotTodaySatan"?
How bug prioritization works in agile projects vs non agile
Cayley's Matrix Notation
Contradiction proof for inequality of P and NP?
Retract an already submitted recommendation letter (written for an undergrad student)
Is this a typo in Section 1.8.1 Mathematics for Computer Science?
How long after the last departure shall the airport stay open for an emergency return?
How much of a wave function must reside inside event horizon for it to be consumed by the black hole?
Trouble removing package using Yum on CentOS7
A Note on N!
What makes accurate emulation of old systems a difficult task?
Why is the underscore command _ useful?
Why must Chinese maps be obfuscated?
Are there moral objections to a life motivated purely by money? How to sway a person from this lifestyle?
What to do with someone that cheated their way through university and a PhD program?
Determine the application client is using to connect
How do I reattach a shelf to the wall when it ripped out of the wall?
Could moose/elk survive in the Amazon forest?
What is this word supposed to be?
"The cow" OR "a cow" OR "cows" in this context
Multiple fireplaces in an apartment building?
Can a barbarian keep raging if she shoves an enemy on her turn?
How to configure an existing Magento 2.1.7 project in another PC and Database?
How to setup magento 2.1 from existing projectMagento 2 Version Update Dilemma (Cloned from Git Repo)Magento > 2.1.7 admin 404 (2.1.8 and 2.1.9)Magento 2 failed database rollback cannot add foreign key constraintsClone Magento 2 respository from git causing installing new project not loading existingMagento 2 InvalidArgumentException Could not find a matching version of packageUpgrading Magento 2.1.7 to 2.1.14Magento 2 How to added languages packs to git repo?magento 2 lost code for EAV attributesThe table Customer_grid_flat is deleted magento 2
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am new to Magento.
I have a working Magento 2.1.7 project and want to put it in a git repository.
If I put the working Magento directory into git and clone the repository to a local machine how do I install the existing project and do the database configuration?
I tried copy pasting the existing repository to another machine and tried to install it by following the normal procedure but it didn't work, instead I got this error:
An error has happened during application run. See exception log for details.
I also tried to import the database as well but I got this error while importing:
Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in <b>Unknown</b> on line <b>0</b><br /> SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"
I extended the max_input_vars
to 10000 in the php.ini file but still, I get the same error.
Please suggest me about how can I configure and install an existing Magento 2.1.7 project ** because I want to put the working project to GIT for my team to work with !**.
magento2 magento-2.1 magento-2.1.7
bumped to the homepage by Community♦ 2 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am new to Magento.
I have a working Magento 2.1.7 project and want to put it in a git repository.
If I put the working Magento directory into git and clone the repository to a local machine how do I install the existing project and do the database configuration?
I tried copy pasting the existing repository to another machine and tried to install it by following the normal procedure but it didn't work, instead I got this error:
An error has happened during application run. See exception log for details.
I also tried to import the database as well but I got this error while importing:
Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in <b>Unknown</b> on line <b>0</b><br /> SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"
I extended the max_input_vars
to 10000 in the php.ini file but still, I get the same error.
Please suggest me about how can I configure and install an existing Magento 2.1.7 project ** because I want to put the working project to GIT for my team to work with !**.
magento2 magento-2.1 magento-2.1.7
bumped to the homepage by Community♦ 2 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Could you update your question with the errors you get in the exception log?
– diazwatson
Aug 16 '17 at 10:48
add a comment |
I am new to Magento.
I have a working Magento 2.1.7 project and want to put it in a git repository.
If I put the working Magento directory into git and clone the repository to a local machine how do I install the existing project and do the database configuration?
I tried copy pasting the existing repository to another machine and tried to install it by following the normal procedure but it didn't work, instead I got this error:
An error has happened during application run. See exception log for details.
I also tried to import the database as well but I got this error while importing:
Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in <b>Unknown</b> on line <b>0</b><br /> SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"
I extended the max_input_vars
to 10000 in the php.ini file but still, I get the same error.
Please suggest me about how can I configure and install an existing Magento 2.1.7 project ** because I want to put the working project to GIT for my team to work with !**.
magento2 magento-2.1 magento-2.1.7
I am new to Magento.
I have a working Magento 2.1.7 project and want to put it in a git repository.
If I put the working Magento directory into git and clone the repository to a local machine how do I install the existing project and do the database configuration?
I tried copy pasting the existing repository to another machine and tried to install it by following the normal procedure but it didn't work, instead I got this error:
An error has happened during application run. See exception log for details.
I also tried to import the database as well but I got this error while importing:
Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in <b>Unknown</b> on line <b>0</b><br /> SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"
I extended the max_input_vars
to 10000 in the php.ini file but still, I get the same error.
Please suggest me about how can I configure and install an existing Magento 2.1.7 project ** because I want to put the working project to GIT for my team to work with !**.
magento2 magento-2.1 magento-2.1.7
magento2 magento-2.1 magento-2.1.7
edited Aug 16 '17 at 11:11
diazwatson
1,59411425
1,59411425
asked Aug 16 '17 at 8:02
kaushik kumar roykaushik kumar roy
329
329
bumped to the homepage by Community♦ 2 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 2 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Could you update your question with the errors you get in the exception log?
– diazwatson
Aug 16 '17 at 10:48
add a comment |
Could you update your question with the errors you get in the exception log?
– diazwatson
Aug 16 '17 at 10:48
Could you update your question with the errors you get in the exception log?
– diazwatson
Aug 16 '17 at 10:48
Could you update your question with the errors you get in the exception log?
– diazwatson
Aug 16 '17 at 10:48
add a comment |
2 Answers
2
active
oldest
votes
Change folllowing in php.ini and restart server.
memory_limit to 1G
post_max_size = 50M
upload_max_filesize = 50M
and also change max_execution_time to maximum time like 100 etc.
Also assign permissions to var and pub folders for this error
An error has happened during application run. See exception log for details.
add a comment |
First of all, make sure that you have set the proper settings in php.ini configuration file. To see the recommended settings, please check this out:
http://devdocs.magento.com/guides/v2.0/install-gde/trouble/php/tshoot_php-set.html
Now make sure you have installed composer and other required PHP extensions (install missing PHP extensions). You can check out the system requirements for Magento 2 here:
http://devdocs.magento.com/guides/v2.0/install-gde/system-requirements-tech.html
Next, check out your files and folder permissions. Magento uses a three-bit mask that you subtract from the UNIX defaults of 666 for files and 777 for directories. Here’s what that means:
775 for directories, which means full control by the user, complete
control by the group, and enables everyone to traverse the directory.
Shared hosting providers typically require these permissions.664 for files, which means writable by the user, writable by the
group, and read-only for everyone else.
After making sure of all the above things, migrate your Magento 2 store from one location to another with the following steps:
1. Export Magento 2 Database
By default, you may have PHPMyAdmin
or a similar tool that is capable of exporting your database. Open your database tool and export your Magento 2 database in the .sql
file format, because most of the database tools support the .sql
file.
2. Backup and Transfer Magento 2 Files & Folders
After exporting your database, now you will need to download all files & folders of Magento 2 from your current location and upload them to the new location. It might be a time-consuming task, as it depends on how big your Magento 2 store is. If possible, a good approach is to create a zip archive of the files & folders before downloading them.
Go to Magento 2 installation directory, create a zip archive of all the files & folders and then download it.
Upload the downloaded zip file to the new location and extract it to the new desired destination folder for the Magento 2.
3. Import Magento 2 Database
Once you have transferred the Magento 2 files & folders, you should import the database to the new server. Go to the PHPMyAdmin
, create a new database. Assign credentials to the database or create new username and password for it. In step 1, as we had already exported the database, import the database .sql
file into this new database.
4. Edit Magento 2 Configurations
We are done with exchanging files between both the locations. Now it’s the time to configure your Magento 2 store with your new location. First, you need to edit the app/etc/env.php
file with new Magento 2 database configurations according to your new server. Open the env.php
file and alter the lines below:
‘db’ =>
array (
‘table_prefix’ => ”,
‘connection’ =>
array (
‘default’ =>
array (
‘host’ => ‘DATABASE_HOST’,
‘dbname’ => ‘DATABASE_NAME’,
‘username’ => ‘DATABASE_USERNAME’,
‘password’ => ‘DATABASE_PASSWORD’,
‘active’ => ‘1’,
),
),
),
Where:
‘host’
is the database hostname. Most commonly used host is “localhost”.
‘dbname’
is the database name. Use the one you had created in step 3.
‘username’
is a username that has full privileges to your new database.
‘password’
is the password for that particular database user.
New server means new domain name. You have to replace old server domain name with new domain name. For this, you need to modify the value of web/unsecure/base_url
and web/secure/base_url
in core_config_data
table. Enter the new domain name in the value column for both records.
5. Clear Magento 2 Cache, Sessions and Deploy Static Content
The final step is to clear the Magento 2 cache and deploy static content. Go to following paths and delete everything:
ROOT > var > cache > *DELETE ALL*
ROOT > var > page_cache > *DELETE ALL*
ROOT > var > session > *DELETE ALL*
ROOT > pub > static > DELETE ALL EXCEPT .HTACCESS
Now, we are setting up static content to deploy on our Magento 2 store. To perform this task, using Command Prompt, navigate to the installation directory of Magento 2 and run the following Magento 2 CLI Command:
php bin/magento setup:static-content:deploy
If you get any error, check your PHP.EXE and PHP.INI Environment
Variable
Next, flush Magento cache by running php bin/magento cache:flush
in CMD.
And finally, to Reindex Magento Static Blocks run php bin/magento indexer:reindex
command.
You are done with successful migration of Magento 2 store. If you face any issue, do not hesitate to comment!
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "479"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f189259%2fhow-to-configure-an-existing-magento-2-1-7-project-in-another-pc-and-database%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Change folllowing in php.ini and restart server.
memory_limit to 1G
post_max_size = 50M
upload_max_filesize = 50M
and also change max_execution_time to maximum time like 100 etc.
Also assign permissions to var and pub folders for this error
An error has happened during application run. See exception log for details.
add a comment |
Change folllowing in php.ini and restart server.
memory_limit to 1G
post_max_size = 50M
upload_max_filesize = 50M
and also change max_execution_time to maximum time like 100 etc.
Also assign permissions to var and pub folders for this error
An error has happened during application run. See exception log for details.
add a comment |
Change folllowing in php.ini and restart server.
memory_limit to 1G
post_max_size = 50M
upload_max_filesize = 50M
and also change max_execution_time to maximum time like 100 etc.
Also assign permissions to var and pub folders for this error
An error has happened during application run. See exception log for details.
Change folllowing in php.ini and restart server.
memory_limit to 1G
post_max_size = 50M
upload_max_filesize = 50M
and also change max_execution_time to maximum time like 100 etc.
Also assign permissions to var and pub folders for this error
An error has happened during application run. See exception log for details.
answered Aug 16 '17 at 10:19
Ashar RiazAshar Riaz
508519
508519
add a comment |
add a comment |
First of all, make sure that you have set the proper settings in php.ini configuration file. To see the recommended settings, please check this out:
http://devdocs.magento.com/guides/v2.0/install-gde/trouble/php/tshoot_php-set.html
Now make sure you have installed composer and other required PHP extensions (install missing PHP extensions). You can check out the system requirements for Magento 2 here:
http://devdocs.magento.com/guides/v2.0/install-gde/system-requirements-tech.html
Next, check out your files and folder permissions. Magento uses a three-bit mask that you subtract from the UNIX defaults of 666 for files and 777 for directories. Here’s what that means:
775 for directories, which means full control by the user, complete
control by the group, and enables everyone to traverse the directory.
Shared hosting providers typically require these permissions.664 for files, which means writable by the user, writable by the
group, and read-only for everyone else.
After making sure of all the above things, migrate your Magento 2 store from one location to another with the following steps:
1. Export Magento 2 Database
By default, you may have PHPMyAdmin
or a similar tool that is capable of exporting your database. Open your database tool and export your Magento 2 database in the .sql
file format, because most of the database tools support the .sql
file.
2. Backup and Transfer Magento 2 Files & Folders
After exporting your database, now you will need to download all files & folders of Magento 2 from your current location and upload them to the new location. It might be a time-consuming task, as it depends on how big your Magento 2 store is. If possible, a good approach is to create a zip archive of the files & folders before downloading them.
Go to Magento 2 installation directory, create a zip archive of all the files & folders and then download it.
Upload the downloaded zip file to the new location and extract it to the new desired destination folder for the Magento 2.
3. Import Magento 2 Database
Once you have transferred the Magento 2 files & folders, you should import the database to the new server. Go to the PHPMyAdmin
, create a new database. Assign credentials to the database or create new username and password for it. In step 1, as we had already exported the database, import the database .sql
file into this new database.
4. Edit Magento 2 Configurations
We are done with exchanging files between both the locations. Now it’s the time to configure your Magento 2 store with your new location. First, you need to edit the app/etc/env.php
file with new Magento 2 database configurations according to your new server. Open the env.php
file and alter the lines below:
‘db’ =>
array (
‘table_prefix’ => ”,
‘connection’ =>
array (
‘default’ =>
array (
‘host’ => ‘DATABASE_HOST’,
‘dbname’ => ‘DATABASE_NAME’,
‘username’ => ‘DATABASE_USERNAME’,
‘password’ => ‘DATABASE_PASSWORD’,
‘active’ => ‘1’,
),
),
),
Where:
‘host’
is the database hostname. Most commonly used host is “localhost”.
‘dbname’
is the database name. Use the one you had created in step 3.
‘username’
is a username that has full privileges to your new database.
‘password’
is the password for that particular database user.
New server means new domain name. You have to replace old server domain name with new domain name. For this, you need to modify the value of web/unsecure/base_url
and web/secure/base_url
in core_config_data
table. Enter the new domain name in the value column for both records.
5. Clear Magento 2 Cache, Sessions and Deploy Static Content
The final step is to clear the Magento 2 cache and deploy static content. Go to following paths and delete everything:
ROOT > var > cache > *DELETE ALL*
ROOT > var > page_cache > *DELETE ALL*
ROOT > var > session > *DELETE ALL*
ROOT > pub > static > DELETE ALL EXCEPT .HTACCESS
Now, we are setting up static content to deploy on our Magento 2 store. To perform this task, using Command Prompt, navigate to the installation directory of Magento 2 and run the following Magento 2 CLI Command:
php bin/magento setup:static-content:deploy
If you get any error, check your PHP.EXE and PHP.INI Environment
Variable
Next, flush Magento cache by running php bin/magento cache:flush
in CMD.
And finally, to Reindex Magento Static Blocks run php bin/magento indexer:reindex
command.
You are done with successful migration of Magento 2 store. If you face any issue, do not hesitate to comment!
add a comment |
First of all, make sure that you have set the proper settings in php.ini configuration file. To see the recommended settings, please check this out:
http://devdocs.magento.com/guides/v2.0/install-gde/trouble/php/tshoot_php-set.html
Now make sure you have installed composer and other required PHP extensions (install missing PHP extensions). You can check out the system requirements for Magento 2 here:
http://devdocs.magento.com/guides/v2.0/install-gde/system-requirements-tech.html
Next, check out your files and folder permissions. Magento uses a three-bit mask that you subtract from the UNIX defaults of 666 for files and 777 for directories. Here’s what that means:
775 for directories, which means full control by the user, complete
control by the group, and enables everyone to traverse the directory.
Shared hosting providers typically require these permissions.664 for files, which means writable by the user, writable by the
group, and read-only for everyone else.
After making sure of all the above things, migrate your Magento 2 store from one location to another with the following steps:
1. Export Magento 2 Database
By default, you may have PHPMyAdmin
or a similar tool that is capable of exporting your database. Open your database tool and export your Magento 2 database in the .sql
file format, because most of the database tools support the .sql
file.
2. Backup and Transfer Magento 2 Files & Folders
After exporting your database, now you will need to download all files & folders of Magento 2 from your current location and upload them to the new location. It might be a time-consuming task, as it depends on how big your Magento 2 store is. If possible, a good approach is to create a zip archive of the files & folders before downloading them.
Go to Magento 2 installation directory, create a zip archive of all the files & folders and then download it.
Upload the downloaded zip file to the new location and extract it to the new desired destination folder for the Magento 2.
3. Import Magento 2 Database
Once you have transferred the Magento 2 files & folders, you should import the database to the new server. Go to the PHPMyAdmin
, create a new database. Assign credentials to the database or create new username and password for it. In step 1, as we had already exported the database, import the database .sql
file into this new database.
4. Edit Magento 2 Configurations
We are done with exchanging files between both the locations. Now it’s the time to configure your Magento 2 store with your new location. First, you need to edit the app/etc/env.php
file with new Magento 2 database configurations according to your new server. Open the env.php
file and alter the lines below:
‘db’ =>
array (
‘table_prefix’ => ”,
‘connection’ =>
array (
‘default’ =>
array (
‘host’ => ‘DATABASE_HOST’,
‘dbname’ => ‘DATABASE_NAME’,
‘username’ => ‘DATABASE_USERNAME’,
‘password’ => ‘DATABASE_PASSWORD’,
‘active’ => ‘1’,
),
),
),
Where:
‘host’
is the database hostname. Most commonly used host is “localhost”.
‘dbname’
is the database name. Use the one you had created in step 3.
‘username’
is a username that has full privileges to your new database.
‘password’
is the password for that particular database user.
New server means new domain name. You have to replace old server domain name with new domain name. For this, you need to modify the value of web/unsecure/base_url
and web/secure/base_url
in core_config_data
table. Enter the new domain name in the value column for both records.
5. Clear Magento 2 Cache, Sessions and Deploy Static Content
The final step is to clear the Magento 2 cache and deploy static content. Go to following paths and delete everything:
ROOT > var > cache > *DELETE ALL*
ROOT > var > page_cache > *DELETE ALL*
ROOT > var > session > *DELETE ALL*
ROOT > pub > static > DELETE ALL EXCEPT .HTACCESS
Now, we are setting up static content to deploy on our Magento 2 store. To perform this task, using Command Prompt, navigate to the installation directory of Magento 2 and run the following Magento 2 CLI Command:
php bin/magento setup:static-content:deploy
If you get any error, check your PHP.EXE and PHP.INI Environment
Variable
Next, flush Magento cache by running php bin/magento cache:flush
in CMD.
And finally, to Reindex Magento Static Blocks run php bin/magento indexer:reindex
command.
You are done with successful migration of Magento 2 store. If you face any issue, do not hesitate to comment!
add a comment |
First of all, make sure that you have set the proper settings in php.ini configuration file. To see the recommended settings, please check this out:
http://devdocs.magento.com/guides/v2.0/install-gde/trouble/php/tshoot_php-set.html
Now make sure you have installed composer and other required PHP extensions (install missing PHP extensions). You can check out the system requirements for Magento 2 here:
http://devdocs.magento.com/guides/v2.0/install-gde/system-requirements-tech.html
Next, check out your files and folder permissions. Magento uses a three-bit mask that you subtract from the UNIX defaults of 666 for files and 777 for directories. Here’s what that means:
775 for directories, which means full control by the user, complete
control by the group, and enables everyone to traverse the directory.
Shared hosting providers typically require these permissions.664 for files, which means writable by the user, writable by the
group, and read-only for everyone else.
After making sure of all the above things, migrate your Magento 2 store from one location to another with the following steps:
1. Export Magento 2 Database
By default, you may have PHPMyAdmin
or a similar tool that is capable of exporting your database. Open your database tool and export your Magento 2 database in the .sql
file format, because most of the database tools support the .sql
file.
2. Backup and Transfer Magento 2 Files & Folders
After exporting your database, now you will need to download all files & folders of Magento 2 from your current location and upload them to the new location. It might be a time-consuming task, as it depends on how big your Magento 2 store is. If possible, a good approach is to create a zip archive of the files & folders before downloading them.
Go to Magento 2 installation directory, create a zip archive of all the files & folders and then download it.
Upload the downloaded zip file to the new location and extract it to the new desired destination folder for the Magento 2.
3. Import Magento 2 Database
Once you have transferred the Magento 2 files & folders, you should import the database to the new server. Go to the PHPMyAdmin
, create a new database. Assign credentials to the database or create new username and password for it. In step 1, as we had already exported the database, import the database .sql
file into this new database.
4. Edit Magento 2 Configurations
We are done with exchanging files between both the locations. Now it’s the time to configure your Magento 2 store with your new location. First, you need to edit the app/etc/env.php
file with new Magento 2 database configurations according to your new server. Open the env.php
file and alter the lines below:
‘db’ =>
array (
‘table_prefix’ => ”,
‘connection’ =>
array (
‘default’ =>
array (
‘host’ => ‘DATABASE_HOST’,
‘dbname’ => ‘DATABASE_NAME’,
‘username’ => ‘DATABASE_USERNAME’,
‘password’ => ‘DATABASE_PASSWORD’,
‘active’ => ‘1’,
),
),
),
Where:
‘host’
is the database hostname. Most commonly used host is “localhost”.
‘dbname’
is the database name. Use the one you had created in step 3.
‘username’
is a username that has full privileges to your new database.
‘password’
is the password for that particular database user.
New server means new domain name. You have to replace old server domain name with new domain name. For this, you need to modify the value of web/unsecure/base_url
and web/secure/base_url
in core_config_data
table. Enter the new domain name in the value column for both records.
5. Clear Magento 2 Cache, Sessions and Deploy Static Content
The final step is to clear the Magento 2 cache and deploy static content. Go to following paths and delete everything:
ROOT > var > cache > *DELETE ALL*
ROOT > var > page_cache > *DELETE ALL*
ROOT > var > session > *DELETE ALL*
ROOT > pub > static > DELETE ALL EXCEPT .HTACCESS
Now, we are setting up static content to deploy on our Magento 2 store. To perform this task, using Command Prompt, navigate to the installation directory of Magento 2 and run the following Magento 2 CLI Command:
php bin/magento setup:static-content:deploy
If you get any error, check your PHP.EXE and PHP.INI Environment
Variable
Next, flush Magento cache by running php bin/magento cache:flush
in CMD.
And finally, to Reindex Magento Static Blocks run php bin/magento indexer:reindex
command.
You are done with successful migration of Magento 2 store. If you face any issue, do not hesitate to comment!
First of all, make sure that you have set the proper settings in php.ini configuration file. To see the recommended settings, please check this out:
http://devdocs.magento.com/guides/v2.0/install-gde/trouble/php/tshoot_php-set.html
Now make sure you have installed composer and other required PHP extensions (install missing PHP extensions). You can check out the system requirements for Magento 2 here:
http://devdocs.magento.com/guides/v2.0/install-gde/system-requirements-tech.html
Next, check out your files and folder permissions. Magento uses a three-bit mask that you subtract from the UNIX defaults of 666 for files and 777 for directories. Here’s what that means:
775 for directories, which means full control by the user, complete
control by the group, and enables everyone to traverse the directory.
Shared hosting providers typically require these permissions.664 for files, which means writable by the user, writable by the
group, and read-only for everyone else.
After making sure of all the above things, migrate your Magento 2 store from one location to another with the following steps:
1. Export Magento 2 Database
By default, you may have PHPMyAdmin
or a similar tool that is capable of exporting your database. Open your database tool and export your Magento 2 database in the .sql
file format, because most of the database tools support the .sql
file.
2. Backup and Transfer Magento 2 Files & Folders
After exporting your database, now you will need to download all files & folders of Magento 2 from your current location and upload them to the new location. It might be a time-consuming task, as it depends on how big your Magento 2 store is. If possible, a good approach is to create a zip archive of the files & folders before downloading them.
Go to Magento 2 installation directory, create a zip archive of all the files & folders and then download it.
Upload the downloaded zip file to the new location and extract it to the new desired destination folder for the Magento 2.
3. Import Magento 2 Database
Once you have transferred the Magento 2 files & folders, you should import the database to the new server. Go to the PHPMyAdmin
, create a new database. Assign credentials to the database or create new username and password for it. In step 1, as we had already exported the database, import the database .sql
file into this new database.
4. Edit Magento 2 Configurations
We are done with exchanging files between both the locations. Now it’s the time to configure your Magento 2 store with your new location. First, you need to edit the app/etc/env.php
file with new Magento 2 database configurations according to your new server. Open the env.php
file and alter the lines below:
‘db’ =>
array (
‘table_prefix’ => ”,
‘connection’ =>
array (
‘default’ =>
array (
‘host’ => ‘DATABASE_HOST’,
‘dbname’ => ‘DATABASE_NAME’,
‘username’ => ‘DATABASE_USERNAME’,
‘password’ => ‘DATABASE_PASSWORD’,
‘active’ => ‘1’,
),
),
),
Where:
‘host’
is the database hostname. Most commonly used host is “localhost”.
‘dbname’
is the database name. Use the one you had created in step 3.
‘username’
is a username that has full privileges to your new database.
‘password’
is the password for that particular database user.
New server means new domain name. You have to replace old server domain name with new domain name. For this, you need to modify the value of web/unsecure/base_url
and web/secure/base_url
in core_config_data
table. Enter the new domain name in the value column for both records.
5. Clear Magento 2 Cache, Sessions and Deploy Static Content
The final step is to clear the Magento 2 cache and deploy static content. Go to following paths and delete everything:
ROOT > var > cache > *DELETE ALL*
ROOT > var > page_cache > *DELETE ALL*
ROOT > var > session > *DELETE ALL*
ROOT > pub > static > DELETE ALL EXCEPT .HTACCESS
Now, we are setting up static content to deploy on our Magento 2 store. To perform this task, using Command Prompt, navigate to the installation directory of Magento 2 and run the following Magento 2 CLI Command:
php bin/magento setup:static-content:deploy
If you get any error, check your PHP.EXE and PHP.INI Environment
Variable
Next, flush Magento cache by running php bin/magento cache:flush
in CMD.
And finally, to Reindex Magento Static Blocks run php bin/magento indexer:reindex
command.
You are done with successful migration of Magento 2 store. If you face any issue, do not hesitate to comment!
answered Aug 16 '17 at 16:33
Fayyaz KhattakFayyaz Khattak
1,5611022
1,5611022
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f189259%2fhow-to-configure-an-existing-magento-2-1-7-project-in-another-pc-and-database%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Could you update your question with the errors you get in the exception log?
– diazwatson
Aug 16 '17 at 10:48