- Issue created by @Kristen Pol
- Assigned to Kristen Pol
- Status changed to Postponed
over 2 years ago 6:18am 26 February 2023 - 🇺🇸United States Kristen Pol Santa Cruz, CA, USA
Hmm... this might be due to the redirect branch updates... marking postponed until I can test further.
- Issue was unassigned.
- Assigned to Kristen Pol
- Status changed to Active
almost 2 years ago 5:13pm 7 January 2024 - 🇺🇸United States Kristen Pol Santa Cruz, CA, USA
I think this is working so assigning to myself for more testing.
- 🇺🇸United States Kristen Pol Santa Cruz, CA, USA
Confirmed this is still a bug.
- Issue was unassigned.
- Status changed to Fixed
almost 2 years ago 9:54pm 7 January 2024 - 🇺🇸United States Kristen Pol Santa Cruz, CA, USA
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 - Status changed to Fixed
almost 2 years ago 9:54pm 7 January 2024 - 🇺🇸United States Kristen Pol Santa Cruz, CA, USA
Part of 1.6.0 release → .