Drupal 迁移问题 - 安装屏幕显示而不是站点
我们正在将一些旧的 Drupal 安装 (6.x) 从一个托管平台迁移到另一个托管平台。不幸的是，由于政治问题，我们无法在迁移之前升级 Drupal 核心或模块（例如，需要在昨天完成！）。
将所有文件复制到新服务器（在相同位置）并重新导入所需的数据库并修改 settings.php 文件后，当我们访问站点时，显示的就是 Drupal 安装屏幕。
我猜这是某种路径问题，但 settings.php 文件中没有路径。继此处的另一篇文章之后，我意识到我没有带来 .htaccess 文件，但我现在已经这样做了，但仍然没有任何变化。
任何人都可以建议我应该寻找的地方或者我可能错过的步骤吗？
我们正在从 Apache 服务器迁移到 LiteSpeed Web 服务器，但我怀疑这是一个问题。
任何人可以提供的任何帮助将不胜感激。
谢谢 乔什
We are migrating a bit of an old Drupal installation (6.x) from one hosting platform to another. Unfortunately due to political issues we are unable to upgrade the Drupal Core or modules prior to migration (eg. Needs to be done yesterday!).
Having copied all files across to the new server (in the identical location) and also re-imported the required databases and modified the settings.php file when we access the site all that is displayed is the Drupal installation screen.
I'm guessing it's some sort of path issue but there were no paths in the settings.php file. Following another post on here I realised that I hadn't brought across the .htaccess files but I have now done that and still no change.
Can anyone suggest anywhere I should be looking or perhaps a step I have missed?
We are moving from an Apache server to a LiteSpeed Web Server but I doubt that is an issue.
Any help anyone can provide would be hugely appreciated.
Thanks
Josh
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
当 Drupal 可以连接到数据库服务器（因此凭据似乎有效）时，通常会显示安装屏幕，但找不到现有的 Drupal 数据库本身。
因此，您应该检查 settings.php 中的数据库连接设置并验证它是否引用了正确的数据库。您还应该验证数据库是否已正确迁移，以及 Drupal 实例使用的用户是否具有迁移数据库的正确访问权限（尽管后者会导致不同的错误消息 IIRC）。
The install screen is normally shown when Drupal can connect to the database server (so credentials seem to work), but does not find the existing Drupal database itself.
So you should check your database connection settings in settings.php and verify that it references the correct database. You should also verify that the database got migrated correctly, and that the user used by the Drupal instance has the proper access rights for the migrated database (although the latter would result in a different error message, IIRC).