Problem/Motivation

This is a fantastic module to import and sync content entities from one Drupal installation to another. And I think we should build up on it!

Before importing content into a Drupal site you often need to get a clear view on possible conflicts and what will be imported or updated!

Things to consider are for example:

  • Changed field values if updating content based on a primary key like NID or UUID (Diff view)
  • Different schema (missing fields, changed field types, ...)
  • New revisions for existing entities
  • Missing reference targets
  • ...?

And I think such a review process, informing you about possible issues, would provice more transparency for the import of Drupal Content Entities. The tool would become a supertool ;)

A further thing might be mapping field values. While typically fields values from fields with the same name within the same entity type / bundle from target should go into the same target field name, the module could also offer other fields as target and preselect the one with the same name.
If a target field does not exist, it could be empty and one could select a different target field or leave it empty. That would be super powerful.

Should we split this into two issues? Are there other modules or helpful tools (like migrate) that could help solving this?

PS: A vice versa step for the export could be something like #3498510: Allow to partially export content

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

anybody created an issue. See original summary.

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented

Would be great to get maintainer feedback on this. We'd be interested to contribute this because it would help us in numerous cases, I think. And we love this module! Thank you!

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented
Issue summary: View changes
anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented

Just came across https://www.drupal.org/project/entity_io which seems to contain part of the suggested functionality, but has no tests and seems to be AI-generated in large parts. It seems as single_content_sync is more mature, but maybe things from https://www.drupal.org/project/entity_io can be helpful or both projects could join forces?

In this issue let's focus on the functionality in this module.

nginex’s picture

nginex commented

Hi @anybody,

Interesting ideas from you!

I like a possibility to review changes, its definitely a green light, probably it can also be applicable for drush command, so you can confirm your import after reviewing the changes.

The idea with mapping could be a dedicated issue. Currently it's possible to do so in backend, but having UI is an interesting way to go.

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented

Thank you for the positive feedback @nginex! I know this is not a simple task, but this module looks like the probably most complete syncing / importing (+mapping) solution for Drupal in the wild and this functionality would make a lot of sense for me.