Magento documents understanding and moving

fridge magnets -Red appl || tn max




Novice start will always be very confusing scratching their heads, but stick to it, more than the google, multi-try will be successful.
 We first look at magento the original installation package, and we use the period of magento site so what difference
 Differences are as follows:
 A root directory of the media folder there is a site to add commodities picture. (Inside a folder name of the cache, this folder is a picture cache files can be deleted, Magento runtime will automatically re-generated.)
 The root directory of the var folder, the files are cached in the cache and the session folder is cached, it means that you can always delete out. Moving to remember to clear maybe has a file in the file.
 3 in app / design / frontend / default / folder and the skin / frontend / default folder to store the template file that you later installed. For example, your template folder name is the after theme110 then install it, the template path should be app/design/frontend/default/theme110 and skin/frontend/default/theme110.
 The most exceptional circumstances, you get the template file is not in this folder. But you and the original skin / frontend / folder content magento file comparison will find his location.
 Sometimes the template also contains the plug-in is part of the template. In general, if the template file contains the file app / code / community or the app / code / local is to say, this template with a plug-in.
 Stored in app / code / community and app / code / local file folder with the main file of the plug-in, plug-in configuration file in the app / etc / modules.
 5 to install the plug should pay attention to some plug-in template files, general plug-in template files in app / design / frontend / default / default and skin / the frontend / default / default ie, the default template.
 6. Installed magento appears the app / etc / local.xml file so the file, this file contains the configuration information of magento, such as the address of the database, database user name, password, table prefix, site background address address. This file is created automatically magento installation. When magento undetectable this file exists, it will enter the setup page. So when the time of moving our website, we will be the original site local.xml rename in order to once again let magento into the setup page, configure the new server and database information.
 The 7.magento the database contains magento products, classification, user information, order information, the information of the previous plug-in, so moving the entire database to transfer to the new server to re-enter the installation page in magento, fill out a new database information.
 Introduced as mentioned above, how to give our magento move?

The original site file var file in the cache and session files to be deleted, delete the cache files in the media. And production of all documents into a single compressed package in order to reduce the file size to facilitate the transfer.
 2 compressed package transferred to the new server domain name to point to the file folder, unzip it.
 The unpacked file is corrupted the correct file permissions (file permissions problem).
 Export magento database using phpmyadmin export, reference articles: http://www.hellokeykey.com/magento-export-database-via-phpmyadmin/
 Note: look at your database with or without table prefix, write in the first step.
 5 in the new space to create a new database, import the backup data file.
 6. The app / etc / local.xml file so the file rename.
 This file also contains the database table prefix, rename, open look.
<resources> <db> <table_prefix> <! [CDATA [mage_]]> </ table_prefix> </ db> <default_setup> <connection> <host> <! [CDATA [localhost]]> </ host> <username > <! [CDATA [chiqingm_mage2]]> </ username> <password> <! [CDATA [AcccPuPg654]]> </ password> <dbname> <! [CDATA [sdw_mage2]]> </ dbname> <active> 1 </ active> </ connection> </ default_setup> </ resources>
the <table_prefix> <! [CDATA [here the contents of the table prefix]]> </ table_prefix in the above code, this database table prefix mage_ the7 Check the var folder in the cache and the session folder is already empty.
 URL to access your site into the magento installation page.
 9 to fill in the database that step, write the first four steps of the new name of the database, user name, password, table prefix information. Note to view your database with or without table prefix, or magento will re-create all the tables.
 10 after the end of the installation into the background to refresh the next cache and index management.
 11 at the front desk to check whether there is strange. If some image not displaying properly, check whether the use of a fixed link, causing the image is invalid because the domain name to replace.


 Added:
 Why magento move to have all the website files to be transferred together, because your magento site may be in the process, unknowingly modify files outside some template files, but you can not be screened which is to turn over. All files with the move is the most hassle free.
 In general, the move if only to transfer the template file will be a lot of problems. Some template or plug-in will have a file stored in the folder I did not mention above, if you move only transfer media folder the app and skin template file will be a problem because the file did not transfer complete.
 Whether to do what must be the first backup, before moving on to do the next backup should the original site. If you use the space with one-button backup, this will be very simple.