Node Limit by Term

Node Limit By Term

Control content creation with taxonomy-based limits. Set maximum node counts per content type and term combination to manage site content growth and enforce editorial policies.

Features

Node Limit By Term provides a straightforward solution for managing content volume in your Drupal site. The module prevents content creators from exceeding specified node limits based on both content type and taxonomy term combinations.

Basic Functionality: Administrators can configure maximum node limits for specific content types and taxonomy terms through an intuitive backend configuration form. When a user attempts to create a node that would exceed the configured limit, the system prevents the submission and displays a clear error message.

Unique Features: Unlike generic node count restrictions, this module allows granular control by combining content type and taxonomy term restrictions. You can limit "Articles" tagged with "News" separately from "Articles" tagged with "Blog," giving you precise editorial control.

Use Cases and When to Use: This module is ideal for multi-tenant Drupal sites where different teams manage separate sections, sites with strict content governance policies, or platforms that need to manage resource usage. Use it when you want to prevent runaway content creation, enforce editorial guidelines, or ensure fair resource allocation across different content categories.

Post-Installation

After enabling the Node Limit By Term module, navigate to the configuration page to set up your limits.

Configuration Process:

Go to Administration > Configuration > Content > Node Limit By Term Settings (path: /admin/config/content/node-limit-by-term). On this page, you'll see a form where you can add node limits. For each limit, specify:

• The content type to which the limit applies
• The taxonomy vocabulary and term that triggers the limit
• The maximum number of nodes allowed

After configuring your limits, test by attempting to create or edit nodes. When a user tries to create a node that would exceed a configured limit, they'll receive a validation error preventing the action. The module runs checks automatically on node creation and editing, so no additional steps are needed.

Special Considerations: Existing nodes are not retroactively deleted or limited—only new content creation and updates are restricted. The module checks limits at form validation time, giving users immediate feedback before submission.

Additional Requirements

Node Limit By Term requires only Drupal core and has no external dependencies. It works with any standard Drupal installation using the core taxonomy system. No additional libraries, APIs, or contributed modules are required for basic functionality.

Similar Projects

Content Limits: A simpler module that restricts total node counts by content type only, without taxonomy term filtering. Node Limit By Term adds granularity by combining content type and term restrictions, making it suitable for more complex content governance.

Entity Limit: Offers node limiting but requires more complex configuration. Node Limit By Term provides an easier-to-use interface specifically optimized for taxonomy-based restrictions.

What Sets Node Limit By Term Apart: This module uniquely focuses on the taxonomy term + content type combination, giving you precise control without requiring custom code or complex rules configuration. It's designed for administrators who need straightforward, maintainable solutions.

Supporting This Module

Community Documentation

Check out these resources to learn more about using Node Limit By Term:

Troubleshooting

Limits Not Enforcing: Ensure the content type and taxonomy term are correctly configured on the settings page. Check that nodes are tagged with the correct taxonomy terms.

Users Can't Create Any Nodes: Verify that your configured limits are appropriate. If the limit is set to zero or too low, users may be blocked from creating content.

Existing Nodes Exceeding Limits: The module only prevents new nodes from exceeding limits. If you need to clean up existing content, use Views or custom scripts to identify and remove excess nodes.