Jeremy Malcolm

Center for Online Safety and Liberty

<p>The <strong>Dead Dove</strong> plugin lets administrators and users apply content warnings to their content. Administrators define the available content warnings in a custom taxonomy of terms, and specify which of them trigger warnings by default. Users can overide these defaults in their user settings. Tags may be applied at the post level, block level, or even within a block using a shortcode. From version 2.0, they can also be applied when posting to BuddyBoss activity feeds and forums, even by users who lack access to the WordPress dashboard.</p>
<p>Content that has been tagged with a term that triggers a content warning for the user viewing it will be blurred from view. To view the content the user must read and accept a disclaimer that has been defined by the administrator in the description of the taxonomy term.</p>
<h3><strong>Features</strong></h3>
<ul>
<li>Blur content based on assigned terms and display warning text before viewing.  </li>
<li>Administrators select which terms require warnings, with the warning text pulled from term descriptions.  </li>
<li>Users can override admin settings by choosing their own tag warning preferences.  </li>
<li>Warning can be applied at the post or block level, using a shortcode with terms as parameters, or when posting to a Buddyboss activity feed or forum.</li>
<li>Multiple term descriptions are shown if more than one warning term is applied.</li>
</ul>
<h3>Usage</h3>
<h3><strong>Admin Settings</strong></h3>
<ol>
<li>Go to <strong>Settings > Content Warning</strong>.  </li>
<li>Select the terms that require a content warning.  </li>
<li>Add a description to each term to provide the warning text.</li>
</ol>
<h3><strong>User Settings</strong></h3>
<ol>
<li>Users who have access to the WordPress Dashboard can go to <strong>Your Profile</strong> to adjust their warning settings.</li>
<li>BuddyBoss users can adjust their warning settings by going to <strong>Account Settings</strong>, <strong>Content Warning Settings</strong>.</li>
<li>Users can disable warnings for certain terms set by the admin or enable warnings for terms that were not set by the admin.</li>
<li>User selections are stored in the <code>deaddove_user_warning_terms</code> user meta key.</li>
</ol>
<h3><strong>Post term usage</strong></h3>
<p>To apply a content warning to an entire post, apply a term that requires a content warning to the post. The content warning taxonomy will appear in the post editor screen, alongside tags, and are used in the same way.</p>
<h3><strong>Block Usage</strong></h3>
<ol>
<li>In the block editor, add the Content Warning block.</li>
<li>Select warning terms in the block settings.</li>
<li>Add your content inside the Content Warning block, which will be blurred until the user agrees to view it.</li>
</ol>
<h3><strong>Shortcode Usage</strong></h3>
<p>Use the <code>[content_warning]</code> shortcode to apply warnings within a block. The slug of the term or terms should be entered into the shortcode separated by commas.</p>
<p><strong>Example 1:</strong> Single term</p>
<pre><code>[content_warning tags="sensitive"]
This section discusses sensitive material.
[/content_warning]
</code></pre>
<p><strong>Example 2:</strong> Multiple terms</p>
<pre><code>[content_warning tags="graphic,offensive"]
This section contains graphic language and offensive themes.
[/content_warning]
</code></pre>
<h3><strong>BuddyBoss Usage</strong></h3>
<p>When adding content to the Activity Feed or Forum post, the available content warnings are shown in a drop-down in the editing box.</p>
<h3>Roadmap</h3>
<ul>
<li><strong>Geolocation-based Warnings</strong>: Modify content visibility based on the viewer’s location.  </li>
<li><strong>Custom Styling Options</strong>: Provide options to style blurred content and buttons using CSS.  </li>
<li><strong>Apply Shortcode from Editing Toolbar</strong>: Simpler application of content warnings to text selections.</li>
</ul>
<h3>License</h3>
<p>This plugin is licensed under the GPLv2 or later. See the <a href="https://www.gnu.org/licenses/gpl-2.0.html" rel="nofollow ugc">license</a> for more details.</p>


Dead Dove

Extend the WordPress tagging system to provide content warnings. Selected content will be blurred until the user reads and agrees to a disclaimer.

maid-h

<p><strong>MHT Entry Confirm</strong> adds a confirmation gate and content restriction modal to your WordPress site. Before visitors can view protected pages, a full-screen confirmation modal appears — content is revealed only after the visitor explicitly confirms they meet the required conditions.</p>
<p>Designed for sites that need simple, privacy-friendly access control without the overhead of complex membership plugins.</p>
<p><strong>Common use cases:</strong></p>
<p>– Age verification for adult content, alcohol, tobacco, or gambling-related sites<br />
– Content warnings for mature themes, violence, or graphic media<br />
– Regional or legal access restrictions (e.g. country-specific compliance)<br />
– Age-gated product pages for games, movies, or media with age ratings</p>
<p><strong>Why choose MHT Entry Confirm?</strong></p>
<p>– No personal data collected — fully GDPR-friendly<br />
– No tracking, no ads, no upsells<br />
– Free and open-source (GPL-2.0)<br />
– Lightweight — no impact on page speed</p>
<h3>Frontend-First Architecture</h3>
<p><strong>MHT Entry Confirm is designed with a frontend-first architecture.</strong></p>
<p>The confirmation gate runs entirely in the browser using JavaScript and cookies.<br />
After the page is loaded, the modal logic works independently from the WordPress backend.</p>
<p>– No AJAX requests to the server<br />
– No PHP processing during confirmation<br />
– No database interaction for visitor validation</p>
<p>All confirmation logic runs on the client side.</p>
<h3>Features</h3>
<p>– <strong>Blocking confirmation modal</strong><br />
  Displays a full-page modal before protected content is shown.</p>
<p>– <strong>Cookie-based access memory</strong><br />
  Remembers confirmed visitors for a configurable number of days, or for the current browser session only.</p>
<p>– <strong>Customizable appearance</strong><br />
  Adjust logo image, title color, modal title, description text, button color, backdrop color and opacity to match your site design.</p>
<p>– <strong>Safe redirect for restricted visitors</strong><br />
  Redirect visitors who do not confirm to a specified external URL.</p>
<p>– <strong>Flexible button settings</strong><br />
  Customize confirmation and decline button labels, and optionally swap their positions.</p>
<p>– <strong>Exclusion rules</strong><br />
  Disable the confirmation modal on specific posts, categories, or tags by ID.</p>
<p>– <strong>Cookie flag control</strong><br />
  Change the cookie flag value to invalidate existing cookies and force re-confirmation for all visitors.</p>
<p>– <strong>Test mode</strong><br />
  Preview and adjust the modal without saving cookies — useful for development and design tuning.</p>
<h3>For Developers</h3>
<p>MHT Entry Confirm dispatches a custom JavaScript event after a visitor successfully passes the confirmation step, allowing you to trigger additional logic.</p>
<p>The event name is stable within the same major version.</p>
<pre><code><script>
    document.addEventListener("mhtentryconfirm_passed", function() {
        // Custom logic after confirmation is passed
    });
</script>
</code></pre>


MHT Entry Confirm

Lightweight WordPress plugin to restrict content behind a confirmation modal — no tracking, no ads, privacy-friendly.

Dead Dove vs MHT Entry Confirm