BUG REPORT · WORDPRESS

Bug Report for WordPress

Bug reports with severity, environment, and reproduction steps. Free for 500 submissions per month — no backend, no SDK, no plugin.

Get free access key Copy the code

500/mo free·no card·drop-in for WordPress

submit.phpphp28 lines

01<?php
02// Drop into a PHP page. Receives a form POST and proxies it to splitforms.com.
03// Useful when you want to add server-side validation or rate limiting.
04 
05if ($_SERVER['REQUEST_METHOD'] === 'POST') {
06    $allowed = ['title', 'severity', 'browser', 'steps', 'email'];
07    $payload = ['access_key' => 'YOUR_ACCESS_KEY'];
08    $payload['subject'] = 'New bug report';
09 
10    foreach ($allowed as $f) {
11        if (isset($_POST[$f])) $payload[$f] = $_POST[$f];
12    }
13 
14    $ch = curl_init('https://splitforms.com/api/submit');
15    curl_setopt($ch, CURLOPT_POST, true);
16    curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($payload));
17    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
18    curl_setopt($ch, CURLOPT_HTTPHEADER, ['Accept: application/json']);
19    $response = curl_exec($ch);
20    $status   = curl_getinfo($ch, CURLINFO_HTTP_CODE);
21    curl_close($ch);
22 
23    header('Content-Type: application/json');
24    http_response_code($status);
25    echo $response;
26    exit;
27}
28?>

500

submissions / mo, free

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00WordPress + Bug Reportplatform-specific integration guide

Why WordPress developers choose splitforms for bug report

WordPress contact form plugins (Contact Form 7, WPForms, Fluent Forms) work but add database bloat, update fatigue, and a monthly subscription for features like webhook delivery or advanced spam controls. The bug report on this page drops into a Custom HTML block — no PHP, no plugin activation, no settings page to configure. Every field POSTs to splitforms as standard form data, so your WordPress admin stays clean. You keep using WordPress for content management and page building while splitforms handles the form pipeline.

§ 00Quick answerPHP · support

Yes — this is the shortest safe path for WordPress.

Use the PHP snippet on this page, keep the bug report fields visible in your WordPress UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.

best implementation

Paste the PHP version, then replace YOUR_ACCESS_KEY.

The posted payload contains short summary, severity, browser & os, steps to reproduce, your email (so we can follow up). Required fields are short summary, severity, steps to reproduce and your email (so we can follow up).

native wordpress reality

use case fit

User-reported bugs are signal — but only if the report has steps-to-reproduce and a screenshot. The form forces the structure, then files the issue automatically.

§ 01Bug Report × WordPresswhy this combination, in 80 words

Built for WordPress developers who hate operating a backend.

Splitforms is the form backend for WordPress sites. One POST endpoint, no SDK, no plugin — drop the bug report into a page and ship.

Splitforms is the form backend for WordPress sites. One POST endpoint, spam filtering, and a real dashboard — drop-in, no server, no PHP. Free for 500 dashboard submissions per month; Starter adds email, signed webhooks, exports, and retained uploads; Pro is $5/mo for 5,000.

✦ what you get on the free plan

✓500 form submissions per month
✓2 forms on Free; unlimited forms on Pro
✓Spam protection (honeypot + classifier)
✓Webhooks: Slack, Discord, WhatsApp, custom
✓CSV export of all submissions
✓Email notifications (CC and BCC on Pro)

§ 02Copy-paste codePHP · 28 lines

Drop into any WordPress project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a WordPress page, and ship. No build-time integration required.

submit.phpphp28 lines

01<?php
02// Drop into a PHP page. Receives a form POST and proxies it to splitforms.com.
03// Useful when you want to add server-side validation or rate limiting.
04 
05if ($_SERVER['REQUEST_METHOD'] === 'POST') {
06    $allowed = ['title', 'severity', 'browser', 'steps', 'email'];
07    $payload = ['access_key' => 'YOUR_ACCESS_KEY'];
08    $payload['subject'] = 'New bug report';
09 
10    foreach ($allowed as $f) {
11        if (isset($_POST[$f])) $payload[$f] = $_POST[$f];
12    }
13 
14    $ch = curl_init('https://splitforms.com/api/submit');
15    curl_setopt($ch, CURLOPT_POST, true);
16    curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($payload));
17    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
18    curl_setopt($ch, CURLOPT_HTTPHEADER, ['Accept: application/json']);
19    $response = curl_exec($ch);
20    $status   = curl_getinfo($ch, CURLINFO_HTTP_CODE);
21    curl_close($ch);
22 
23    header('Content-Type: application/json');
24    http_response_code($status);
25    echo $response;
26    exit;
27}
28?>

ALTPrefer plain HTML? View the universal bug report HTML snippet28 lines

form.htmlHTML

<form action="https://splitforms.com/api/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
  <input type="hidden" name="subject" value="New bug report">

  <label for="title">Short summary *</label>
  <input id="title" type="text" name="title" placeholder="What went wrong?" required>
  <label for="severity">Severity *</label>
  <select id="severity" name="severity" required>
    <option value="">Choose…</option>
    <option>Critical</option>
    <option>High</option>
    <option>Medium</option>
    <option>Low</option>
  </select>
  <label for="browser">Browser &amp; OS</label>
  <input id="browser" type="text" name="browser" placeholder="Chrome 120 / macOS">
  <label for="steps">Steps to reproduce *</label>
  <textarea id="steps" name="steps" placeholder="1. Go to…
2. Click…
3. See error" required></textarea>
  <label for="email">Your email (so we can follow up) *</label>
  <input id="email" type="email" name="email" placeholder="you@example.com" required>

  <!-- honeypot — bots fill every field -->
  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">

  <button type="submit">Send</button>
</form>

§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first bug report submission. None of them require a backend, a database, or a CAPTCHA library.

STEP 01GENERATE

Generate a free splitforms key

Create your form

key=sk_live_••••••••

STEP 02EMBED

Paste the bug report into your WordPress project

Drop the form snippet into a WordPress page, component, or layout. Replace YOUR_ACCESS_KEY with the key from your dashboard. The form action is a hard-coded URL — no env vars or build-time wiring needed.

snippetphp

<?php
  …
</form>

STEP 03RECEIVE

Receive submissions

Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.

inbox · 1 newjust now

FROM contact@yoursite.com

New bug report

Maya Iyer maya@studio71.co

Loved the demo — quick question about pricing on the 3-year plan. Are usage limits per project or account-wide?

§ 03bBug Report Form (Issue Submission)template-specific playbook

The reason this bug report exists.

Screenshot upload (Pro) · webhooks into Linear / GitHub Issues / Slack.

why it matters

Bug reports without reproduction steps waste hours of triage. The form structures the report — what happened, what was expected, steps to reproduce, browser / OS / device, screenshot. Screenshot upload is critical: 'the page broke' tells you nothing; a screenshot of the broken state tells you everything. Webhook the structured report into Linear or GitHub Issues so it lands as a triageable ticket, not a Slack message that scrolls away. For SaaS teams the time saved is huge — instead of a 4-message back-and-forth gathering basic context, the engineer opens the issue and starts debugging.

route the submission

Structure the report

Required: what happened, what you expected, steps to reproduce. Optional: browser, OS, device, URL where it occurred. Most templates auto-detect browser/OS via JS so the user doesn't have to fill them.

Screenshot upload

Pro file upload — drag-and-drop a screenshot or screen recording. Multi-file accepted. Image attachments arrive on the email and via webhook with signed URLs.

Webhook into Linear / GitHub

Lands as a Linear issue or GitHub issue with the structured report as the body and the screenshot embedded. Engineer opens, reproduces, fixes — no triage thread needed.

§ 03cWordPress production notesnative path · deploy · gotchas

What changes when this bug report lives in WordPress.

These notes come from the WordPress platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.

without splitforms

WordPress core has no contact-form feature — every contact form on a WP site is either a plugin (Contact Form 7, WPForms, Gravity Forms, Forminator, Fluent Forms, Ninja Forms) or a custom theme template. Plugins add 3-7 database tables, increase TTFB by 50-300ms, and most require a paid SMTP plugin (WP Mail SMTP) on top because shared-host PHP mail() lands in spam. CF7 alone is 1.2MB of JS/CSS loaded on every page. Anti-spam is a separate Akismet subscription ($10/mo for commercial use) or a paid CAPTCHA plugin. Splitforms replaces the plugin: a <form> tag in a Custom HTML block, pointing at our endpoint, with a hidden access_key field. No plugin, no extra DB tables, no SMTP gymnastics.

deploy notes

WordPress runs on shared hosts (Bluehost, Hostinger), managed WP hosts (Kinsta, WP Engine, Pressable), or self-hosted Apache/nginx. The form's POST is cross-origin to splitforms.com, so the host doesn't matter for delivery. Caching plugins (WP Rocket, W3 Total Cache, LiteSpeed Cache) cache the page that hosts the form — that's fine, the form action URL is static. Don't proxy through WP's admin-ajax.php or wp_remote_post — adds latency and re-introduces the SMTP problem. For Multisite, use one access key per site or a shared key with form-name to disambiguate. Headless WP (Next.js/Astro front) doesn't involve PHP at all — use the matching framework's snippet.

WordPress gotcha

WordPress wpautop() mangles your form HTML in posts

If you paste a <form> directly into a Classic Editor post, WordPress's wpautop filter wraps random <p> tags around your inputs and breaks the markup. Use a Custom HTML block (block editor) or a theme template file instead — wpautop doesn't touch those.

WordPress gotcha

Caching plugins (WP Rocket, W3 Total Cache) cache the form page itself

Page caching is fine — your form posts to splitforms.com directly, not a WordPress endpoint, so the cached HTML still works. But if you ever switch to a WP-side handler (e.g. wp_ajax), exclude /contact/ from the page cache or submissions will hit a stale page.

WordPress gotcha

Theme-injected JavaScript can hijack form submission

Some themes (Astra, OceanWP, GeneratePress 'Premium') auto-attach AJAX handlers to every form on the page. Add data-no-ajax="true" or a custom class your theme excludes — or use a Custom HTML block which most themes leave alone.

WordPress gotcha

Cloudflare Bot Fight Mode blocks splitforms responses

If you proxy your WP site through Cloudflare with Bot Fight Mode on, the redirect from splitforms.com → /thanks may be flagged. Whitelist your domain in splitforms's allowed-domains list AND ensure /thanks is reachable without a Cloudflare challenge.

PATTERN A

Pattern A — Custom HTML block (Block Editor / Gutenberg)

Drop a Custom HTML block on any page or post. Survives theme switches and plugin updates. No PHP required, no theme file editing. Reusable Patterns let you save the form once and drop it on every page. Use the same wiring for the bug report fields on this page.

pattern-a.phpphp9 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
03  <input type="hidden" name="redirect" value="/thanks/" />
04  <p><label>Name <input name="name" required /></label></p>
05  <p><label>Email <input name="email" type="email" required /></label></p>
06  <p><label>Message <textarea name="message" required></textarea></label></p>
07  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" />
08  <p><button type="submit">Send</button></p>
09</form>

PATTERN B

Pattern B — theme template with key from wp-config constant

For developer-managed themes (Bedrock/Sage/classic), define SPLITFORMS_KEY as a constant in wp-config.php and echo it via esc_attr(). Keeps the key out of the theme repo, lets staging and production read different keys via environment. Use the same wiring for the bug report fields on this page.

pattern-b.phpphp8 lines

01<?php // page-contact.php in your theme ?>
02<form action="https://splitforms.com/api/submit" method="POST">
03  <input type="hidden" name="access_key" value="<?php echo esc_attr( SPLITFORMS_KEY ); ?>" />
04  <input type="hidden" name="redirect"   value="<?php echo esc_url( home_url('/thanks') ); ?>" />
05  <input name="email" type="email" required />
06  <textarea name="message" required></textarea>
07  <button type="submit">Send</button>
08</form>

§ 04Field-by-field rundown5 fields · names you POST

What every field actually does.

Each field below ships in the bug report template — rename, remove, or add your own. Splitforms accepts any name you POST.

titleREQUIRED

TEXT

Short summary

Buyer-persona signal — IC vs decision-maker changes the follow-up cadence.

placeholder · What went wrong?

severityREQUIRED

SELECT

Severity

Triage signal — drives whether this pages on-call or waits till Monday.

CriticalHighMediumLow

browser

TEXT

Browser & OS

Repro context for engineering — saves a back-and-forth.

placeholder · Chrome 120 / macOS

stepsREQUIRED

TEXTAREA

Steps to reproduce

Free-text input — no character limit, expands as the visitor types.

placeholder · 1. Go to… 2. Click… 3. See error

emailREQUIRED

Your email (so we can follow up)

Reply-to address — splitforms wires this so hitting reply goes back to the sender.

placeholder · you@example.com

§ 05Bug Report on other frameworks21 frameworks · same backend

One backend. Every framework.

The same bug report template works on every framework splitforms supports. Pick yours.

§ 06Questions9 answered

Bug Report on WordPress — FAQ.

Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.

01Does this bug report work on WordPress?

Yes. The form is plain HTML with a single POST endpoint, so it runs on any WordPress site without server-side code, plugins, or SDKs. Drop the snippet into a WordPress page or component and submissions land in your splitforms dashboard.

02How much does the bug report cost on WordPress?

Free for 500 submissions per month — no credit card, no trial. Pro is $5/mo for 5,000 submissions, and there's a one-time $59 3-year plan (15,000 submissions/mo for 36 months). The same pricing applies regardless of which framework hosts the form.

03Can I customize the fields?

Yes. The template ships with sensible defaults (short summary, severity, browser & os, steps to reproduce…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.

04How does spam protection work on the bug report?

A hidden honeypot field catches dumb bots, and a tuned classifier scores the rest. You only see real submissions in your dashboard. No CAPTCHA, no friction for human users — and it works the same on WordPress as on any other framework.

05Can I send the bug report submissions to Slack or Discord?

Yes. Webhooks are available on Starter and above, with auto-formatted payloads for Slack, Discord, and WhatsApp (via CallMeBot). Or send raw signed JSON to any URL — Zapier, n8n, your own server. Configure in the splitforms dashboard.

06Will it work on a static WordPress site?

Yes — the form posts directly to splitforms from the browser, so no server is involved. Works on Vercel, Netlify, GitHub Pages, Cloudflare Pages, S3, or any plain Apache host.

07Should I auto-detect browser / OS?

Yes — JavaScript can read navigator.userAgent and pre-fill hidden fields with browser name, version, OS, and screen size. The user doesn't see them; the engineer gets them. Saves 90% of 'what browser are you on?' replies.

08Can I integrate with Linear / GitHub / Sentry?

Yes — webhook the JSON. Linear and GitHub both accept inbound issue creation via API or Zapier. Sentry doesn't accept user-reported bugs as events but you can webhook to a Slack channel where the on-call engineer triages and creates the Sentry issue manually.

09How do I prevent abuse / spam in bug reports?

Public bug-report forms attract spam — hidden honeypot plus splitforms' classifier catches most. Require an email field; bots filling random emails get filtered by the classifier. For severe abuse, gate the form behind a logged-in user session.

§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.

Feature	Web3Forms	Formspree	splitforms
Free monthly submissions	250	50	500
Custom fields beyond contact	Yes	Pro tier	Free
Webhooks (Slack / Discord)	Pro tier	Pro tier	Free, signed
AI / MCP submission inbox	No	No	Yes
Long-term plan (3-year flat)	—	—	$59 every 3 years

§ 08More templates for WordPress5 adjacent patterns

Ship a bug report on WordPress in 60 seconds.

500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your WordPress project.

Get free access key →Read the docs

founders pricing locked in · early access open

Bug Report for WordPress

Why WordPress developers choose splitforms for bug report

Yes — this is the shortest safe path for WordPress.

Paste the PHP version, then replace YOUR_ACCESS_KEY.

Built for WordPress developers who hate operating a backend.

Drop into any WordPress project.

Generate, embed, receive.

Generate a free splitforms key

Paste the bug report into your WordPress project

Receive submissions

The reason this bug report exists.

Structure the report

Screenshot upload

Webhook into Linear / GitHub

What changes when this bug report lives in WordPress.

WordPress wpautop() mangles your form HTML in posts

Caching plugins (WP Rocket, W3 Total Cache) cache the form page itself

Theme-injected JavaScript can hijack form submission

Cloudflare Bot Fight Mode blocks splitforms responses

Pattern A — Custom HTML block (Block Editor / Gutenberg)

Pattern B — theme template with key from wp-config constant

What every field actually does.

Short summary

Severity

Browser & OS

Steps to reproduce

Your email (so we can follow up)

One backend. Every framework.

Bug Report on WordPress — FAQ.

splitforms vs everything else.

Other ready-to-ship WordPress forms.

Ship a bug report on WordPress in 60 seconds.