Drupal 内容访问问题
我最近刚刚尝试将访问内容模块安装到 Drupal 5。该模块无法正常工作，并且我无法在不出现内部服务器错误的情况下卸载该模块。
因为我对这个模块很感兴趣，所以我现在必须尝试使用它。
现在，当匿名用户查看具有特定 field_name 的页面时，我会收到此错误，该页面连接到我无法授予完全访问权限的内容类型。
用户警告：where 子句中的列“nid”是不明确的查询：SELECT 标题 FROM 节点 INNER JOIN node_access na ON na.nid = n.nid WHERE (na.grant_view >= 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 1 AND na.realm = 'content_access_rid'))) AND ( nid=7626) 在 /includes/database.mysql.inc 第 174 行。
nid=7626 指的是连接到内容类型的 field_name。
当我尝试授予对内容类型的访问权限时，出现内部服务器错误。 现在我的日志显示我的数据库架构不是最新的。 我可能不小心在服务器上放置了该模块的更高版本。
有什么想法吗？
I just recently tried installing the Access Content Module to Drupal 5. The module didn't work correctly and I can not uninstall the module without getting an Internal Server Error.
Since I'm struck with the module I now have to try to use it.
Now I'm getting this error when an anonymous user views a page with a specific field_name that is connected to a content type that I can't grant full access to.
user warning: Column 'nid' in where clause is ambiguous query: SELECT
title FROM node INNER JOIN node_access na ON na.nid = n.nid WHERE
(na.grant_view >= 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid
= 1 AND na.realm = 'content_access_rid'))) AND ( nid=7626) in /includes/database.mysql.inc on line 174.
The nid=7626 is referring to a field_name that is connected to the content type.
When I try and grant access to the content type I get an Internal Server Error.
Now my logs are saying that my database schema is not up to date.
I may have accidentally placed a later version of this module on the server.
Any ideas?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您可以手动关闭 Drupal 数据库中名为 system 的 MySQL 表中的模块。
浏览该表，您应该会在某处看到模块名称和启用标志。请记住在关闭后运行 update.php。
即使您选择保持模块运行， update.php 也会应用尚未应用的模块架构更改，从而解决问题。
You can manually turn off the module in the MySQL table in your Drupal db called system.
Browse the table and you should see the module names somewhere and an enabled flag. Remember to run update.php after you turn it off.
Even if you choose to keep the module running update.php will apply module schema changes that have not been applied, and thus fix the issue.