Add an option to archive config and/or SQL data when uninstalling modules

Created on 17 September 2013, over 11 years ago

Updated 11 February 2025, 12 days ago

Updated: Comment #0

Problem/Motivation

A follow-up to #1199946: Disabled modules are broken beyond repair so the "disable" functionality needs to be removed →

In some edge cases you may need to refer to config or data even after a module in uninstalled.

Or, if you are a developer, you could migrate that config or data back in if you later re-install the module or install a related one that can use the same data. In comment #227 https://drupal.org/node/1199946#comment-7538503 it was suggested that core have a general backup/restore functionality. I don't know that we want to build that for core, but this could feed into a contrib solution for "unarchiving".

In addition, at least the option to archive config and/or data might take some of the fear out of having only the uninstall option.

Proposed resolution

When uninstalling a set of modules, provide default off option to archive configuration or tables. The tables can be discovered via hook_schema (e.g. archive by renaming them perhaps including the module's schema version instead of dropping them).

Remaining tasks

TODO

User interface changes

Added option for uninstall process. Needs perhaps help text and documentation.

API changes

None

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

base system

Created by

🇺🇸United States pwolanin

Live updates comments and jobs are added and updated live.

stale-issue-cleanup

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 12 days ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024