- Issue created by @mlncn
- ππΊHungary bpstr
Hi, thanks for the tip. I'll prepare a dev release after some refactoring.
I have checked every other available module which is listed in the readme, and in some way, all of these modules tried to export referenced entities too which could result in possible circular dependencies that caused memory overflow.
Other problem was using some kind of mapping or switch statement to export field values and that caused custom content entities impossible to export.I needed a solution where config referenced entities could be exported in the exact same way as a config entity. Don't really need dependencies since that may exist or can be reproduced in different ways or even large amounts.
Another key point was to have entities exported separately and easy to edit format:
content/sync/node.page.13862278-4da1-4337-8980-864n0tbad169.yml
The file contains the following format just like a config entity:
uuid: 13862278-4da1-4337-8980-864n0tbad169 langcode: en type: node bundle: page id: '1' dependencies: config: - node.node_type.page - field.field.node.page.body entity: - 'user:user:e2174f02-0609-4883-9216-37ff10e3de48' fields: nid: '1' vid: '1' revision_timestamp: '1688432335' revision_uid: target_id: '1' _entity: 'user:user:e2174f02-0609-4883-9216-37ff10e3de48' revision_log: { } status: '1' uid: target_id: '1' _entity: 'user:user:e2174f02-0609-4883-9216-37ff10e3de48' title: 'Node title' created: '1688432309' changed: '1688432613' promote: '0' sticky: '0' default_langcode: '1' revision_default: '1' revision_translation_affected: '1' path: langcode: hu menu_link: { } body: value: '<p>Formatted HTML contents of the page</p>' summary: '' format: rich_text
This allows more complicated import methods with dependency check
- Status changed to Fixed
over 1 year ago 11:00am 7 July 2023 - Status changed to Fixed
over 1 year ago 10:28am 11 July 2023