You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If in your Django has several languages configured, and your root URLConf is using the new i18n_patterns, then every path under that urlpatterns setup can have two or more versions. Currently, DjangoSEO assumes that every get_absolute_url call will return an unique URL, when that's not the case for multilingual projects.
For instance, when i18n_patterns is active, a call to get_absolute_url can return /en/objects/myobject_slug/ or /de/objects/myobject_slug/, depending on the current request language.
The result of every call to get_absolute_url (or when using request.path) should be unprefixed from the current language, before using it as "key" to save the metadata instance.
The text was updated successfully, but these errors were encountered:
If in your Django has several languages configured, and your root URLConf is using the new
i18n_patterns
, then every path under that urlpatterns setup can have two or more versions. Currently, DjangoSEO assumes that everyget_absolute_url
call will return an unique URL, when that's not the case for multilingual projects.For instance, when
i18n_patterns
is active, a call toget_absolute_url
can return/en/objects/myobject_slug/
or/de/objects/myobject_slug/
, depending on the current request language.The result of every call to
get_absolute_url
(or when usingrequest.path
) should be unprefixed from the current language, before using it as "key" to save the metadata instance.The text was updated successfully, but these errors were encountered: