Flinkform – GDPR Contact Forms for the Block Editor vs Disable Gutenberg

This plugin disables the new Gutenberg Editor (aka Block Editor) and replaces it with the Classic Editor. You can disable Gutenberg completely, or selectively disable for posts, pages, roles, post types, and theme templates. Plus you can hide the Gutenberg nag, menu item, and more! ♠ The all-in-one, COMPLETE solution for handling Gutenberg ♠ Hide ALL traces of Gutenberg and replace with Classic Editor ♠ Restores original Edit Post screen (TinyMCE, meta boxes, etc.) The Disable Gutenberg plugin restores the classic (original) WordPress editor and the “Edit Post” screen. So you can continue using plugins and theme functions that extend the Classic Editor. Supports awesome features like Meta Boxes, Quicktags, Custom Fields, and everything else the Classic Editor can do. Easy to Use Just activate and done! The default plugin settings are configured to hide all traces of the Gutenberg Block Editor, and fully restore the original Classic Editor. Further options for customizing when/where Gutenberg is enabled are available in the plugin settings. ♠ Disable Block Widgets and restore Classic Widgets 🙂 Options Disable Gutenberg completely (all post types) Disable Gutenberg for any post type Disable Gutenberg for any user role Disable Gutenberg for any theme template Disable Gutenberg for any post/page IDs Disable Gutenberg admin notice (nag) Option to restore Classic Widgets Option to hide the plugin menu item Option to hide the Gutenberg plugin menu item (settings link) Adds “Classic Editor” link to each post on the Posts screen Adds item to the WP sidebar menu: “Add New (Classic)” Option to enable Custom Fields Meta Box for ACF Choose which editor to use for each post Whitelist any post title, slug, or ID Option to enable/disable frontend Gutenberg stylesheet ♠ Works same as Classic Editor plugin, but can do a LOT more! ♠ Lightweight and super fast, built with WP APIs 🙂 Fully configurable, enable or disable Gutenberg and restore the Classic Editor wherever is necessary. Automatically replaces Gutenberg with the Classic Editor. Features Super simple Clean, secure code Built with the WordPress API Lightweight, fast and flexible Regularly updated and “future proof” Works great with other WordPress plugins Plugin options configurable via settings screen Focused on flexibility, performance, and security One-click restore plugin default options Translation ready ♠ Works great with Google AMP and the WordPress AMP plugin Disable Gutenberg is developed and maintained by Jeff Starr, 15-year WordPress developer and book author. Super light & fast plugin, super easy on server resources! Why? Gutenberg is a useful editor but sometimes you want to disable it for specific posts, pages, user roles, post types, and/or theme templates. This plugin enables you to disable Gutenberg and replace it with the Classic Editor wherever you want. For example, lots of WordPress users already enjoy robust page-building functionality via one of the many great plugins like Composer or Elementor. So many options, no need to feel “locked in” to using Gutenberg! If you like Disable Gutenberg, please give it a 5-star rating, thank you! Privacy This plugin does not collect or store any user data. It does not set any cookies, and it does not connect to any third-party locations. Thus, this plugin does not affect user privacy in any way. Support development I develop and maintain this free plugin with love for the WordPress community. To show support, you can make a donation or purchase one of my books: The Tao of WordPress Digging into WordPress .htaccess made easy WordPress Themes In Depth Wizard’s SQL Recipes for WordPress And/or purchase one of my premium WordPress plugins: BBQ Pro – Blazing fast WordPress firewall Blackhole Pro – Automatically block bad bots Banhammer Pro – Monitor traffic and ban the bad guys GA Google Analytics Pro – Connect WordPress to Google Analytics Head Meta Pro – Ultimate Meta Tags for WordPress REST Pro Tools – Awesome tools for managing the WP REST API Simple Ajax Chat Pro – Unlimited chat rooms USP Pro – Unlimited front-end forms Links, tweets and likes also appreciated. Thanks! 🙂

Flinkform is a form builder that lives entirely inside the WordPress Block Editor. Forms are composed from native blocks (block.json v3), styled through theme.json design tokens, and powered by the Interactivity API — no separate form builder UI, no shortcodes, no jQuery, under 15 KB of frontend JavaScript (gzipped). Built in Germany for GDPR-first websites. Das deutschsprachige Kontaktformular-Plugin für den Block-Editor. Try it before you install it: live demo forms, including multi-step and conditional logic, at https://demo.flinkform.de/ GDPR by design No IP logging, no user-agent logging, no tracking, no external services in the free core. Spam protection runs on a honeypot, a signed timing check and a proof-of-work challenge with a no-JavaScript maths fallback — no reCAPTCHA, no hCaptcha, no Cloudflare Turnstile, and therefore no data transfer to US servers. Includes a consent field, retention periods with automatic deletion and integration with the WordPress privacy tools. Free, not a trial Multi-step forms and conditional logic are in the free core, not behind a paywall: Multi-step forms with progress indicator and per-step validation Conditional logic for fields, steps, skipping steps and gating the submit button 14 field types including a dedicated consent field Submissions dashboard inside WordPress with search, filters and read state Email notifications with merge tags, plus an optional confirmation mail Automatic theme.json styling — forms match your theme without extra CSS Built for accessibility: the rendered markup passes axe-core against WCAG 2.1 A/AA with zero violations Flinkform Pro The optional Pro add-on adds Stripe payments (card, SEPA direct debit, Apple Pay, Google Pay — whichever methods you enable in Stripe), calculation fields, multi-file upload, SMTP delivery, webhooks, newsletter integrations, CSV export and custom CSS. Details and pricing: https://flinkform.de/pro Requirements WordPress 6.5 or newer, PHP 8.1 or newer, Block Editor (Gutenberg). How it works Block Editor native — forms are built with block.json and the Interactivity API, directly inside the editor theme.json styling — forms inherit your theme’s typography, colours and spacing automatically Modern stack — WordPress 6.5+, PHP 8.1+, no jQuery, frontend JS under 15 KB gzipped Multi-step forms — split long forms into steps with a Page Break block, included in the free core Conditional logic — show/hide fields based on user input, included in the free core Accessible by default — full keyboard navigation, screen-reader compatible, aria-live announcements Privacy by design — no external services, no tracking cookies, no IP tracking — everything stays on your server Features (free core) Form building * 14 field types: Text, Email, Textarea, Number, Date, URL, Phone, Select, Radio, Checkbox, Toggle, Hidden, Consent, Address * Composite Address field: street, postal code and city in a compact grid, with optional address line 2 and country * Dedicated Consent field for privacy-policy agreement * Notice block: a highlighted note between fields (info, success, warning, important) — pair it with conditional logic to surface guidance only when it applies * Section Heading and Page Break blocks for structuring longer forms * Multi-step forms with Page Break block, per-step validation and progress indicator (bar, dots or numbers) * Conditional logic — show/hide fields, skip steps, gate the submit button, with nestable groups for “(A or B) and C” * Two-column layout with per-field full-width override Styling * Automatic theme.json inheritance (colours, typography, spacing, border radius) * Style panel: primary colour, field style (bordered/soft/underline/minimal), label position (above/beside/floating/placeholder), submit button style (fill/outline/ghost), plus colour pickers for labels and help/consent text — and the Section Heading block carries WordPress’s native text-colour option Accessibility * Built accessible: real label/for pairs, fieldset/legend for choice groups, errors announced via role=”alert” and linked with aria-describedby, focus moves to the first invalid field * Multi-step navigation announces the new step via aria-live and manages focus; the progress indicator is a real progressbar with current values * Visible focus rings even when the theme removes them, prefers-reduced-motion respected, and the spam protection needs no CAPTCHA — nothing to squint at, nothing to solve * Works fully without JavaScript, and the form markup passes axe-core (WCAG 2.1 A/AA) with zero violations — including the error state Notifications * Admin notification email on every submission (configurable recipient, merge tags) * Optional confirmation email to the submitter * Sender name and address per form, with a Reply-To for each email — send from your own address without an SMTP plugin * Sends through your site’s standard WordPress mail (wp_mail) Spam protection * Always-on honeypot + signed time-based check (zero configuration) * Built-in proof-of-work challenge with accessible math fallback for visitors without JavaScript * No external service, no API keys, no tracking cookies, 100% GDPR-friendly After submission * Success message or redirect to a custom thank-you URL (with open-redirect protection) * Optional submission ID and form ID query parameters for conversion tracking (GA4, Meta Pixel, Plausible, etc.) Admin * Submissions list with search, filter by form, sort, bulk actions * Single-submission detail view with all field labels and values * Mark as read/unread * Per-form data retention with automatic daily purge Privacy Flinkform is built with privacy by default. Here is what the free core does and does not do: What the free core stores: * Form submissions (the field values visitors enter) in a dedicated database table ({prefix}flinkform_submissions) What the free core does NOT do: * It stores no IP addresses and no browser user-agent strings * It sets no tracking, analytics or marketing cookies. Flinkform sets exactly one strictly-necessary cookie — flinkform_flash (lifetime ~60 seconds, httpOnly) — and only when a form submission fails validation, to carry the error message and the visitor’s input across the page reload. Successful submissions set no cookie at all * It contacts no external service Data retention: * By default, submissions are retained until you delete them. To comply with the storage-limitation principle (GDPR Art. 5), set a per-form retention period (Form block → Data Retention) and Flinkform deletes older submissions automatically each day * Individual submissions can be deleted from the admin submissions screen at any time Data deletion: * All free-core data (the submissions table) is permanently removed when the plugin is uninstalled through the WordPress admin * Flinkform integrates with WordPress’s privacy tools (Tools > Export Personal Data / Erase Personal Data) to support data-subject access and erasure requests Source Code The complete, uncompiled source code (including the src/ directory with the unminified JavaScript/CSS that compiles into build/) is publicly available at: https://github.com/dennisbuchwald/Flinkform Build instructions (Node.js 18+ and npm required): 1. Clone the repository: git clone https://github.com/dennisbuchwald/Flinkform.git 2. Install dependencies: npm install 3. Build the compiled assets into build/: npm run build The build is powered by @wordpress/scripts (webpack). The src/ sources are excluded from the distributed plugin zip to keep it small; this repository is the canonical, reviewable source.