WordPress plugin intelligence profile

DMValdez Clean Post Toolkit

Keep standard blog posts clean and fast: block Elementor on posts, then give editors native buttons and accordions instead.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.0
Current version1.3.1
WordPress coverageTested up to WordPress 7.0
Minimum stackWP 5.8 · PHP 7.4
Directory statusactive
Last directory update17 Jul 20263mo ago
Active installations40Adoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records DMValdez Clean Post Toolkit version 1.3.1 as active, updated 3mo ago and tested up to WordPress 7.0.

Overview

About this plugin

DMValdez Clean Post Toolkit solves the classic battle between clean site architecture and editor convenience.

When editors use heavy page builders like Elementor on standard blog posts, it creates “div soup,” slows down page loads, and makes future theme migrations a nightmare. This plugin programmatically disables Elementor on the standard post post type and shows a friendly one-time modal explaining why — then hands editors a lightweight Classic Editor toolbar so they never have to reach for a page builder just to add a button or an FAQ.

Everything the toolbar inserts renders as clean, semantic HTML5 — no page-builder markup, no extra database bloat, and styling ships as a single small CSS file shared by the frontend, the block editor, and the Classic Editor’s own WYSIWYG iframe.

What’s included

php explaining the policy.

Buttons — [postguard_btn] — a theme-styled button that inherits your active theme’s Elementor button classes, so it looks native even with Elementor disabled. Inserted via a toolbar dialog with a live color-picker popup; every option is optional and defaults to your theme’s normal look:

  • text, link — button label and URL.
  • style — default (inherits theme), primary, or outline.
  • radius — square, md (rounded), or pill.
  • padding — sm, md, or lg; or padding_custom (px) to override with an exact value.
  • align — left, center, right, or full (full width).
  • bg_color, text_color, hover_bg_color, hover_text_color — hex colors, independent hover state.
  • border_color, border_width — add or override a border on any style.

Accordions — [postguard_accordion_group] / [postguard_accordion_item] — pure HTML5 <details> / <summary> accordions, zero JavaScript on the frontend. The toolbar’s “Insert Accordion” dialog builds a full FAQ block in one pass — a 3-column grid for up to 9 question/answer pairs, plus shared styling options:

  • question_tag — render each question as h2, h3, h4, or plain text (semantically valid — a heading is allowed as the sole child of <summary> ).
  • default_state — none (all collapsed), first (first item open), or all (all open) on page load; any individual item can also force itself open with open="yes".
  • item_spacing, row_padding — px values controlling the gap between cards and internal padding.
  • bg_color, title_color, content_color, hover_bg_color, hover_title_color — hex colors, cascading to every item in the group automatically.

"]answer[/postguard_accordion] still works standalone for hand-written content.

[/postguard_code] — real syntax-highlighted code, not a plain gray box. js (no third-party CDN requests) in a dark editor-style theme, with line numbers and a one-click Copy button. Supports Plain Text, HTML, CSS, JavaScript, PHP, Python, SQL, Bash, and JSON.

The highlighting assets only load on posts/pages that actually use the shortcode.

Toolbar helpers — a “Pick a Color” popup gives editors a real color picker with a copyable hex readout for any of the fields above, and a “Request a feature” link in every dialog points straight to the support forum.

Requirements

The Classic Editor (either natively, or via the Classic Editor plugin) is required to see the toolbar button — the toolkit hooks into TinyMCE’s mce_buttons / mce_external_plugins filters. Shortcodes themselves render correctly regardless of which editor inserted them.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • classic editor
  • elementor disable
  • accordion
  • button
  • shortcodes
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 7.0

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 7.0.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.0
Minimum requirementsWordPress 5.8 · PHP 7.4
Update activity17 Jul 20263mo ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.