Home  >  Article  >  Backend Development  >  Detailed explanation of dedecms space migration steps_PHP tutorial

Detailed explanation of dedecms space migration steps_PHP tutorial

WBOY
WBOYOriginal
2016-07-21 15:10:09803browse

1.在新空间重新安装一次原版本的DEDECMS,然后把旧站的所有数据,这里的数据指的是文件,即除了根目录下文件夹include下的配置文件config_base.php外的所有文件覆盖到新空间下

2.在旧网站后台系统管理-数据备份哪里备份数据,这里的数据指的是DEDECMS自己后台所采取的备份文件,类似用phpmyadmin等工具所作的备份。备份完成后,DEDECMS会将备份文件放到根目录下的dede目录(默认是dede,如果你修改了,就是你修改后的目录)下的backup_data文件夹里面,你会发现是许多文本文件。

3.在新网站打开后台(注:这里域名已经解析到新站),系统管理-数据备份-还原数据-开始还原数据,直接还原就行了。

注意:备份数据的时候指定备份数据格式那里一定要注意,一定要提前咨询新空间商,然后在决定是选择3.x/4.0.x还是选择4.1.x/5.x版本,不然备份错误,老网站又进不去,你就等着哭吧!o(∩_∩)o..

第一 : 空间和空间之间搬家

其实空间和空间之间搬家时最方便的,大家掌握好我说的步骤,100%能成功搬家,首先大家进入DEDE后台,选择系统-数据库备份-全选-然后点开始,这里要看下你的数据库对应版本要和新空间的数据库版本一样才可以,不然会出现乱码。等一会就会提示所有数据备份完毕,根据你的数据库大小时间不一定,备份完后,大家打开你网站的FTP,看一下data\backupdata目录中有txt文件,这就是我们刚才备份的数据了,如果不确定话可以看一下文件的创建日期。然后把这个backupdata文件夹连同的内容一起下载到本地,继续,把images,templets,uploads,plus这4个文件夹全部下载到本地。最后我们把新空间重新安装 DEDE程序,要对应你的版本,安装好后,把这几个文件夹覆盖到根目录,进入后台,选择系统-数据库还原-数据还原,就会看到你的数据库信息,全选后点击开始还原数据,一会就完了,然后选择你的首页文件,更新首页就OK了,这样我们的空间搬家就完成了。

第二:后台无法备份数据库怎样搬家

由于种种原因,我们的后台进不去了,或者数据库无法备份,那么我应该怎么搬家那?首先我们用PHPMYADMIN进入SQL数据库,这个应该都会把,不会的话百度一下,选择你的数据库然后备份,导出到本地,然后把你原来空间的所有文件全部下载到你的新空间中,继续打data这个文件夹当中的 common.inc.php这个文件,修改你的新空间数据库账户密码和IP,然后覆盖,这样就可以了,但是不适合菜鸟使用这种方法,除非真的没办法了,推荐第一种搬家方法,这一种方法多多少少可能有点小问题,我的网站就是昨天从空间搬到了VPS服务器,用这种方法出现了后台无法更新,不过很快解决了,是权限的问题。

做网站,域名一般变动能性不大,空间却可能转来转去。一转就要涉及网站数据的般迁。以织梦内容管理系统Dedecms搭建的网站搬起家来方法不少,但有效的也只有一两种。

由于Dedecms是用PHP编制,且需要MYSQL数据库才能撑起一个网站,WEB网页区与数据据库区一般不在同一地方,不象ASP程序编写的科汛、ZBLOG、赛特、新云等,WEB网页与ACCESS数据库是存在一起的,可以整站搬迁。

但是,使用过Wordpress博客程序的朋友,大可以明白,PHP程序编写的网页打开的速度较ASP快一点,但静态生成效果不及ASP。让人庆喜的是织梦内容管理系统Dedecms可以实现文章地址全静态化,实是难通可贵。

而且,织梦内容管理系统Dedecms做出来的网站也可以整站搬迁,方法如下:

一、登陆你的DEDECMS后台,在“系统”区找到“数据库备份/还原”,将数据库进行“备份”;

二、将老空间里所有的文件,全部下载至你的电脑本地;

三、将文件上传至新空间;

四、在新空间安装DEDECMS系统,方法——在织梦的官方网站下载一个新的安装系统,将系统里的“install”文件夹里的东西传至空间,进行覆盖。接着,运行http://你的域名/install,进行安装。需要注意的是:数据库表的前缀必须和原数据库表的前缀必须一致(按默认操作即可);

五、安装完后,登陆后台,点击“系统”区的“数据库备份/还原”,将数据进行“还原”;

六、数据生成,搬家工作完成。

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 what the version is)

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.

(Of course the database name, database username and password must be 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.

www.bkjia.comtruehttp: //www.bkjia.com/PHPjc/327136.htmlTechArticle1. Reinstall the original version of DEDECMS in the new space, and then put all the data of the old site into the data here Refers to files, that is, except the configuration file conf under the include folder in the root directory...
Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn