The confirmation email already used the current language
as a language prefix in the URLs. However, the new answer
notification email and the outgoing message email are sent
from other contexts (from celery beat or in response to a
new email arriving) where there is no HTTP request to
provide a preferred language. However, each of these emails
is associated with an instance, and their config has a default
language. These commits make sure that default language
is used in the links in these emails.
Coverage increased (+0.005%) to 98.141% when pulling c0e83488d388a059f79af835d760259ccbf447a3 on email-links-should-be-instance-default-language into a8cb5ff1cf7a4cd27dbfff42e82f22690fc5ea12 on alpaca.
The confirmation email already used the current language as a language prefix in the URLs. However, the new answer notification email and the outgoing message email are sent from other contexts (from celery beat or in response to a new email arriving) where there is no HTTP request to provide a preferred language. However, each of these emails is associated with an instance, and their config has a default language. These commits make sure that default language is used in the links in these emails.