CompleteWebResources

<p>Change the default WordPress comment blocklist functionality to exact match and save entries marked as spam for review.</p>
<p>The WordPress comment blocklist inside matches keywords, so for example, blocklisting a word such as “pasta” will automatically delete comments containing “pastaroni” or “anitpasta” (but not “chef boyardee”).</p>
<p>If you try to use the WordPress comment blocklist for contact form entries, this can be hugely problematic. The first major issue is falsely identifying comments as spam so you risk blocking valid contact form entries.</p>
<p>Additionally, there’s no moderation queue built into Formidable Forms, Contact Form 7, or Gravity Forms for entries marked as spam. This plugin fixes those issues.</p>
<h4>Changing the default WordPress comment blocklist functionality</h4>
<p>This plugin changes the default inside match blocklist functionality to exact match keywords, URLs, and ip addresses. If you add “karaoke” to your blocklist you’ll only be blocking “karaoke” and not “karaoke stars.”</p>
<h4>Retaining Contact Form Entries</h4>
<p>The plugin also retains contact form entries marked as spam in your database, so you can check them from the WordPress admin area.</p>
<h4>Important Notes / FAQ</h4>
<ul>
<li>For default comments in a post after submitting, if blocklisted, the comment will go to Spam status, whereas the default functionality would be to send that comment to the trash.</li>
<li>We’re currently configured to work with Contact Form 7, Formidable Forms and Gravity Forms.</li>
<li>Add keywords you want to block to the WordPress admin area under <strong>Settings > Discussion > Disallowed Comment Keys</strong></li>
<li>Upon activation, the plugin will automatically populate three keywords by default in the “Disallowed Comment Keys” field in the WP Admin area. This is so you know things are working. We leave it to the user to control their specific blocklist keywords. If you want a list of we’ll known spam words as a starting point, check your preferred search engine for “ultimate comment blocklist” or “WordPress comment blocklist.”</li>
<li><strong>CAUTION:</strong> Even though this is a significantly less blunt approach than the default WordPress functionality, please be careful. If you add the word “appointment” to your blocklist, you will block any form fill with the word “appointment” from getting through to your inbox.</li>
</ul>
<h4>Support the Plugin</h4>
<p>If you love this plugin and want to support it, you can help us by linking to this page, leaving constructive feedback, or sending a monetary donation <a href="https://paypal.me/completewebresources" rel="nofollow ugc">paypal.me/completewebresources</a>.</p>


Exact Match Disallowed Comment & Contact Forms

Change the default WordPress comment blocklist functionality to exact match and save entries marked as spam for review.

Ryan Tipones

<p><strong>Secure Form Checkout</strong> connects your Formidable Forms payment forms to the accept.blue payment processing platform. All card data is handled inside a secure accept.blue Hosted Tokenization iFrame — it never passes through your server, keeping your site PCI-compliant.</p>
<p>This is the <strong>free Lite version</strong>.</p>
<h4>What’s Included in Lite</h4>
<ul>
<li><strong>Credit card payments</strong> via accept.blue Hosted Tokenization iFrame — card data never touches your server</li>
<li><strong>Test / Sandbox mode</strong> — safely test payments with accept.blue sandbox credentials before going live</li>
<li><strong>Test Connection</strong> — verify your API credentials without leaving WordPress</li>
<li><strong>Debug logging</strong> — dedicated per-month log file with an in-admin log viewer, gated behind a settings toggle</li>
<li><strong>card authentication</strong> — optional EMV card authentication browser-based authentication per Form Action</li>
<li><strong>Per-form API credential override</strong> — run different forms against different accept.blue merchant accounts</li>
<li><strong>Processing overlay</strong> — animated spinner shown on form submit while payment processes</li>
<li><strong>Minified assets</strong> — production-ready JS and CSS; source files served automatically when WP_DEBUG is on</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 6.0 or higher</li>
<li>PHP 7.4 or higher</li>
<li>Formidable Forms Pro (required for payment fields)</li>
<li>An active accept.blue merchant account (sign up at https://accept.blue)</li>
</ul>
<h3>Source code</h3>
<p>The unminified source files for all JavaScript and CSS are included in the plugin’s assets/ directory alongside the minified production files. No separate build step is required to review the source.</p>
<h3>External Services</h3>
<p>This plugin connects to the accept.blue payment processing platform. Two distinct accept.blue services are contacted:</p>
<h4>1. accept.blue Payment API</h4>
<p>Used to authorise and capture credit card payments. When a visitor submits a payment form, the plugin sends a server-side request to the accept.blue API to process the charge.</p>
<p>Data sent: a short-lived card nonce token (generated by the Hosted Tokenization iFrame — never the raw card number or CVV), the payment amount, currency code, and the site’s accept.blue API credentials.</p>
<p>When data is sent: only when a visitor submits a payment form and the tokenization step has completed successfully.</p>
<ul>
<li>API endpoint (live): https://api.accept.blue/api/v2/</li>
<li>API endpoint (sandbox): https://api.sandbox.accept.blue/api/v2/</li>
<li>accept.blue website: https://accept.blue</li>
<li>API documentation: https://docs.accept.blue/api/v2</li>
<li>Terms of Service / Privacy Policy: https://accept.blue/terms-of-use/</li>
</ul>
<h4>2. accept.blue Hosted Tokenization Service</h4>
<p>Used to securely capture card details inside an iFrame. When a visitor views a payment form, the browser loads a secure iFrame from accept.blue’s tokenization service. The visitor enters their card number, expiry, and CVV directly into this iFrame. That card data is sent from the visitor’s browser directly to accept.blue — it never passes through your WordPress server.</p>
<p>Data sent: raw card details (card number, expiry, CVV) sent from the visitor’s browser directly to accept.blue’s tokenization servers. Your server receives only a short-lived nonce in return.</p>
<p>When data is sent: when the visitor enters card details and submits the payment form.</p>
<ul>
<li>Tokenization endpoint (live): https://tokenization.accept.blue/tokenization/v0.3/</li>
<li>Tokenization endpoint (sandbox): https://tokenization.sandbox.accept.blue/tokenization/v0.3/</li>
<li>Terms of Service / Privacy Policy: https://accept.blue/terms-of-use/</li>
</ul>


RyanPay Card Payments with accept.blue for Formidable

Accept credit card payments through accept.blue directly inside your Formidable Forms.

Exact Match Disallowed Comment & Contact Forms vs RyanPay Card Payments with accept.blue for Formidable