Archivum Inactive Archiver

Preguntas frecuentes

Is archiving safe?

Archiving moves the plugin’s files to another folder without changing them. Nothing in the database is altered. Restoring moves them back.

Can I archive an active plugin?

No. Deactivate it first. This is deliberate: deactivation runs the plugin’s own clean-up code, and that should be your decision.

Where do archived plugins go?

A folder named wp-content/archived-plugins- followed by twelve random characters, for example archived-plugins-3f9a1c0b7d2e, with one folder per plugin inside it. The Archived Plugins screen shows the exact name. Developers can change the location with the archive_inactive_dir filter, for example to move it outside the web root.

Why does the archive folder have random characters in its name?

So that nobody can guess its address. Archived plugins are often old, and old plugins can contain files that are unsafe to run. The plugin already blocks web access to the folder, but some servers ignore that block. A name that differs on every site means that, even there, an outsider does not know where to look. The characters are chosen once per site and do not change.

Do archived plugins get updates?

Not while they are archived: WordPress only updates plugins in the plugins folder. When you restore a plugin, this plugin updates it to its latest version straight away, using WordPress’s own updater. This works for any plugin that shows an update on the Plugins screen, and needs the update_plugins capability. At most five plugins are updated per restore; any others are named so you can update them from the Plugins screen. It can be turned off in Plugins → Archived Plugins → Settings.

Can updating a plugin on restore cause problems?

Rarely, and no more than updating any inactive plugin. The plugin stays inactive after the update. Most plugins make their database changes the next time they are activated, whichever version they come from. If a plugin skipped several versions while it was archived, read its changelog before activating it.

Can I download an archived plugin?

Yes. “Download” under each archived plugin sends it as a zip that can be installed again with Plugins → Add Plugin → Upload Plugin. Only the plugin’s own files are included. It is offered to users who may delete plugins, and works up to 200 MB; for larger plugins, copy the folder over FTP or SSH.

What happens to a deleted plugin’s settings?

Deleting an archived plugin removes its files only. Settings it stored in the database stay, because WordPress removes those only by running the plugin’s own uninstall routine. Archivum Pro’s “Clean up and delete” runs that routine for you; without Pro, restore the plugin and delete it from the Plugins screen, which runs it.

What happens to my archived plugins if I deactivate or delete this plugin?

They stay on disk in the archive folder. Reactivate or reinstall this plugin and it finds the folder again, so they reappear on the Archived Plugins screen. You can also move a folder back into wp-content/plugins by hand over FTP or SSH.

My site runs on nginx. Is the archive folder protected?

Not automatically. nginx does not read .htaccess files, and neither does Apache when the host has switched overrides off. The Archived Plugins screen requests a file in the archive folder from your own site and shows a warning if it is served; Tools → Site Health shows it too. If you see it, ask your host to deny web access to every address beginning /wp-content/archived-plugins (on nginx: location ^~ /wp-content/archived-plugins { deny all; }), or use the archive_inactive_dir filter to store the archive outside the web root.

Can I edit the .htaccess file in the archive folder?

No. The plugin manages .htaccess, web.config and index.php in the archive folder and rewrites them if they change. Put your own rules in the server configuration instead.

Who can archive, restore, download and delete?

Archive and restore need the activate_plugins capability. Permanent deletion and Download also need delete_plugins. Updating on restore needs update_plugins. On multisite all of these need manage_network_plugins. If DISALLOW_FILE_MODS is set, the screen is read-only.

Does it contact any outside service?

Only through WordPress itself: when a plugin is updated on restore, WordPress’s own updater checks for and downloads the update, exactly as it does on the Plugins screen. The Archived Plugins screen also requests a file from your own site, to check that the archive folder is blocked from the web. Nothing is sent to the plugin’s authors.

What is Archivum Pro?

A separate, paid add-on from the same authors, sold at inactivearchiver.com. It needs this plugin. It adds automatic archiving after a period you choose, automatic deletion after a period in the archive (always announced a week ahead, and only after someone has seen the announcement), email reports, Clean up and delete, flags for plugins closed or abandoned on WordPress.org, an activity log, WP-CLI commands and two more Site Health checks. Nothing in this plugin is locked or limited without it.

I get “WordPress cannot write to its files directly on this server”.

Your host requires FTP or SSH credentials for WordPress to change files (you will see the same prompt when installing plugins). This plugin only works where WordPress can write directly.

I used an earlier version under a different name. How do I upgrade?

Earlier versions were distributed in a folder named archive-inactive, archive-inactive-plugins or inactive-archiving-system. Deactivate the old version, install and activate this one, then delete the old one. They use different folder names, so WordPress treats them as separate plugins and will not update one into the other. Everything you archived before is picked up automatically.

A plugin I archived with version 1.0 or 1.1 is not showing.

Open Plugins → Archived Plugins. Version 1.2 and later pick up everything in the archive folder, including folders they cannot identify as a plugin, so nothing is hidden.

Is there a warranty?

No. See “Disclaimer” below.