Problem/Motivation
Using default-content:export-references does not export comments.
Steps to reproduce
- Create a content type that allows comments
- Create a node of the type
- Place a comment on the node
- Export the node using drush dcer
- Notice that the comment is not automatically exported
Proposed resolution
Add support for comments.
Remaining tasks
- Decide whether to treat comments as compound entities and export within the parent entity, or as stand-alone entities
- Create a patch
- Review
- Commit
User interface changes
None.
API changes
None.
Data model changes
None.
Comments
Comment #2
berdirComments are clearly standalone, and the node has no reference to comments, its comments that reference the parent node in a custom DER-like, two-field based reference. The comment field just stores the comment setting and I don't think it's a good match to embed them.
Supporting that lookup in either direction would require comment-specific logic. Open to that as I suspect right now, the comment parent reference isn't properly referenced.
Comment #3
berdirthis already seems to be half-working at least, entity_id does contain the entity UUID. not sure if there's anything to do here.
Comment #4
agentrickardWhen working with forum comments at least, we get this error:
That suggests that the entity_id mapping isn't loading properly.
Comment #5
berdirWhat that probably means is that the reference is there, but not tracked as a dependency, so default_content doesn't know that it needs to create the node before the comments.