Drupal - 面包屑导航和“在本节中”
我浏览了整个 Drupal 站点，以了解如何查看菜单面包屑模块安装的面包屑，但似乎没有人遇到与我相同的问题，有没有人遇到过 Drupal 中的菜单面包屑模块并知道如何使用它？ Drupal 中是否还有一个解决方案再次找不到答案，即您获得网站某个部分中所有页面的列表，并以“另请参阅”的方式将它们列出在页面上？
任何帮助将不胜感激。
谢谢西科
I have looked all over the Drupal site to find out how to view the breadcrumbs that the menu breadcrumb module installs, but no one else seems to be having the same problem as me, has any one come across the menu breadcrumb module in Drupal and knows how to use it? Also is there a solution in Drupal again couldn't find an answer, in that you get a list of all the pages in a section of the site and list them on the page, in See Also kind of style?
Any help would be appreciated.
Thanks Sico
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这是两个不同的问题。我不熟悉菜单面包屑模块，但如有疑问，请清除缓存。
如果您想列出网站中的大量页面，请查看视图（术语表已预先打包）， 站点地图，或许多其他模块。如需相关内容的推荐，请查看此比较图表，推荐 API 等。值得您花时间查看 Drupalmodules.org 来调查可用的模块。我只触及了我脑海中的一些。
Those are two different questions. I am not familiar with the Menu Breadcrumbs module, but when in doubt, clear the cache.
If you want to list a lot of pages in the site, check out Views (Glossary comes prepackaged), Site Map, or a number of other modules. For recommendations of related content, check out this comparison chart, the Recommender API, and more. It will be worth your while to check out Drupalmodules.org to investigate what modules are available. I have only touched on a few off the top of my mind.
从快速阅读该模块来看，该模块似乎使用 drupal_set_breadcrumb() 函数来更改面包屑。这意味着您看不到面包屑的原因不应该与该模块有任何关系。如果您停用它，问题仍然会存在。许多主题都可以选择完全禁用面包屑，有些主题甚至没有实现它们。我的猜测是你的问题出在你的主题上。
From a quick read through the module, it seems like the module uses the drupal_set_breadcrumb() function, to alter the breadcrumb. That means that the reason you are not seeing the breadcrumbs shouldn't have anything to do with the module. If you deactivate it you should still have the problem. Many themes have the option to disable breadcrumbs altogether and some doesn't even implement them. My guess would be that your problem is located in your theme.