Drupal 6 到 7 迁移

发布于 2024-12-10 08:41:40 字数 290 浏览 0 评论 0原文

我们有一个用 drupal 6 编写的 drupal 站点。我们知道我们必须为 drupal 7 重写它(大部分)

,但最重要的部分是迁移数据。 CCK migrate 只能迁移大约 90% 的田地。

我正在寻找一种干净的方法将 drupal 6 数据迁移到 drupal 7。

我们使用 content_multigroup 作为一个模块,它基本上就像一个字段集合...如何迁移?

我正在寻找一些通用策略...我正在考虑引导 drupal 7 并只针对 drupal 6 数据库编写查询并保存节点。

We have a drupal site written in drupal 6. We know we will have to rewrite it for drupal 7 (mostly)

But the big part is migrating the data. CCK migrate was only able to migrate about 90% of the fields.

I am looking for a clean way to migrate the drupal 6 data to drupal 7.

We used content_multigroup as a module which is basically like a field collection...How would that be migrated?

I am looking for some general strategies...I am thinking of bootstrapping drupal 7 and just write queries against the drupal 6 database and save nodes.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

孤星 2024-12-17 08:41:40

自从提出这个问题以来,Migrate 模块已经发生了很大的变化。此外,迁移 D2D 模块 是 Drupal 6 到 Drupal 7 迁移的一个很好的起点。

查看文档,您应该对如何进行操作有一个很好的了解。

诚然,Migrate 模块似乎有一个陡峭的学习曲线,但使用 Migrate D2D 示例,您应该足够快地掌握速度。

The Migrate module has evolved a lot since this question was asked. Also the Migrate D2D module is a great starting point for a Drupal 6 to Drupal 7 migration.

Check the documentation and you should get a pretty good idea of how to go about it.

Admittedly, the Migrate module seems to have a steep learning curve but using the Migrate D2D Examples you should get up to speed quickly enough.

万人眼中万个我 2024-12-17 08:41:40

将 Drupal6 升级到 Drupal7

对所有文件、目录和数据库进行完整备份

*注意:
在将其应用到实际网站之前,明智的做法是尝试对网站的测试副本进行更新或升级。即使是微小的更新也可能会导致您网站的行为发生变化。

步骤 1:

Make note of non-core drupal modules(no need drupal core modules) and search if that all modules are available in drupal 7. If the modules are not available, then search “is there any alternate module for drupal 7”. Make sure of it. (*step 1 is important)

步骤 2:

Disable all non-core module. 

Drush:      drush pm-disable `drush pm-list --no-core --type=module –pipe`

步骤 3:

Change the default theme as “Garland”.

Drush:      drush vset theme_default garland, drush vset admin_theme garland

步骤 4:

Update the drupal6.

Drush:      drush up drupal

步骤 5:

Dump the DataBase.

Drush:      drush sql-dump > /path-to-dump/my-sql-dump-file-name.sql
Terminal:   mysqldump -u [username] -p [database name] > [database name].sql

步骤 6:

Download the latest Drupal7.

Drush:      drush dl drupal --select`option to select the version`

步骤 7:

Copy “files” folder from old instance(Drupal6) to new instance(Drupal7) and change the folder permissions.

步骤 8:

Import the dumped DB to new instance.

Drush:  (drush sql-drop, drush sql-cli < /path-of-dump/my-sql-dump-file-name.sql)
Terminal:   mysql -u [username] -p newdatabase < [database name].sql

步骤 9:

Go to Drupal Root > sites > default > settings.php and change into $update_free_access to TRUE in the settings file and then run update.php.

步骤 10:

Download all the contributed modules : include `views and views related modules`.  

步骤 11:

Must download Content Construction Kit (CCK) module. Enable the CCK, Content Migrate modules.

Drush:      drush dl cck, drush en cck

Go to “Admin-Structure > Migrate fields”.

步骤 12:

In that Migrate fields,



After enable click “Migrate fields” in “Available fields” the fields are come under the “Converted Fields”. Once again run “update.php”.

*参考此:https://drupal.org /更新/主题/6/7

Upgrade Drupal6 to Drupal7

Make a full backup of all files, directories, and your database(s)

*Notes:
It is wise to try an update or upgrade on a test copy of your site before applying it to your live site. Even minor updates can cause your site's behavior to change.

Step 1:

Make note of non-core drupal modules(no need drupal core modules) and search if that all modules are available in drupal 7. If the modules are not available, then search “is there any alternate module for drupal 7”. Make sure of it. (*step 1 is important)

Step 2:

Disable all non-core module. 

Drush:      drush pm-disable `drush pm-list --no-core --type=module –pipe`

Step 3:

Change the default theme as “Garland”.

Drush:      drush vset theme_default garland, drush vset admin_theme garland

Step 4:

Update the drupal6.

Drush:      drush up drupal

Step 5:

Dump the DataBase.

Drush:      drush sql-dump > /path-to-dump/my-sql-dump-file-name.sql
Terminal:   mysqldump -u [username] -p [database name] > [database name].sql

Step 6:

Download the latest Drupal7.

Drush:      drush dl drupal --select`option to select the version`

Step 7:

Copy “files” folder from old instance(Drupal6) to new instance(Drupal7) and change the folder permissions.

Step 8:

Import the dumped DB to new instance.

Drush:  (drush sql-drop, drush sql-cli < /path-of-dump/my-sql-dump-file-name.sql)
Terminal:   mysql -u [username] -p newdatabase < [database name].sql

Step 9:

Go to Drupal Root > sites > default > settings.php and change into $update_free_access to TRUE in the settings file and then run update.php.

Step 10:

Download all the contributed modules : include `views and views related modules`.  

Step 11:

Must download Content Construction Kit (CCK) module. Enable the CCK, Content Migrate modules.

Drush:      drush dl cck, drush en cck

Go to “Admin-Structure > Migrate fields”.

Step 12:

In that Migrate fields,



After enable click “Migrate fields” in “Available fields” the fields are come under the “Converted Fields”. Once again run “update.php”.

*Refer this: https://drupal.org/update/themes/6/7

落墨 2024-12-17 08:41:40

您是否看过 http://drupal.org/project/feeds (由于其名称,因其作为数据迁移工具的良好用途而经常受到关注)?

您正在处理哪些领域?

如果失败,并且由于您正在寻找通用策略,我会说以下内容:我会鼓励您尽可能使用 API,而不是直接查询。

根据我自己的经验,在两个选项之间进行选择:

a)在 D6 下运行脚本并通过 SQL 推送到 D7 DB
或者
b) 让脚本在 D7 下运行并通过 SQL 拉取到 D6 DB

我会选择 b) 以确保 node_save 最终完成所有工作。

Have you looked at http://drupal.org/project/feeds (which, because of its name, often flies under the radar for its very good use as a data migration tool) ?

What kind of fields are you dealing with?

If that fails, and since you are looking for general strategies, I'll say the following: I would encourage you to use the API, rather than direct queries, as much as possible.

From my own experience, in choosing between the two options:

a) having a script run under D6 and push via SQL to the D7 DB
or
b) having a script run under D7 and pull via SQL to the D6 DB

I would choose b) to make sure that node_save ultimately gets to do all it's work.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文