dedecms space migration steps_PHP tutorial

1. Reinstall the original version of DEDECMS in the new space, and then put all the data of the old site. The data here refers to files, that is, except for the configuration file config_base.php in the include folder in the root directory. All other files will be overwritten into the new space

2. Where to back up the data in the old website backend system management - data backup. The data here refers to the backup files taken by DEDECMS's own backend, similar to using tools such as phpmyadmin Backups made. After the backup is completed, DEDECMS will place the backup file in the backup_data folder under the dede directory in the root directory (the default is dede, if you modify it, it will be the directory you modified). You will find many text files.

3. Open the backend on the new website (note: the domain name here has been resolved to the new website), system management - data backup - restore data - start restoring data, just restore directly.

Note: When backing up data, you must pay attention to the backup data format. You must consult the new space provider in advance, and then decide whether to choose 3.x/4.0.x or 4.1.x/5.x version, otherwise the backup is wrong and the old website cannot be accessed, and you will just cry! o(∩_∩)o..

First: Moving between spaces

In fact, it is most convenient when moving between spaces. If you master the steps I mentioned, you will be 100% successful in moving. First, enter the DEDE backend, select System-Database Backup-Select All-and click Start. Here are the steps Check that the corresponding version of your database must be the same as the database version of the new space, otherwise garbled characters will appear. After a while, you will be prompted that all data has been backed up. The time may vary depending on the size of your database. After the backup is completed, open the FTP of your website and see if there is a txt file in the databackupdata directory. This is the data we just backed up. If If you're not sure, you can look at the creation date of the file. Then download the backupdata folder together with its contents to the local area. Continue to download all four folders, images, templets, uploads, and plus, to the local area. Finally, we reinstall the DEDE program in the new space, which should correspond to your version. After installation, overwrite these folders to the root directory, enter the background, select System-Database Restore-Data Restore, and you will see your database. Information, select all and click to start restoring data. It will be finished in a while. Then select your homepage file and update the homepage. Then our space move is completed.

Second: How to move the database if the background cannot be backed up

Due to various reasons, our backend cannot be accessed, or the database cannot be backed up, so how should I move? First, we use PHPMYADMIN to enter the SQL database. This should be done. If not, search on Baidu and select your database. Then back up, export to local, then download all the files in your original space to your new space, continue to open the common.inc.php file in the data folder, and modify your new space database account password and IP , and then cover it, that’s it, but it’s not suitable for novices to use this method. Unless there is really no other way, I recommend the first moving method. This method may have some minor problems. My website was moved from yesterday. The space was moved to the VPS server. Using this method, the background could not be updated, but it was quickly solved. It was a permissions issue.

When building a website, the domain name is generally not very likely to change, but the space may change around. A transfer will involve the general migration of website data. There are many ways to move a website built with the Dedecms content management system, but there are only one or two that are effective.

Since Dedecms is compiled in PHP and requires a MYSQL database to support a website, the WEB page area and the database area are generally not in the same place, unlike Kexin, ZBLOG, Seth, Xinyun, etc. written in ASP programs , WEB pages and ACCESS database exist together, and the entire site can be relocated.

However, friends who have used the WordPress blog program can understand that web pages written in the PHP program open faster than ASP, but the static generation effect is not as good as ASP. What makes people happy is that Dedecms, the content management system of DreamWeaver, can realize full static address of articles, which is really difficult to achieve and valuable.

Moreover, the website created by Dedecms content management system can also be relocated as a whole. The method is as follows:

1. Log in to your DEDECMS backend, find "Database Backup/Restore" in the "System" area, and "back up" the database;

2. Download all the files in the old space to your computer locally;

3. Upload files to the new space;

4. Install the DEDECMS system in the new space. Method - download a new installation system from the official website of Dreamweaver, and transfer the contents of the "install" folder in the system to the space for overwriting. Then, run http://yourdomain/install to install. It should be noted that the prefix of the database table must be consistent with the prefix of the original database table (just follow the default operation);

5. After installation, log in to the backend and click "Database Backup/Restore" in the "System" area to "restore" the data;

6. Data generation and moving work completed.

Of course, there is another way to prevent WordPress blog from moving:

1. Download the files in the old space to the local, and back up MYSQL to the local through PHPADMIN;

2. Upload the website files to the new space and import the database through PHPADMIN;

3. Modify the database name and password filled in during dede installation: Open config_base.php in the "include" directory and download this file

Look for "Database Connection Information", change the following parameters (database name and password), and upload overwrite.

4. The move is completed.

As for which method is best, it depends on the beholder and the wise. Here is a reminder, if your website’s mysql database exceeds 20M, it is best to adopt the first method above (also called the reinstallation method), because some space providers have database import size limits (generally not larger than 20M) - use reinstall You can avoid this restriction by installing it.

dedeCms moving instructions-the official tutorial is definitely detailed enough

Because the mysql database names of different virtual host spaces are different (because their prefixes are different, you will know it after using it),

So you need to back up the database first, then restore it to a new space, and then regenerate the html.

(Note: The versions of the MYSQL database in the new space and the original site must be both 4.1 or above, or 4.0 or below 4.0 to avoid problems. To view the version, you can log in to PHPMyAdmin to see the version)

When reinstalling the same version of dedecms system in a new space,

Of course the database name, database user name and password must be filled in for the new database,

The prefix of the set database table must be consistent with the prefix of the original database table to avoid not seeing the content.

The specifics are as follows:

1. Log in to the backend, back up the database (this database backup file is saved in ../dede/backupdata/), and remember the user name and password for logging in to the backend.

2. Download the database backup file (ie../dede/backupdata/ this folder), website style template file (ie../templets/ this folder), and../upimg/ this folder ( This is the folder where all uploaded files are saved).

3. Reinstall the same version of the dedecms system in the new space. The prefix of the database table set at this time must be consistent with the prefix of the original database table to avoid not seeing the content.

(The database name, database username and password are of course filled in for the new database)

4. Upload the three folders ../dede/backupdata/ and ../templets/ and ../upimg/ of the original site to overwrite the corresponding folders in the new space, thus backing up the database of the original site. The files and website style templates have been placed on the new site.

5. Log in to the new space backend>System Settings>Database Management>Database Restore, restore the database, and then set the "Modify System Parameters" (or "System Variable Configuration") of the website, and regenerate HTML for the entire site That’s it.

After the database is restored, the backend login username and password must use the original website backend login username and password before the backup.

The default character encoding of mysql databases in different spaces is different. In order to prevent garbled characters, you should clearly check the original encoding (usually latin or gbk) when backing up the old database, and check the new one when restoring the database. Does the database support your encoding (some databases do not support gbk). If it supports the same encoding after selecting the recovery, there will be no garbled code problem.