
A reader writes a thoughtful comment, clicks Submit, and nothing happens — or the page reloads with the comment gone and no trace of it anywhere. When wordpress comment form not submitting happens, readers give up, discussions die, and the site owner often never knows, because no error is shown to anyone. The form itself is rarely broken. The fault is usually a discussion setting, a spam filter, a plugin conflict, or a cached page serving an expired security token.
This guide works through the causes in order, from filling in the form correctly to repairing the database. Test as a logged-out visitor wherever possible, because the form behaves differently for logged-in admins. Work through the fixes one at a time, and submit a test comment after each one. A test comment that appears — or lands visibly in moderation — is the proof that counts.
Table of Contents
- Why This Error Happens
- Quick Checks
- Diagnosing the Problem
- Fix 1: Fill In Every Required Field and Submit Again
- Fix 2: Check Comments Are Enabled for That Post
- Fix 3: Check the Post Is Not Closed to Comments by Age
- Fix 4: Test as a Logged-Out Visitor and Check the Login Requirement
- Fix 5: Clear the Browser Cache, Pause the Ad Blocker and Try Another Browser
- Fix 6: Check the Comment Is Not Held for Moderation or Marked as Spam
- Fix 7: Reconfigure the Spam Filter or CAPTCHA Blocking Submissions
- Fix 8: Test for a Plugin Conflict in Troubleshooting Mode
- Fix 9: Switch to a Default Theme to Rule Out a Broken Comment Template
- Fix 10: Fix the Missing Theme Footer Code That Loads Comment Scripts
- Fix 11: Check the Custom Comment Form for Missing Hidden Fields
- Fix 12: Clear Caching and Stop Cached Pages Serving Stale Forms
- Fix 13: Check Security Rules Blocking the Comment Submission Address
- Fix 14: Check the Database Comments Table and Repair It
- Fix 15: Update WordPress, the Theme and Plugins, and Re-Test the Default Form
- What to Avoid
- Frequently Asked Questions
- Conclusion
- Helpful Official Resources
Why This Error Happens
Submitting a comment sends the name, email, comment text, and a security token to the server, which checks the discussion settings, runs spam filters, and writes the comment to the database. If any check fails — a missing field, a closed post, a spam verdict, an expired token — the submission is refused, often with no message at all. These are the reasons that happens most often.
1. Comments Are Switched Off for the Post
WordPress allows comments per post as well as site-wide, and the two settings can disagree. A post with comments disabled shows no form, or shows a form that refuses submissions, while other posts accept comments normally. Imported posts, posts created by page builders, and posts with individual discussion settings changed are the usual cases. The site-wide setting being on does not override a single post’s setting.
2. A Required Field Is Empty or Blocked
The default form requires a comment, and usually a name and an email address. If a field is empty, hidden by the theme, or blocked by a browser extension, the submission fails validation and the page reloads with the comment lost. Custom themes and comment plugins can add extra required fields, such as a checkbox, that visitors miss. The failure looks like a broken form, but it is a validation refusal.
3. The Comment Is Held for Moderation or Flagged as Spam
Many submissions succeed but never appear, because WordPress holds them for moderation or a spam plugin marks them as spam. To the visitor, the comment vanished; to the site owner, it sits in a queue nobody checked. Moderation holds comments with links, comments from new visitors, and comments matching the moderation word list. Spam filters can be over-eager, especially with default settings on a new site.
4. A Spam Filter or CAPTCHA Rejects the Submission
Spam plugins and CAPTCHA tools guard the form, and a misconfigured guard rejects real comments along with spam. An expired CAPTCHA key, a CAPTCHA that fails to load, or a spam rule that is too strict all produce silent refusals. The visitor sees a form that will not submit, the owner sees nothing at all, and the guard gives no explanation to either side.
5. A Plugin or Theme Breaks the Form Script
The comment form needs JavaScript for reply threading, and the theme must load the footer code that powers it. A plugin conflict, a theme missing the required footer function, or a broken custom comment template can all stop the form submitting. The form looks complete, but the submission path is broken underneath, so clicks do nothing or reload the page unchanged.
6. A Cached Page Serves an Expired Security Token
WordPress forms carry a security token that proves the submission came from a real visit. Caching plugins store whole pages, including the form with its token, and a cached page can serve a token that has already expired. The server refuses the stale token, and the submission fails. This cause is the hardest to spot, because the form looks perfect and the failure leaves no message — and it is also the cause behind many reports of wordpress comment form not submitting on cached sites.
Quick Checks
Two minutes before the deep fixes.
- Open the post in a private browser window, logged out, and look for the comment form.
- Check whether the form appears at all, appears but will not submit, or submits with no comment appearing.
- Check whether comments work on other posts, or fail on every post.
- Check the Comments screen in the dashboard for pending and spam queues you have not checked.
- Check whether the fault began after a new plugin, a theme change, or a caching change.
- Think about what changed — did wordpress comment form not submitting begin after a spam plugin, a security plugin, or a comment plugin was added?
Diagnosing the Problem
| Symptom | Cause | Go to Fix |
|---|---|---|
| No form shown under the post | Comments disabled for the post | Fix 2 |
| Form shows, submit does nothing | Script fault or blocked field | Fix 5 |
| Form reloads, comment vanishes | Validation or stale token | Fix 1 |
| Comment submitted, never appears | Held for moderation or spam | Fix 6 |
| CAPTCHA never completes or errors | CAPTCHA misconfiguration | Fix 7 |
| Form fails on every post | Plugin conflict or theme fault | Fix 8 |
| Form fails only when logged out | Login requirement or cache | Fix 4 |
| Form worked before caching was added | Cached page with expired token | Fix 12 |
Fix 1: Fill In Every Required Field and Submit Again
The simplest cause is the most overlooked: a required field left empty. The name, email, and comment fields are required by default, and some themes add a consent checkbox that must be ticked. A failed validation reloads the page and often clears the comment text, which makes the fault look worse than it is. One careful, complete submission establishes whether the form works at all.

- Open the post in a private browser window, logged out, and scroll to the comment form.
- Read every field label, and note which fields are marked required with an asterisk.
- Type a name, a valid email address, and a short test comment of two or three sentences.
- Tick any consent or “save my details” checkbox the form shows, if it is marked required.
- Click the submit button once, and wait for the page to reload fully.
- Check whether the comment appears, or a message says it awaits moderation.
- If the page reloads with the comment gone, note exactly what happened — blank form, error message, or unchanged page — for the fixes below.
- Clicking submit twice can create duplicate comments, or confuse the validation — click once and wait.
- An email address with a typo fails validation silently on some setups, so type it carefully.
- If the form has no visible required markers, assume name, email, and comment are all required.
- When wordpress comment form not submitting means the page reloads empty, a missed required field is the first suspect.
Fix 2: Check Comments Are Enabled for That Post
Comments can be disabled for a single post while the site-wide setting stays on. The post editor holds the per-post switch, and the bulk editor, importers, and page builders can change it without the owner noticing. Checking the post itself, and the site-wide default, covers both levels of the setting.
- In the dashboard, open the post that refuses comments for editing.
- In the block editor sidebar, open the Discussion panel — enable it under Options, then Preferences, then Panels if it is hidden.
- Check Allow comments is ticked for this post.
- Click Update to save the post.
- Next, open Settings, then Discussion, and check Allow people to submit comments on new posts.
- Click Save Changes at the bottom of the Discussion settings.
- Open the post in a private window and check the form appears and accepts a test comment.
- The site-wide setting affects only new posts — changing it does not reopen comments on existing posts, which need the per-post fix.
- In the classic editor, the discussion switch lives in a meta box below the editor, enabled through Screen Options.
- Posts imported from another site often arrive with comments disabled, whatever the new site’s default says.
- If the form appears after this fix but submissions still fail, the fault is deeper, and Fixes 5 onwards apply.
Fix 3: Check the Post Is Not Closed to Comments by Age
WordPress can close comments automatically on posts older than a set number of days. The setting is easy to enable and easy to forget, and it produces a form that disappears — or a “comments are closed” message — on older posts while new posts work fine. The age pattern is the giveaway: new posts accept comments, old posts do not.
- In the dashboard, open Settings, then Discussion.
- Find Automatically close comments on posts older than and check whether it is ticked.
- If it is ticked, note the number of days, and check the failing post’s age against it.
- Untick the setting if you want comments open on older posts, or raise the number of days.
- Click Save Changes at the bottom of the page.
- For a post already closed by age, reopen it individually with the per-post switch in Fix 2.
- Open the older post in a private window and check the form appears and accepts a test comment.
- The auto-close setting does not reopen posts it already closed — each closed post needs the per-post switch turned back on.
- A post closed by age shows “Comments are closed” or no form at all, depending on the theme — both mean the same thing.
- Some sites close old comments deliberately to cut spam; if that is your policy, the behaviour is correct, not a fault.
- After changing the setting, test an old post specifically, because new posts were never affected.
Fix 4: Test as a Logged-Out Visitor and Check the Login Requirement
The form behaves differently for logged-in users and visitors. A setting that requires registration and login hides the form from visitors entirely, showing a login link instead. Admins testing while logged in see a working form and conclude nothing is wrong, while every visitor is locked out. Testing logged out, and checking the login setting, closes that blind spot.
- Open the post in a private browser window, where you are not logged in.
- Check whether the comment form appears, or only a message asking visitors to log in.
- In the dashboard, open Settings, then Discussion.
- Find Users must be registered and logged in to comment and check whether it is ticked.
- If it is ticked and you want open comments, untick it and click Save Changes.
- If you want login-only comments, keep it ticked, and check the login link on the post actually works.
- Retest in a private window: visitors should now see the form, or a working login path.
- Always test comment faults logged out — logged-in testing hides the login requirement, the cache behaviour, and the spam-filter path.
- Registration settings interact with this one: if registration is closed, visitors cannot create accounts to comment at all.
- If registration itself is broken, our guide to WordPress new user registration not working covers the registration side.
- A form that works for admins but not for visitors is a settings or cache fault, never a broken form.
Fix 5: Clear the Browser Cache, Pause the Ad Blocker and Try Another Browser
Browser extensions, especially ad blockers and privacy tools, can block the comment form’s scripts or strip its fields. A stale browser cache can load an old copy of the form page. Testing in a clean browser with no extensions rules out the visitor’s own computer before the site is changed — and it is the test to suggest to any reader who reports the fault.
- Open the post in a private browser window, which loads no extensions and no cache.
- Fill in the form completely and submit a test comment.
- If it works in the private window, the normal browser’s cache or extensions are the cause.
- In the normal browser, clear the cache and cookies for the site, and pause the ad blocker for the site.
- Try a different browser entirely, such as Firefox if the fault appears in Chrome.
- If the private window also fails, the fault is on the site, and Fixes 6 onwards apply.
- Ask a reporting reader to try a private window too, before changing the site for their report alone.
- Privacy extensions sometimes block the form’s submission address, mistaking it for a tracker — pausing the extension for the site is the test.
- A fault in one browser only is a browser fault, not a site fault, however convincingly it presents.
- Clearing the cache signs the tester out of some sites, so a private window is the quicker clean test.
- When wordpress comment form not submitting is reported by one reader only, their browser is the first suspect, not the site.
Fix 6: Check the Comment Is Not Held for Moderation or Marked as Spam
Many “failed” submissions actually succeed and land in the moderation or spam queue, where they wait unseen. WordPress holds comments with links, comments from first-time visitors, and comments matching the moderation word list. Checking the queues, and adjusting the moderation rules, turns invisible successes into visible comments.

- In the dashboard, open Comments and click the Pending tab.
- Look for the missing test comments, and approve the genuine ones.
- Click the Spam tab and check for genuine comments caught by the spam filter.
- Mark any genuine comment in spam as Not Spam, which also teaches the filter.
- Open Settings, then Discussion, and review the Comment Moderation and Disallowed Comment Keys lists.
- Remove any over-broad word or address from the lists that is catching genuine comments.
- Submit a fresh test comment and check whether it appears, or lands visibly in Pending.
- Comments with two or more links are held by default — the link threshold is a setting, and lowering the hold is a choice with spam consequences.
- A comment held for moderation is a success, not a failure — the visitor should see an “awaiting moderation” message, and the owner should check the queue daily.
- If approved comments still do not show, our guide to WordPress comments not appearing covers the display side of the fault.
- Empty the spam queue regularly, but check it first — genuine comments hide there more often than owners expect.
Fix 7: Reconfigure the Spam Filter or CAPTCHA Blocking Submissions
Spam plugins and CAPTCHA tools are the gatekeepers of the form, and a misconfigured gatekeeper rejects everyone. An expired CAPTCHA key, a CAPTCHA widget that never loads, or a spam plugin set to its strictest level all produce silent refusals. Reconfiguring the guard — or pausing it briefly to test — separates a guard fault from a form fault.
- In the dashboard, check which spam plugin and CAPTCHA tool the site uses.
- Open the spam plugin’s settings and check it is connected and active — an expired key disables the protection oddly on some plugins.
- Temporarily pause the CAPTCHA on the comment form, and submit a test comment.
- If the test succeeds, the CAPTCHA is the cause — refresh its keys, or replace it with the provider’s current version.
- Restore the CAPTCHA with fresh keys, and test again to confirm real comments pass.
- If the spam plugin is the cause, lower its strictness one step, and test again.
- Keep a spam guard active in the end — removing protection entirely invites a flood of spam within days.
- A CAPTCHA that shows a perpetual spinner, or never appears, usually has a key problem or a script conflict — check the browser console for errors.
- Never leave the form unguarded as a permanent fix; the spam flood that follows is worse than the original fault.
- Some spam plugins hold comments silently instead of showing a message — check the plugin’s log or queue for the missing comments.
- Test with a realistic comment, not a one-word test, because some filters judge short or link-heavy comments more harshly.
Fix 8: Test for a Plugin Conflict in Troubleshooting Mode
Comment plugins, security plugins, caching plugins, and form plugins all touch the comment form, and any one of them can break submissions. Troubleshooting Mode disables plugins for your session only, so you can test the form safely while visitors see the normal site. Re-enabling plugins one at a time finds the culprit without disturbing the live site.
- Install and activate the free Health Check & Troubleshooting plugin from WordPress.org.
- Go to Tools, then Site Health, then Troubleshooting, and click Enable Troubleshooting Mode.
- Open a post in a private window — sign in there so the troubleshooting session applies — and submit a test comment.
- If the test succeeds, a plugin is the cause — re-enable plugins one at a time, testing after each.
- Test comment, security, caching, and optimisation plugins first, as they touch the form directly.
- Keep the culprit disabled, replace it, or adjust its settings, and report the conflict to its developer.
- Click Disable Troubleshooting Mode to restore the normal site.
- Troubleshooting Mode affects only your session — visitors see the site normally throughout the test.
- A plugin updated recently is a prime suspect, especially if the fault has a clear start date.
- For the full conflict-testing method, our guide to WordPress plugin conflict fix covers the step-by-step process.
- Form plugins that replace the default comment form are a common cause — check whether the form is the default form or a replacement.
Fix 9: Switch to a Default Theme to Rule Out a Broken Comment Template
The theme provides the comment template: the form markup, the reply links, and the comment display. A theme with a broken or outdated template can show a form that never submits, or hide the form entirely. Switching briefly to a default theme such as Twenty Twenty-Five rules the theme out. Do it at a quiet time, and switch back promptly.
- Note the current theme name, so you can switch back to it exactly.
- Go to Appearance, then Themes, and activate a default theme such as Twenty Twenty-Five.
- Open a post in a private window and submit a test comment on the default theme’s form.
- If the test succeeds, the original theme’s comment template is the cause.
- Update the original theme, or ask its developer for a fix for the comment template.
- Switch back to the original theme immediately after the test.
- If the default theme also fails, the fault is not the theme — continue with Fixes 10 onwards.
- Switching themes does not delete comments, posts, or settings — it only changes the appearance during the test.
- A theme that overrides the comment form with custom markup is more likely to break than one using the default template.
- Child themes inherit the parent’s comment template, so test with the parent theme’s behaviour in mind.
- Keep the test short, because visitors see the changed appearance while the default theme is active.
Fix 10: Fix the Missing Theme Footer Code That Loads Comment Scripts
WordPress themes must call the footer function that loads queued scripts, including the comment-reply script that powers threaded replies and form behaviour. A theme missing that call — common in hand-built or very old themes — breaks comment scripts silently. The form appears, but its behaviour never loads. Checking the theme’s footer file, or asking the theme developer, fixes it at the source.

- In the dashboard, go to Appearance, then Theme File Editor, if it is available.
- Open the theme’s
footer.phpfile and search for the footer function call near the closing body tag. - If the call is missing, the theme is faulty — do not edit it directly unless you are confident.
- The safe fix is to update the theme, switch to a maintained theme, or ask the theme developer to add the missing call.
- If you use a child theme, check whether its footer template overrides the parent’s, and restore the parent’s footer.
- After any theme change, clear the cache and submit a test comment in a private window.
- Check threaded replies too — replying to a comment exercises the script this fix restores.
- Editing theme files directly is risky: a typo can break the whole site, and updates overwrite the change — prefer a theme update or a child theme.
- The Theme File Editor may be disabled by the host or a security plugin, which is a good thing — use the theme developer route instead.
- A theme that fails this check usually has other faults too, so consider it a sign the theme needs replacing.
- When wordpress comment form not submitting survives plugin tests and the form looks complete, the missing footer call is a strong suspect.
Fix 11: Check the Custom Comment Form for Missing Hidden Fields
Custom comment forms — built by themes, page builders, or code snippets — must include hidden fields that identify the post and carry the security token. A form missing those fields submits data WordPress cannot attach to a post, so the submission is refused. Comparing the custom form with the default form, or temporarily restoring the default form, reveals the missing piece.
- Check whether the site uses a custom comment form: look in the theme options, the page builder settings, and the code snippets.
- Temporarily switch the post to the default comment form, by pausing the custom form’s plugin or snippet.
- Submit a test comment on the default form in a private window.
- If the default form works, the custom form is the cause — inspect its fields against the default form’s fields.
- Look for the hidden post identifier field and the security token field, which the custom form must include.
- Restore the custom form only after its missing fields are added, or keep the default form permanently.
- Test threaded replies on the restored form, because reply handling needs its own hidden field.
- A form that looks identical to the default form can still miss a hidden field — appearance proves nothing here.
- Code snippets that customise the comment form are a common source of missing fields, especially snippets copied from old tutorials.
- If a form plugin replaces the comment form, check its settings for a post-identifier mapping, and test with the plugin paused.
- Form submission faults in page-builder forms share causes with comment forms: our guide to Elementor form submissions not working covers the builder side.
Fix 12: Clear Caching and Stop Cached Pages Serving Stale Forms
Caching plugins store the rendered post page, including the comment form and its security token. A visitor who loads a cached page submits with a token that may already be expired, and the server refuses the submission. The form looks perfect, the visitor did nothing wrong, and no error explains the refusal. Excluding comment pages from caching, or using a cache that refreshes the token, ends the fault.
- In the caching plugin’s settings, find the cache exclusion or “never cache” list.
- Add the post URLs, or a rule covering single posts, to the exclusion list — or enable the plugin’s option to exclude pages with comment forms.
- Purge the entire cache, so no stale form remains anywhere.
- Clear the server cache in the hosting panel, and the CDN cache if one is used.
- Open a post in a private window, wait for the page to load fully, and submit a test comment.
- If the test succeeds, the stale cache was the cause — keep the exclusion in place permanently.
- Check the plugin for a setting that refreshes security tokens on cached pages, and enable it if offered.
- Excluding posts from caching costs a little speed, but a comment form that works is worth more than a cached page that refuses submissions.
- Some caching plugins offer “cache logged-in users separately” — that setting alone does not fix the token problem for visitors.
- Test with a fully loaded page: submitting before the page finishes loading can itself use a stale token.
- After purging, wait a minute before testing, because the first visit after a purge rebuilds the cache slowly.
Fix 13: Check Security Rules Blocking the Comment Submission Address
Security plugins and server firewalls can block the address WordPress uses to receive comments, wp-comments-post.php, mistaking legitimate submissions for attacks. Rate limiting, bot protection, and firewall rules can all refuse the submission silently, or with a generic forbidden message. Checking the security log for blocked requests to that address reveals the block.
- Open the security plugin’s settings and find its firewall log or blocked-requests log.
- Search the log for the comment submission address and for recent blocked POST requests.
- If blocks appear, add an exception for the comment submission address, following the plugin’s documentation.
- Check the hosting firewall or CDN firewall rules too, especially bot-protection rules.
- Temporarily pause the security plugin’s firewall, and submit a test comment in a private window.
- If the test succeeds, the firewall rule is the cause — restore the firewall with the exception in place.
- Never leave the firewall paused as a permanent fix; the exception, not the pause, is the cure.
- A “403 Forbidden” message on submit is the clearest sign of a firewall block — note the exact message for the security log search.
- Rate limiting can block a visitor who submits several test comments quickly, so space test submissions a minute apart.
- Some hosts block the submission address at the server level after a spam attack — ask the host to check if no plugin log explains the block.
- Security exceptions should be narrow: allow the comment address, not the whole admin area.
Fix 14: Check the Database Comments Table and Repair It
Comments live in a database table, and a damaged table refuses new writes while the rest of the site works normally. The form submits, the server tries to write, the write fails, and the visitor sees nothing. Site Health reports database problems, and the host can repair tables safely. Take a backup first, because repair changes the database directly.

- Take a full backup of the site, including the database, before touching anything.
- Open Tools, then Site Health, and read the Status tab for critical database issues.
- Expand the Info tab and check the Database section for errors or warnings.
- Ask your host to check the comments table and repair it if it is marked as crashed or damaged.
- Alternatively, use a database management tool only if you are confident, and repair the comments table specifically.
- After any repair, submit a test comment in a private window and check it appears or lands in moderation.
- Keep the backup until comments submit reliably for a full day.
- Never run a database repair without a backup — repair can discard damaged rows, and the backup is the only way back.
- A full database, where the hosting quota is reached, also blocks writes — check the database size with the host.
- If Site Health shows no database issue, the table is probably healthy, and the fault lies elsewhere.
- The host repair route is the safer path for most site owners, because the host can also check the database server itself.
Fix 15: Update WordPress, the Theme and Plugins, and Re-Test the Default Form
Outdated software carries known comment bugs, fixed in later releases. An old theme can load an outdated comment template, an old spam plugin can misjudge real comments, and an old WordPress core can mishandle the submission. Updating everything, then re-testing with the default form, clears the version-mismatch class of faults. Back up first, and test after each group of updates.
- Take a full backup of the site, including files and the database.
- Go to Dashboard, then Updates, and note what is available.
- Update WordPress core first, if an update is offered, and wait for it to finish.
- Update the active theme next, and recheck the comment settings after the theme update.
- Update plugins in small groups, submitting a test comment after each group.
- Clear all caches, and submit a final test comment in a private window on the default form.
- Restore custom comment features one at a time, testing after each, so a faulty feature is caught immediately.
- Update on a staging copy first if the site is busy — updates can change the comment form’s appearance as well as fix bugs.
- A test comment that works after updating proves the fault was a fixed bug, and no deeper repair is needed.
- Keep WordPress, the theme, and plugins updated on a regular schedule afterwards, so comment faults do not return with age.
- Delete the test comments afterwards, so the live post shows only genuine discussion.
What to Avoid
- Do not remove spam protection permanently to fix submissions — the spam flood that follows is worse than the original fault.
- Do not edit the database directly unless you have a backup and know exactly what you are changing.
- Do not install nulled or pirated themes and plugins — they can carry malware and break the comment form.
- Do not test only while logged in as admin — the form behaves differently for visitors, and logged-in tests hide the real fault.
- Do not delete genuine comments from the spam queue without checking — real readers’ comments hide there.
- Do not leave the security firewall paused as a fix — add a narrow exception for the comment address instead.
- Do not ignore the pending queue — comments held for moderation are successes waiting for approval, not failures.
Frequently Asked Questions
Why is wordpress comment form not submitting with no error message?
Because WordPress often refuses a submission silently: a failed validation, an expired security token from a cached page, or a spam verdict all reload the page without explaining. Work through Fix 1, Fix 6, and Fix 12: submit carefully with all fields filled, check the pending and spam queues, and clear the cache with an exclusion for post pages. One of those three explains most silent failures.
Why do comments work on new posts but not on old posts?
Because of the auto-close setting, which closes comments on posts older than a set number of days. New posts are inside the limit, old posts are past it. Fix 3 shows how to change the setting and reopen individual old posts. The per-post switch in Fix 2 must be turned on for each already-closed post, because changing the site-wide setting does not reopen them.
Why do my comments go to spam even though they are genuine?
Because spam filters judge comments on links, wording, and sender history, and a genuine comment with several links or trigger words can score as spam. Check the spam queue with Fix 6, mark genuine comments as Not Spam, and review the moderation word list for over-broad entries. A spam plugin set to its strictest level catches more genuine comments — lower the strictness one step and test again.
Do visitors need an account to comment on my site?
Only if the login requirement is switched on. With the default settings, visitors comment with a name and email address, no account needed. If the “users must be registered and logged in” setting is ticked, visitors see a login link instead of the form. Fix 4 shows how to check and change the setting, and how to test as a logged-out visitor.
Can a caching plugin really stop comments from submitting?
Yes. Cached pages serve the comment form with a security token from when the page was cached, and the server refuses an expired token. The form looks perfect and the refusal is silent, which makes this cause hard to spot. Fix 12 excludes post pages from caching and purges the stale cache, which ends the fault while keeping caching for the rest of the site.
Will switching themes delete my existing comments?
No. Comments are stored in the database, independent of the theme. Switching themes changes only the form and the display, never the stored comments. Fix 9 uses a brief theme switch purely as a test, and switching back restores the original appearance with all comments intact. The same applies to plugin tests: disabling a plugin does not delete comments.
Conclusion
When wordpress comment form not submitting silences your readers, start with a careful logged-out test, then check the post settings, the queues, and the spam guard, and only then test plugins, themes, caches, and the database. Most forms are fixed by the first seven fixes, because the fault is a setting, a queue, or a guard — not damage. Finish by submitting a test comment as a visitor and watching it appear or land visibly in moderation, because a test comment with a visible result is the proof the form truly works. Check the pending queue daily from now on, and no genuine comment will wait unseen again.
