How to unsplit List(text) paragraph fields while keeping data?

Created on 1 February 2023, about 2 years ago
Updated 20 October 2023, over 1 year ago

Problem/Motivation

On a multi-site setup I work in, a lot of paragraph field storages were split between some sites to add new values overtime (bad idea). Now we want to standardize these values for all the sites, by adding all the values from each site to all sites and work from there, removing splits.

If I just add all options to the shared config, and then remove the field from the split, the data stored in the field is lost and everything is back to empty (which makes sense). Is there a way to unify all these split storages into the shared one while keeping the data?

Currently, the way we are dealing with this is moving everything to a new field and then deleting the existing field entirely. I appreciate any suggestions.

💬 Support request
Status

Closed: cannot reproduce

Version

1.0

Component

Documentation

Created by

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

Comments & Activities

  • Issue created by @luiscarvalho
  • 🇨🇭Switzerland bircher 🇨🇿

    I thought you can add values on List(text) fields but not remove them.
    If not via a config import then maybe you can do it with an update hook.

    But I am afraid that config split can not do anything for you here.
    I would try adding all the options to the field storage, and as long as the uuid is the same it should be treated as the same field and possibly update it on an import. But I don't know if that helps. If when splitting you had different uuids for the fields then you need an update hook to set them to be the same so that the config import doesn't remove and add the field again.

  • Status changed to Closed: cannot reproduce over 1 year ago
  • 🇨🇭Switzerland bircher 🇨🇿
Production build 0.71.5 2024