Content not created for non-default-language node

Hmm... this might be due to the redirect branch updates... marking postponed until I can test further.

Unassigning for now.

Target dev version.

I think this is working so assigning to myself for more testing.

Confirmed this is still a bug.

Actually, this was fixed. When I tested earlier I had tracking off so I needed to run queue.

I just tested again with:

• Created Spanish untranslated node without alias with contract tracking on
• Created Spanish untranslated node without alias with contract tracking off and then seed/run queue
• Created Spanish untranslated node with alias with contract tracking on
• Created Spanish untranslated node with alias with contract tracking off and then seed/run queue
• Created Spanish untranslated term without alias with contract tracking on
• Created Spanish untranslated term without alias with contract tracking off and then seed/run queue
• Created Spanish untranslated term with alias with contract tracking on
• Created Spanish untranslated term with alias with contract tracking off and then seed/run queue

The content works as expected. The redirects do not but that's being handled in:

🐛 All canonical redirects are unpublished when translation is unpublished Active
📌 Add language prefix for canonical redirect Active
📌 Add internal path redirect support for multilingual sites Needs review

Part of 1.6.0 release → .