Remap new references post deleting old references

Created on 12 March 2022, over 2 years ago
Updated 1 November 2024, 20 days ago

Problem/Motivation

Currently the module supports only deletion of old references. Whereas in real time there might a need to remap new nodes to the same references. This patch is a starting point to achieve that.

Steps to reproduce

Not applicable as this is a new feature

Proposed resolution

During deletion we can also check the alternative new node (in this case matching based on title and same content type) and remap the new node. Please note that there should not be more than 2 nodes with the same title in that content type.

Remaining tasks

Make it configurable to do the mapping based on other fields and not just Title (currently hard coded)
Currently, the patch is done when not running via queue. This needs to be done for queue option too

User interface changes

Configuration form to be added to this module

API changes

None

Data model changes

None

Feature request
Status

Needs work

Version

1.0

Component

Code

Created by

🇮🇳India kswamy

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.

  • 🇬🇧United Kingdom scott_euser

    Interesting one! It's a big assumption though that the same title would be an intentional replacement. The bundle check probably partly mitigiates that (e.g. an event and article with same name being a common thing we see) but still I would imagine that:

    1. Maintainers guidance should be seeked out first before putting more effort to see if it's something they'd be interested in.
    2. At least it probably needs to be opt in via module settings rather than default as I expect it'd otherwise be a hard to track down unexpected side effect.
Production build 0.71.5 2024