Skip to content
webfixed

Guides / WordPress

Contact Form 7 error after updating a plugin

By Michael Broadbridge. Last checked 14 November 2026 on WordPress 7.1, Contact Form 7 6.2.

Short answer

Contact Form 7 shows "There was an error trying to send your message. Please try again later." both when the email fails and when a submission is marked as spam. A red border means sending failed and orange means spam. Check the Mail tab and SMTP plugin for red, reCAPTCHA or Akismet for orange, and any recently updated add-on.

Symptoms

You may see one of these messages:

There was an error trying to send your message. Please try again later.

One or more fields have an error. Please check and try again.

Sending mail has been aborted.

Sender email address does not belong to the site domain.

You are not allowed to upload files of this type.

  • After an update, the form shows "There was an error trying to send your message. Please try again later." in a box with a red or orange border.
  • The spinner next to the submit button keeps turning and no message ever appears.
  • A multi-step form, or a form with a file upload, fails while simple forms on the same site still work.
  • The problem started when Contact Form 7, an add-on for it, or a caching or security plugin was updated.

Causes, most likely first

  1. The email failed to send

    Contact Form 7 hands the email to WordPress. If WordPress reports a failure, for example because the host blocks PHP mail or an SMTP plugin has lost its connection, the form shows the error with a red border.

  2. The submission was marked as spam

    reCAPTCHA, Akismet, Cloudflare Turnstile or the disallowed words list can mark a real message as spam. Contact Form 7 then shows the same error with an orange border, and no email is sent.

  3. An add-on no longer matches Contact Form 7

    Add-ons for multi-step forms, conditional fields and similar features call Contact Form 7’s own functions. When an update changes one of those functions, the add-on can crash with a PHP fatal error.

  4. The REST API is blocked

    Contact Form 7 sends each submission to the WordPress REST API, at an address beginning /wp-json/contact-form-7/v1/. A security plugin or firewall rule that blocks the REST API for visitors stops the form.

  5. Cached pages and scripts

    Caching and optimisation plugins can keep serving old copies of pages and scripts after an update, or delay the reCAPTCHA script so it has not run when the form is sent.

How to fix it

Read the colour of the message box

Contact Form 7 uses the same default wording for a failed send and a spam result, so the wording alone does not tell you which happened. Its standard stylesheet gives each result a different border colour. Some themes restyle the box, in which case use the next section instead.

  • Red: WordPress could not send the email, or an add-on stopped the send. The message "Sending mail has been aborted." also appears with a red border.
  • Orange: the submission was marked as spam and no email was sent.
  • Yellow: a field failed validation or the acceptance box was not ticked. Each field with a problem shows its own message underneath.
  • No box at all, with the spinner still turning: the submission never got a proper reply from the site. Look at the REST API, a PHP fatal error or an add-on.

See what the site sent back

Your browser’s developer tools show the reply to each submission. This works in Chrome, Edge, Firefox and Safari.

  1. Open the page with the form, right-click and choose Inspect, then open the Network tab.
  2. Fill in the form and submit it.
  3. Find the request whose name ends in feedback and click it.
  4. A status of 200 means the site replied. Open the Response tab and read the status field: mail_failed, spam, aborted or validation_failed.
  5. A status of 403 usually means a security plugin or firewall blocked the request.
  6. A status of 500 means a PHP error on the server. Turn on the WordPress debug log and submit again to see which plugin caused it.

Fix a failed send (red border)

  1. Open the form and click the Mail tab.Menu: Contact > Contact Forms
  2. Check the To field holds the right address.
  3. Set the From field to an address on your own domain. If it is not, Contact Form 7 shows "Sender email address does not belong to the site domain." in the form editor.
  4. Put Reply-To: [your-email] in the Additional headers box if you want to reply to the visitor, rather than sending from their address.
  5. If you use an SMTP plugin, check it is still active and connected, then send a test email from its settings. An update can leave an expired API key or a disconnected account behind.
  6. If you do not use an SMTP plugin, the site is sending through PHP mail, which many hosts limit or block. Our guide to WordPress not sending emails covers setting up SMTP.

Fix a spam result (orange border)

The free Flamingo plugin, from the author of Contact Form 7, saves every submission, including those marked as spam, and records why.

  1. Install and activate Flamingo, then submit the form again.
  2. Open the Spam view and click the latest message. The side panel shows the submission result and the reason, such as a reCAPTCHA score lower than the threshold or an Akismet spam response.Menu: Flamingo > Inbound Messages
  3. If the reason says the reCAPTCHA response token is empty, the reCAPTCHA script did not run in the browser. Check the keys are still valid, and check optimisation and cookie consent plugins are not delaying or blocking Google’s script.Menu: Contact > Integration
  4. If the reason mentions Akismet, Akismet’s own servers judged the message as spam. Test again with a plain message, and keep Flamingo installed so that real messages caught this way are not lost.
  5. If the reason says the submitted nonce is invalid, the visitor was logged in and the page carried an out-of-date security token. Clear your caches and stop the cache serving pages to logged-in users.

Find an add-on that no longer matches

  1. Turn on the WordPress debug log, submit the form, and open debug.log in wp-content. A line starting "PHP Fatal error" names the file that failed, and the folder in its path shows the plugin.
  2. An error such as ArgumentCountError with "Too few arguments to function" and a function name starting wpcf7_ means an add-on is calling Contact Form 7 the old way.
  3. Check the add-on’s changelog and support forum for a fix, and update it.
  4. If there is no fix yet, roll Contact Form 7 back to the version you had before, using the WP Rollback plugin or the previous versions list on the plugin’s page at wordpress.org. Take a backup first.
  5. Turn off automatic updates for Contact Form 7 until the add-on catches up.Menu: Plugins > Installed Plugins

A rollback is a holding measure. Updates can contain security fixes, so move to the latest version once the add-on works with it.

Clear caches and check the REST API

  1. Clear the cache in your caching plugin, at your host and in Cloudflare or any other content delivery network.
  2. If your optimisation plugin combines, minifies or delays JavaScript, exclude Contact Form 7’s script and the reCAPTCHA script, or switch those options off and test again.
  3. In your security plugin, look for a setting that disables the REST API or limits it to logged-in users. Contact Form 7 needs visitors to reach addresses beginning /wp-json/contact-form-7/v1/.
  4. Submit the form again in a private browser window, logged out, as a visitor would.

If that didn’t work

  1. An upload field rejects every file

    "You are not allowed to upload files of this type." means the file type is not in the field’s allowed list. On one site we look after, Contact Form 7 6.2.4 also showed it for optional upload fields left empty. Version 6.2.4.1 fixed that, so update to the latest release.

  2. A JavaScript error stops the form

    If nothing happens at all on submit, open the Console tab in the developer tools. A red error from another plugin or the theme can stop Contact Form 7’s script running.

  3. A plugin conflict elsewhere

    Deactivate recently updated plugins one at a time, on a staging copy if you have one, and test the form after each.

A fix we made: a multi-step add-on and file uploads

Contact Form 7 6.2.4 changed an internal function that handles uploaded files so that it needs an extra piece of information. A widely used multi-step add-on still called it the old way. On a site we look after, every form step with a file upload then failed with a server error, and the add-on showed an "Error ajax load" alert. Forms without uploads kept working.

Updating both plugins to their latest versions did not fix it, because the add-on still made the old call. We added a small must-use plugin that takes file fields out of the add-on’s step check and checks required uploads itself, and it stays in place until the add-on is fixed. The same alert had appeared on the same site a few weeks earlier for a different reason: a caching plugin serving pages with out-of-date security tokens. Checking the server’s reply for each step showed which cause it was.

When to get help

Stop if the debug log names a fatal error in an add-on and no update fixes it, if the server returns 500 and you cannot find the cause, or if a rollback would leave the site on an old version for a long time. Get help quickly if the form takes enquiries or bookings the business depends on, since every failed submission is lost unless Flamingo is installed.

What a developer would check

  • The server’s reply to each submission and to each step of a multi-step form.
  • The PHP error log for fatal errors in Contact Form 7 add-ons.
  • REST API access for logged-out visitors, through security plugins, firewalls and the host.
  • Caching and script optimisation rules for pages that carry forms.

Describe the problem in your own words and WebFixed gives you an instant fixed quote. Nothing is charged until you accept it.

Related questions

Why does Contact Form 7 show the same error for spam and for a failed email?
Both results use "There was an error trying to send your message. Please try again later." as their default message. You can change either one on the form’s Messages tab, which makes the two easier to tell apart.
Will rolling back Contact Form 7 lose my forms?
No. Forms and their settings are stored in the database, not in the plugin’s files. Take a backup first all the same, and treat the older version as temporary.
Is the form sending emails that I am just not receiving?
Not if it shows the red or orange error. Red means WordPress reported that sending failed, and orange means no email was sent because the submission was marked as spam. A green border with no email arriving is a delivery problem instead.

Written by Michael Broadbridge, Founder of Webgro. First published 14 November 2026. Last checked 14 November 2026 on WordPress 7.1, Contact Form 7 6.2.