Rollback library

WordPress plugin rollback archive

Use this hub to discover older versions of popular WordPress plugins and safely roll back when updates cause problems. Every rollback page uses official ZIP files from WordPress.org, so you always download original, unmodified plugin releases.

56,432 plugins synced
556,891 rollback versions available
Last sync: 18 hours ago

Tip: bookmark this page as your central starting point whenever you need to roll back a plugin update or compare older releases for debugging.

Search for a plugin rollback

Start typing a plugin name or slug (for example, elementor, woocommerce, classic-editor). Select a result to open its dedicated rollback page with all available versions.

You can search by full plugin name ("WooCommerce") or by slug (woocommerce, wordfence, classic-editor).

Most popular plugin rollbacks

These plugins have the highest number of active installs. Use their rollback pages to safely downgrade if a recent update broke layouts, introduced regressions, or caused compatibility issues on production sites.

Classic Editor

9,000,000 installs • v1.6.7

Enables the previous "classic" editor and the old-style Edit Post screen with TinyMCE, Meta Boxes, e… Read more

Rollback classic-editorView rollback

WooCommerce

7,000,000 installs • v10.3.5

Everything you need to launch an online store in days and keep it growing for years. From your first sale to m… Read more

Rollback woocommerceView rollback

LiteSpeed Cache

7,000,000 installs • v7.6.2

All-in-one unbeatable acceleration & PageSpeed improvement: caching, image/CSS/JS optimization...

Rollback litespeed-cacheView rollback

Yoast Duplicate Post

4,000,000 installs • v4.5

The go-to tool for cloning posts and pages, including the powerful Rewrite & Republish feature.

Rollback duplicate-postView rollback

Duplicate Page

3,000,000 installs • v4.5.6

Duplicate Posts, Pages and Custom Posts easily using single click

Rollback duplicate-pageView rollback

WordPress Importer

3,000,000 installs • v0.9.5

Import posts, pages, comments, custom fields, categories, tags and more from a WordPress export file.

Rollback wordpress-importerView rollback

Recently updated plugins

When a plugin releases a fresh version, issues can slip through. This list highlights plugins that have been updated most recently so you can quickly roll back if a new release causes errors, conflicts or visible layout changes.

Recently updated plugins could not be loaded from the BugWP API.

Newest plugins with rollback available

These are the most recently added plugins in the BugWP rollback library. Even new plugins quickly gain multiple versions, and as soon as WordPress.org exposes them, you can roll back from here.

Dan's Annotator
v1.1.0

Lightweight front-end annotation tool with threads, tagging, and collaborator sessions.

Archive NBP
v1.1

A WordPress plugin to display Bank of Poland currencies rates. Allow to view rates as Gute… Read more

Inline Context
v2.3.6

Add inline expandable context notes with direct anchor linking. Optionally show the notes … Read more

Nuttifox Support
v1.0.0

Nuttifox Support gives WordPress owners direct access to a specialist WordPress support ag… Read more

Repostra
v1.0.8

Integrate Repostra content creation platform with your WordPress site, allowing you to aut… Read more

LeadBlaze Chat
v1.0.0

AI-powered chat widget for WordPress. Lightweight, responsive, and easy to integrate with … Read more

FocusEdit
v1.0.0

Enhance the block editor interface with floating panels, manual pinning, and smart expansi… Read more

Canaia Assist
v1.0.0

Conecta tu asistente Canaia.Assist con tu sitio de WordPress para habilitar el chat de asi… Read more

Variation Hub
v1.0.0

Professional WooCommerce variation management with Excel-like spreadsheet interface for bu… Read more

AI Tool Center
v1.3.0

AI Tool Center brings NimBot — a sleek, customizable AI assistant — to your WordPress webs… Read more

How the BugWP rollback system works

BugWP provides a dedicated rollback catalog built from the official WordPress.org plugin repository. Plugin information and available versions are refreshed regularly in the background, so what you see here stays closely aligned with the latest data from WordPress.org.

Instead of manually hunting through changelogs or guessing download URLs, you can search once, open a rollback page, and immediately see version history, download links, and WP-CLI examples for the plugin you are working with. This keeps rollback workflows fast, predictable, and easy to repeat across multiple sites.

BugWP focuses purely on read-only plugin data. It doesn't host or modify ZIP files – it simply helps you discover which versions exist and gives you safe, direct download links back to WordPress.org.

When should you roll back a WordPress plugin?

  • After a breaking update. A plugin update causes a fatal error, white screen, or incompatible PHP/WordPress requirement.
  • Layout or UX regressions. Critical templates, checkout pages or forms look wrong after an update and you need a short-term fix.
  • Performance regressions. A new version significantly slows down page loads, database queries or API calls.
  • Plugin conflicts. A fresh release clashes with other plugins or the theme and you need time to coordinate fixes.

Rolling back should almost always be temporary. Use it to stabilize a production site, then test and move forward to a secure, supported version as soon as the upstream issue has been addressed.

Best practices for safe plugin rollbacks

  1. Work on a staging site when possible. Clone your production site to a staging environment, test the rollback there, and only then switch versions on the live site.
  2. Always create a full backup. Take a database and file backup before changing plugin versions so you can revert if something goes wrong.
  3. Rollback one plugin at a time. When debugging, change only one plugin's version at a time so you can clearly see which change fixed (or caused) the issue.
  4. Monitor logs and key flows. After a rollback, watch your error logs and test important user journeys like checkout, login, and forms.
  5. Plan a path forward. A rollback is not a long-term solution. Track the upstream bug report or changelog and plan to move back to a secure, current release.

For power users and agencies, combining these rollback pages with WP-CLI commands and staging environments can turn plugin version management into a predictable, low-risk workflow.

FAQ: WordPress plugin rollback with BugWP

Is it safe to use older versions of plugins?

Older versions can contain known security or compatibility issues, so you should only roll back as a short-term fix while you investigate the problem or wait for an official patch. Always keep backups and avoid running very outdated versions for long periods.

Where do the ZIP files come from?

Every download link on BugWP points directly to the official WordPress.org download servers. BugWP does not host, alter, or repackage plugin files. It simply indexes available versions and makes them easier to discover.

Can I use WP-CLI to roll back a plugin?

Yes. Each plugin rollback page shows a ready-made WP-CLI command you can run on your server, for example wp plugin install elementor --version=3.16.2. This is ideal for advanced users and automated deployment workflows.

Does BugWP change anything in my WordPress dashboard?

The BugWP rollback pages are separate from the official Plugins screen. You can browse, search, and download older versions here, then install them manually or via WP-CLI on your sites.

Important: BugWP does not host or modify plugin ZIP files. All downloads and version data are mirrored from the official WordPress.org plugin repository.