•

My WordPress form stopped working after an update or a move

There are two quite different kinds of broken form. In one, the visitor presses Send and the form spins, shows an error or does nothing, so the message never leaves the page. In the other, the form says thank you and the email never arrives. The second kind is covered in why a contact form says “sent” but nothing arrives. This guide is mostly about the first kind, and about what the three most common changes do to a form that was working. Both kinds are part of what I fix under WordPress forms and email.

Is this what you’re seeing?

  • Your WordPress forms stopped working after a plugin update.
  • Your forms stopped sending after you changed hosting.
  • The form stopped working after you enabled reCAPTCHA, and now says it can’t verify you’re human.
  • The Send button spins forever, or nothing happens when it’s clicked.
  • An error such as “There was an error trying to send your message. Please try again later.”
  • It works when you’re logged in, but not for visitors, or not on mobile.
  • The form has vanished from the page, leaving a gap or a line of code in square brackets.

What usually causes it

An out-of-date cached script

Forms rely on JavaScript to submit. Caching and optimisation plugins often combine, shrink or delay a site’s scripts, and keep the result. After a form plugin updates, the cached copy can still be the old code, which no longer matches. A “delay JavaScript” setting can also hold the form’s script back until it’s too late. How to tell: the form works when you’re logged in (most caching is skipped for logged-in users) but fails in a private window, or it starts working as soon as you clear the cache.

A plugin or page builder out of step

Some forms depend on two plugins that must match. Elementor’s form widget is part of Elementor Pro, so when the free Elementor and Elementor Pro end up on versions that don’t work together, the form is often one of the first things to go. Form plugins with paid add-ons can fall out of step the same way. How to tell: the form widget is missing or broken in the editor, the Plugins screen shows a warning that one plugin needs a different version of another, or the problem started on the day of an update. Finding a stable Elementor and Elementor Pro pair goes into this in detail.

reCAPTCHA keys that don’t match the form or the domain

reCAPTCHA comes in versions that need different keys: the “I’m not a robot” box (v2) and the invisible score (v3). Keys made for one don’t work in the other. Each key also has a list of domains it’s allowed on, so a move to a new domain, or a staging copy, breaks it. Two plugins both adding reCAPTCHA to the same page can clash, and a v3 score set too strictly turns real people away. How to tell: the reCAPTCHA box or badge shows “Invalid domain for site key” or “Invalid key type”, or every submission fails the check, including yours.

A cookie banner or script delay blocking the check

reCAPTCHA loads from Google. Many cookie banners hold back Google’s scripts until the visitor accepts, and some optimisation plugins delay them. If the check never loads, the form can’t pass it. How to tell: in a private window, the form works after you accept all cookies but fails after you decline them.

The new host blocking the form’s request

When a visitor presses Send, most forms pass the message to WordPress in the background. A security plugin, the new host’s firewall or a Cloudflare rule can see that request as suspicious and block it, so the form spins and then shows a general error. How to tell: it started with the move, and your security plugin or host’s firewall log shows blocked requests at the times you tested.

The new host sending email differently

If the form submits fine after a move but the emails stop, the form is working and the email isn’t. The new server may block outgoing mail, it isn’t in your domain’s SPF record, or the SMTP plugin’s connection didn’t survive the move. How to tell: the form’s entries screen shows the new submissions, but no emails arrive. Sending through your own email provider with an SMTP plugin is the fix that doesn’t depend on the server.

What you can safely try

Take a backup first. Every step here can be undone.

  1. Test the form yourself in a private browser window, and from a phone on mobile data. Write down exactly what happens and any message it shows.
  2. Look in the form plugin’s entries screen. If your tests are there, the form submits and the problem is email. If they’re not, the form itself is failing.
  3. Clear every cache: your caching plugin, your host’s cache and Cloudflare if you use it. On an Elementor site, also use Elementor’s own option to regenerate its files, under its Tools.
  4. In your optimisation plugin, exclude the form’s page from combining and delaying JavaScript, or switch those options off for a test. Switch them back on if it makes no difference.
  5. If it started with reCAPTCHA, check which version the form plugin expects, and that the keys you entered are for that version. In Google’s reCAPTCHA admin page, check your domain is on the key’s list. Make sure only one plugin adds reCAPTCHA.
  6. For a short test, switch the form from reCAPTCHA to the plugin’s honeypot setting, if it has one, and try again. If the form then works, you know where the problem is. Switch back, or choose a better option from what actually stops contact form spam.
  7. Test with cookies declined. If the form fails, ask whoever handles your cookie compliance how reCAPTCHA should be treated, or use a check that doesn’t load anything from Google.
  8. If it started with an update, don’t roll plugins back at random. Rolling back a plugin safely explains how to pick a version and undo it if it doesn’t help.

When to stop and get help

  • You’re losing enquiries or bookings now, and can’t tell how long the form has been broken.
  • Fixing it would mean rolling back Elementor, Elementor Pro or another pair of plugins, and you don’t know which versions work together.
  • A security plugin or the host’s firewall is blocking the form, and you’d need to change its rules.
  • The form takes payments, bookings or file uploads.
  • As soon as you turn reCAPTCHA off, spam floods in.
  • You’ve changed several settings and no longer know which ones were already like that.

A real example

A restaurant’s site built with Elementor ran into trouble during maintenance and hosting work. The free Elementor plugin and Elementor Pro had ended up on versions that didn’t work together. Among other things, the contact form stopped working and the popup menu wouldn’t open. Updating everything to the newest versions wasn’t the safe answer there. I worked out a pair of Elementor and Elementor Pro versions that worked together and with the rest of the site, and restored those. The contact form and the popup were back to a working state with them, without rebuilding either.

The lesson I take from jobs like that is to fix the cause rather than the form. Rebuilding the form, or swapping to a different form plugin, would have left the mismatched pair in place, and the popup menu broken too.

Getting it fixed

I’ll take a backup, work out which change broke the form, fix that, and test every form on the site, including from a private window with cookies declined. See WordPress forms and email for what’s covered. A WordPress repair is a fixed £119, which covers finding the problem and up to 90 minutes of fixing it. Most repairs fit in that, and you’re never charged more without agreeing first.

If you’re missing enquiries right now and can’t wait, see emergency WordPress support.

Questions

Why does my form work when I’m logged in, but not for visitors?

Because visitors see the cached version of the page and you usually don’t. The cached copy may carry old scripts, or an old security code that the form now rejects. Clear the cache and test again in a private window.

My form stopped working after enabling reCAPTCHA. Should I just turn it off?

For a quick test, yes. Left off, many forms soon fill up with spam. Fix the keys or the domain list, or swap to another kind of check, rather than running with no protection.

We changed hosting and the forms stopped sending. Do we need new reCAPTCHA keys?

Only if the domain changed. If it did, add the new domain to the key’s list in Google’s reCAPTCHA admin page. If the domain is the same, look at the new host’s firewall and at how the server sends email instead.

Can I get back the messages people sent while it was broken?

If the form never submitted, there’s nothing to get back: the message stayed in the visitor’s browser. If the form submitted and only the email failed, check the entries screen, because many form plugins keep a copy.

Is it a problem with my form plugin?

Sometimes, but less often than people think. Each plugin has its own weak spots, such as Contact Form 7’s mail tags or Elementor forms needing Elementor Pro. Caching, spam checks and the server are the more common causes after a change.

Written by Peter Claridge, who fixes WordPress sites for businesses across the UK from Reading. Last checked on WordPress 7.1, November 2026.