Secure Nodes

The Secure Nodes module prevents accidental deletion of important content by adding protection settings to specific content types. After installation, users can configure protection for any content type, ensuring critical nodes are safeguarded from deletion.

Features

This module allows you to protect specific content types from deletion. Initially enabled for the 'Article' content type, it offers the flexibility to extend protection to other content types via the admin interface (/admin/config/content/secure_nodes).

Unique features include:

A checkbox called “Protect this Node?” on the node edit form, allowing users to mark a node as protected.
Bulk actions called "Protect content" and "Unprotect content" for applying or removing protection on multiple nodes simultaneously.
A dedicated Protected Nodes tab next to the Content tab, listing all the nodes currently marked as protected.
This module is ideal for use cases where content needs to be preserved long-term and should not be accidentally deleted by users, such as important blog posts, legal documents, or archived content.

Post-Installation

Once installed, the Secure Nodes module is automatically enabled for the Article content type. To enable it for other content types, navigate to admin/config/content/secure_nodes and select the desired content types.

On the node add/edit form for the selected content types, you'll find a new option, “Protect this Node?” in the sidebar menu. Checking this option protects the node from being deleted.

To view all protected nodes, an additional Protected Nodes tab will appear next to the Content tab, showing a list of nodes that have been marked as protected.

Additional Requirements

This module does not require any additional dependencies beyond Drupal Core (Views).

Recommended modules/libraries

There are no specific recommended modules for improving this module’s functionality, though it can complement any module that involves managing large volumes of content.

Similar projects

Initially, I named this module 'Protected Nodes', but during submission, I discovered that a module with the same name already exists (Protected Nodes) and offers similar functionality. My mistake! 😅

How is 'Secure Nodes' different from the Protected Nodes module?

The 'Secure Nodes' module introduces additional features, including bulk operations like 'Protect Node' and 'Unprotect Node' for managing content efficiently. It also provides a dedicated view where you can easily see a list of all protected nodes. Furthermore, unlike the 'Protected Node' module, which doesn't handle bulk 'Delete Content' operations, 'Secure Nodes' prevents nodes from being deleted even during 'Node Delete' bulk operations, ensuring greater protection.

Supporting this Module

There are no current external funding platforms for this project. However, community support through code contributions and issue reporting is welcome.

Community Documentation

There are no current external funding platforms for this project. However, community support through code contributions and issue reporting is welcome.

This is my first contributed module, so feel free to post any issues, questions, or suggestions!