Drupal 7：站点范围的分类限制——对特定术语实施 1:1 术语：节点关系
我正在开发一本在线杂志，并使用视图来生成主页块。
我使用稍微定制的文章作为大多数数据的内容类型，视图提供带有这些文章中必要字段的块。例如：Latest Blogs 视图显示 Short Headline 和 Teaser 字段，但 Top Headline 视图提供包含 Image 和 Full Headline 字段的块。
现在我正在使用视图按标签过滤文章，因此需要标记文章才能显示在主页上。我的大多数块都是列表，不需要最严格的排序灵活性。但是，某些块不是列表，或者最终用户控制某些块中文章的显示顺序非常重要。有没有办法对术语：文章关系强制执行站点范围内的 1:1 标记。例如，我想确保只有一篇文章被标记为 top.news.1 （第一个热门新闻栏位），同样只有一篇文章被标记为 top.news.2代码>.当有人想要将 top.news.2 添加到一篇文章时，已有该标签的一篇文章将会丢失它。或者类似的东西。
我对视图进行了充分的研究，发现它确实非常强大，因此在正确的配置下可能不需要这种级别的微控制，但我认为限制分类与配置视图过滤会更直接地解决问题。
我浏览了网络，但找不到任何真正相关的内容。抱歉，如果我错过了一些明显的事情。
谢谢你！
I'm developing an online magazine, and am using Views to generate blocks for the homepage.
I am using a slightly customized Article as the content type for most of my data, with Views providing blocks with the necessary fields from those Articles. For example: the Latest Blogs View shows the Short Headline and Teaser fields, but the Top Headline View provides a block with the Image and Full Headline fields.
Right now I'm using Views to filter Article by tag, so Articles need to be tagged to show up on the homepage. Most of my blocks are lists and don't need the tightest sorting flexibility. However, some blocks are not lists, or it's important for the end user to have control over the display order of Articles in certain blocks. Is there a way to enforce site-wide 1:1 tagging for term:article relationships. For example, I want to ensure that only one Article is tagged top.news.1 (the first Top News slot), and likewise only one article is tagged top.news.2. When someone wants to add top.news.2 to an Article, the one Article that already has that tag will lose it. Or something like that.
I have played around with Views enough to gather that it is really powerful, so this level of microcontrol might not be necessary with the right configuration, but I think restricting taxonomy versus configuring Views filtration would address the problem more directly.
I've looked around the web and haven't been able to find anything really relevant. Sorry if I missed something obvious.
Thank you!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您（或您的站点编辑者）希望能够以下功能是否正确：
如果是这样，您最好的选择可能是 Nodequeue，它正是这样做的，并允许您限制节点受到关注。它非常易于使用，我们的非技术客户使用起来没有任何问题。
如果您的用例与此不同或需要更大的灵活性，Nodequeue 可能不适合，但它非常适合您所描述的特定示例。
Is it correct that you (or your site editor) want the ability to:
If so, your best bet is likely Nodequeue, which does exactly that, and allows you to restrict the number of nodes spotlighted. It's very easy to use and our non-technical clients have no problems with it.
If your use case is different from that or requires more flexibility, Nodequeue may not be the right fit, but it works great for the specific example you're describing.