Uninstall allowed_formats after D10.1 upgrade?

Created on 2 February 2024, over 1 year ago

After upgrading to Drupal 10.1.x and running database updates, should we be uninstalling the allowed_formats module? If so, maybe that should be added to the project page under What do you need to do?

πŸ’¬ Support request
Status

Active

Version

3.0

Component

Documentation

Created by

πŸ‡¨πŸ‡¦Canada chrisck BC, Canada

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @chrisck
  • From the module page:

    Important updates in the 3.0.0 release (3.0.x branch)

    • Since Drupal 10.1.0, limiting the text formats per field instance is a feature provided by Drupal core. Read https://www.drupal.org/node/3318572 β†’ for details.
    • In the 3.0.0 release, the allowed formats feature has been removed as obsolete, but we provide an update path from existing sites to move the allowed formats, as they were stored by the previous versions of the module, to Drupal >=10.1.0 way, in field settings.
    • The module provides also a feature that allows site builders to hide the formatted text format help and guidelines. Even this feature is still preserved in the 3.0.x module branch, there is an issue that aims to move it in Drupal core in the future. See https://www.drupal.org/i/3323007 β†’ .

    So it depends if you use the feature of this module to hide the formatted text format help and guidelines. That functionality isn't in Core yet.

  • Status changed to Fixed 12 months ago
  • If you aren't sure whether a site uses the feature, uninstall the module and export site config in a dev environment. If a config file besides core.extension.yml was changed, then the module was still used.

  • Automatically closed - issue fixed for 2 weeks with no activity.

  • πŸ‡ΊπŸ‡ΈUnited States joegl

    This might save others some grief / catastrophe in data loss. We recently had an issue where we uninstalled the allowed_formats module at the same time as the field configurations were updated to remove the module as a dependency. The order of the config import then went like this:

    1. Import core.extension.yml (uninstalls allowed_formats module). Because the active configuration on the site still had allowed_formats as a dependency for the fields, it deleted those fields.
    2. Update field configurations to remove allowed_formats as a dependency. Because the uninstalling of the module deleted the fields, this step actually re-created the fields.

    This resulted in losing all the data for the fields. I would recommend making sure all the fields are correctly configured to not have the allowed_formats module as a dependency, and then uninstalling the module at a later time. Or write a database update to manually update the relevant field configurations as part of the deployment.

Production build 0.71.5 2024