Closed (duplicate)
Project:
Single Content Sync
Version:
1.4.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Issue tags:
Reporter:
Created:
12 Jan 2024 at 01:19 UTC
Updated:
4 Dec 2024 at 12:27 UTC
Jump to comment: Most recent
Comments
Comment #2
abrammYou're right, comments aren't currently supported. I'll check what's needed to add support.
Comment #4
abrammI've pushed an initial boilerplate for the Comments entity type support class.
A challenging part would be exporting references to the parent Node (which should already exist in the system) and a reference to the parent comment (which should already exist as well).
As an option, we could add a setting to export the Node with all of its child Comments, but that could not work if there're a lot of comments for the node.
Keeping this open for now.
Comment #5
joekings commentedThanks, just tried it, export worked again, had a different output than when i tried it yesterday, but am getting an error on import
SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'entity_type'
> cannot be null
Comment #6
abrammHi joekings,
Sorry if I haven't been clear, the PR is not ready for testing. It's just some basic sceleton code.
Comment #7
abrammComment #8
leeksoup commented@abramm - is there any update to this feature? I have a need to sync specifically comments in the Forum module, but I think the comment entities are the same as any other comments in Drupal.
Looking at one of my comment entities, I see that this is its data structure:
Which of these fields needs to be mapped in the Comment.php plugin?
Comment #9
leeksoup commentedRe #4
How difficult would it be to do this option? I don't have a lot of comments per node so this might work for me.
Comment #10
nginex commentedAll the work should happen in #3478941: creating a comment exporter plugin