Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

HTTP 410 (Gone) responses · Version history

HTTP 410 (Gone) responses changelog and version history

Latest version
1.2.1
Aug 5, 2026 (3 months ago)
Releases
16
since 2011
In the last year
4
about one every 69 days
Tested up to
WordPress 7.0.8
PHP 7.4 or later

Releases each year

  • 20116 releases
  • 20122 releases
  • 20134 releases
  • 20264 releases

20264 releases

  1. HTTP 410 (Gone) responses 1.2.1Latest

    • The “Maximum number of 404 errors to keep” setting is now capped at 10,000 to prevent unbounded growth of the logged-404s table.
    • Fixed the “Recent 404 errors” pagination controls floating away from the table above them; they now stay aligned beneath it.

  2. HTTP 410 (Gone) responses 1.1.0

    • Compatibility: Tested and confirmed working on WordPress 7.0.
    • Updated minimum WordPress requirement to 5.0.
    • Added Requires PHP: 7.4 declaration to match WordPress 7.0 minimum.
    • Updated admin script enqueue to use the modern $args array form (WP 6.3+).

  3. HTTP 410 (Gone) responses 1.0.3

    • Official release build for WordPress.org plugin directory.

  4. HTTP 410 (Gone) responses 1.0.2

    • Bugfix: Updated version number in plugin header and asset versions.

20134 releases

  1. HTTP 410 (Gone) responses 0.8.2

    • Overhaul settings page UI.
    • Add option to specify how many 404 errors to keep.

  2. HTTP 410 (Gone) responses 0.8.1

    • Add select all helpers to 410/404 lists.

  3. HTTP 410 (Gone) responses 0.7.2

    • Add support for popular caching plugins (W3 Total Cache and WP Super Cache).

  4. HTTP 410 (Gone) responses 0.7.1

    • Database tweaks (change ID to unsigned MEDIUMINT)

20122 releases

  1. HTTP 410 (Gone) responses 0.7

    • Added logging of 404 errors so they can be easily added to the list of obsolete URLs.

  2. HTTP 410 (Gone) responses 0.6.1

    • Bugfix: don’t accept URLs that don’t resolve to WordPress
    • Warn about invalid URLs when permalink settings change

20116 releases

  1. HTTP 410 (Gone) responses 0.6

    • Moved storage of old URLs from the Options API to the database, to avoid issues with long lists.

  2. HTTP 410 (Gone) responses 0.5

    • Added the option to use your own template to display the 410 response. Just add a file called 410.php to your theme folder.

  3. HTTP 410 (Gone) responses 0.4

    • Bugfix: With batch deletes, only the first item being deleted was noted by the plugin

  4. HTTP 410 (Gone) responses 0.3

    • Bugfix: URLs containing non-ascii characters were not always recognised
    • Bugfix: URLs were displayed in encoded form on the settings page
    • Added a mclv_410_response action to allow users to customise the response message when a deleted article is requested

  5. HTTP 410 (Gone) responses 0.2

    • Added wildcard support to URLs
    • Bugfix: don’t check URLs of deleted revisions and new draft posts

  6. HTTP 410 (Gone) responses 0.1

Questions about HTTP 410 (Gone) responses’s releases

What is the latest version of HTTP 410 (Gone) responses?

1.2.1, released on Aug 5, 2026 (3 months ago). It’s tested up to WordPress 7.0.8 and needs PHP 7.4 or later.

How often is HTTP 410 (Gone) responses updated?

4 releases in the last year, about one every 69 days. Its first release on WordPress.org dates from February 2011.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in HTTP 410 (Gone) responses’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.