- Issue created by @valthebald
- πΊπ¦Ukraine abramm Lutsk
That'd be a nice addition.
I would still ignore some field types though (like entity references) as they could be unsafe to import/export without special handling. - Merge request !88Issue #3414711: Default plugin for fieldable entities. β (Open) created by valthebald
- Status changed to Needs review
5 months ago 8:29am 16 January 2024 - Status changed to Needs work
5 months ago 9:07am 16 January 2024 - π§π¬Bulgaria valthebald Sofia
Back to needs work because I haven't tested the full flow import then export
- Status changed to Needs review
5 months ago 9:59am 16 January 2024 - πΊπ¦Ukraine abramm Lutsk
Hi valthebald,
I didn't test this yet but the code looks promising. We're going to work on the module issues at Global Contribution Weekend which is happening next week, will probably check it there.
Thank you for your effort!
- π«π·France erwangel
Thank you for this plugin which as it says aims to "reduce the need in custom plugins for each content type"! This MR-88 applied and worked perfectly on D10.2.3 and SCS 1.4.4 for transferring feed entities (type feeds_feed). I just had to change the 'owner' field in the export yaml text ; this is hardcoded, to 'uid'. Perhaps you should set the default name of the entity owner to 'uid' that is more likely to meet than 'owner' or at least set a comment close to the corresponding line in yaml to attract user's attention that they may have to adjust the name of this field. I also had to move by hand the 'source' field which is of type 'uri' but this is rather a general issue, not this plugin's concern, as SCS lacks definition for 'uri' field in SingleContentSyncFieldProcessor.