[META] Replace base fields with config fields for individual Rabbit Hole settings

Created on 10 March 2021, over 3 years ago
Updated 28 June 2023, 12 months ago

Problem/Motivation

This is a meta issue to keep the progress of transition from base fields to config fields for individual Rabbit Hole settings.

The change is supposed to fix the common problems related to translations/content moderations/etc. including the following issues:
πŸ› Unable to uninstall submodules Closed: cannot reproduce
#3087824: Unable to save translation when using content_moderation due to EntityUntranslatableFields and rh_action β†’
πŸ› Redirect Urls not translateable - redirects in wrong language Fixed

Other positive changes are:
1) Movement to the model when every fieldable entity will be supported out-of-the-box. We won't need to add integration for each entity type and won't need to maintain a bunch on sub-modules;
2) The database structure should more friendly - we won't expand the default entity table with a bunch of columns when we don't need them. Rabbit Hole settings will be kept in a separate field table.

This is an experimental change and will be available in a new module (branch) version - 2.x.

🌱 Plan
Status

Fixed

Version

2.0

Component

Miscellaneous

Created by

πŸ‡ΊπŸ‡¦Ukraine Matroskeen πŸ‡ΊπŸ‡¦ Ukraine, Lutsk

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

Comments & Activities

Not all content is available!

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

Production build 0.69.0 2024