because the name of the MySQL database varies from one virtual host space to another (because its prefix is different, it is used to know),
So you need to back up the database first, then put it in a new space restore, and then regenerate the HTML.
(Note: The new space and the original site MySQL database version must be more than 4.1, or the same is 4.0, 4.0 or less, to avoid problems.) View version can login phpMyAdmin can see the version is how much)
New space when reinstalling the same version of the DEDECMS system,
The database name and database user name and password are, of course, filled in with a new database,
The database tables that you set must be prefixed with the prefix of the original database table to avoid seeing the content.
This is exactly the case:
1. Login background, BACKUP database (This database backup file is saved in the. /dede/backup_data/), and remember the username and password of the login background.
2. Download the database backup file (ie.. /dede/backup_data/this folder), website style template file (ie.. /templets/this folder), and. /upimg/This folder (this is the folder where all the uploaded files are saved).
3. Reinstall the same version of the DEDECMS system in the new space, at which point the database table must be prefixed with the prefix of the original database table to avoid seeing the content.
(The database name and database user name and password are, of course, filled with the new database.)
4. Upload the original station. /dede/backup_data/and. /templets/and. /upimg/these 3 folders to overwrite the corresponding folders in the new space, so that the original site of the database backup files and website style template to the new station.
5. Log in to the new Space backend > System Settings > Database management > Database restore, restore the database, and then set the site's "Modify system Parameters" (or "System variable Configuration"), the entire station to regenerate the HTML.
After the database recovery, the background login username and password to use the back up the original website login username and password.
different space MySQL database default character encoding is not the same, in order to prevent garbled, you back up the old database when you see the original encoding (usually Latin or GBK), restore the database to see whether the new database supports your encoding (some databases do not support GBK) , if you support the selection of the same encoding after recovery, there will be no garbled problem.
DEDECMS Moving Instructions-Official tutorial is definitely enough detail