Content translation isn't supported right now, which is not really intentional, the module is just still in development.

We should export the default content translation to content/*, and translations to content//*, which is similar to how config export directory structures look. Importing is a bit more tricky - we use a chunked sorted graph to determine how to import content with concurrency without blowing anything up, and a translation could have an entity reference that the default translation does not have.

Should be fun! I'll try to get a patch soon.

CommentFileSizeAuthor
#3 2980506-3.patch36.6 KBsamuel.mortenson
#2 2980506.patch29.12 KBsamuel.mortenson

Comments

samuel.mortenson created an issue. See original summary.

samuel.mortenson’s picture

samuel.mortenson
he/him
Primary language English
commented
Status: Active » Needs review
StatusFileSize
new 2980506.patch29.12 KB

Wow, this was a ton of work!

samuel.mortenson’s picture

samuel.mortenson
he/him
Primary language English
commented
StatusFileSize
new 2980506-3.patch36.6 KB

Missed the new files.

The last submitted patch, 2: 2980506.patch, failed testing. View results

samuel.mortenson’s picture

samuel.mortenson
he/him
Primary language English
commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.