Manual:Moving a wiki/zh

这个页面解释了如何将一个维基移到另一个服务器. 当移动到不同的web服务器或域名（或两者都有）时，这通常是需要的.

最安全的方法是在两个维基上使用同一MediaWiki版本. 但是，在新服务器上安装较新的MediaWiki版本，并直接在新服务器上执行升级也是可行的. 事实上，如果想将维基升级到比旧服务器（如php版本）要求更高的新版本，这可能是您唯一的选择.

这些步骤在其他页面中有基本的解释:


 * 1) 备份你的维基.
 * 2) 将备份从旧服务器传输至新服务器.
 * 3) 在新服务器上恢复备份



升级新服务器
If you are upgrading to a newer MediaWiki version on the new server, instead of copying the old MediaWiki directory and extensions to the new server, you should follow the upgrading procedure. 你将在新服务器上下载MediaWiki的新版本和使用的扩展的新版本，以匹配新的MediaWiki版本. 记得运行升级程序.

注释

 * If the URL has changed (for example, a new domain), be sure to update all references to it in LocalSettings.php. 如需使用可视化编辑器（VisualEditor），你也需要更新Parsoid configuration.
 * Links on cached pages may still point to the old domain. You may need to bump $wgCacheEpoch to discard cached pages prior to that time.
 * Check that the  directory has the correct permissions set if using uploads; it must be writable by the web server.
 * Make sure any extension directories have the correct permissions as well (e.g., if linux: )
 * When manually transferring a wiki from a windows platform to a Linux platform the best method is to:
 * 1) Manually install MediaWiki on the Linux platform from a tar file as outlined here: Manual Install of Wiki (i.e., try not to use install from an automated package)
 * 2) Replace the newly installed MediaWiki folder (e.g., /var/www/mediawiki...) on your Linux machine with the MediaWiki base folder from your windows machine
 * 3) Update your Linux machine's MySQL Database (e.g. wikidb) with the wiki database from your windows machine (i.e., use the backup and restore features of mysql as outlined above)
 * After importing a wiki database, even if the database can work, some minor problems may arise:
 * 1) You might need to repair Searchindex: In phpMyAdmin, enter "  " for rebuilding the search index. wikidb是你的数据库的名称.
 * 2) The collation of some rows may be changed. Cross-check it with the original database.

Test
At this point, try to use the wiki on the new server. Log in as a sysop and a regular user and check that viewing, creating and editing pages and uploading files still works. Fix any problems reported either by PHP or MediaWiki itself.

You can do the entire process to test if the move will work without problems, before actually putting the old wiki in read-only mode. Once you know your wiki in the new server works as expected, you can put your old wiki in read-only mode and perform the move again.



常见问题

 * Inaccessible files after changing the domain

The column md_deps in the module_deps table contains absolute file paths, which are used to locate the images and LESS files that CSS depends on. These paths break when the wiki is, e.g., moved to another folder or another server. After your move, you might see PHP warnings that certain files could not be accessed. In current versions of MediaWiki, this can be solved by running update.php, thus clearing caches.

In versions older than MediaWiki 1.25 (where T37472 is not implemented), update.php does not delete the contents of the module_deps table. For these versions, the workaround is to manually fix wrong entries in the module_deps table:

This can be used to update wrong path segments and to fix the error.

A similar issue can happen when MediaWiki tries to read resource loader messages. In this case the solution is to truncate the according tables:



参见

 * - if you don't have a successful backup
 * - change the installation directory of your wiki
 * - A set of tools to transfer content from one wiki to another if you don't have shell access to the old wiki.
 * - change the installation directory of your wiki
 * - A set of tools to transfer content from one wiki to another if you don't have shell access to the old wiki.
 * - A set of tools to transfer content from one wiki to another if you don't have shell access to the old wiki.



外部链接

 * Detailed instructions on 'Migrating to a new server'
 * Specific page to move easily a wiki (in french)