Resolve "Offline fallback page for django legacy pages is misleading in some situations"

Closes #838 (closed)

added type::bug label

assigned to @yuha

changed target branch from master to release-3.0

added 53 commits

• ccce4818...8c7ae257 - 42 commits from branch release-3.0
• 75c1a5e6 - 1 earlier commit
• 49dbf41a - Translated using Weblate (Ukrainian)
• a848198f - Translated using Weblate (Ukrainian)
• d8ebd660 - Translated using Weblate (Ukrainian)
• 4687ad34 - Translated using Weblate (Russian)
• f217f5b6 - Translated using Weblate (German)
• 244b0a87 - Translated using Weblate (Ukrainian)
• b1e6b66c - Translated using Weblate (Russian)
• 6e5e73e8 - Translated using Weblate (German)
• 49e89725 - Translated using Weblate (Ukrainian)
• 6fd6b558 - Translated using Weblate (Ukrainian)

Compare with previous version

added 3 commits

• 6f847c2c - Change accepted status codes for legacy page resposes
• a7a16cb0 - Reword offline fallback page
• 9232eb3e - Add changelog

Compare with previous version

marked this merge request as ready

assigned to @nik and unassigned @yuha

added 3 commits

• 4d2f8119 - Change accepted status codes for legacy page resposes
• cebe47c1 - Reword offline fallback page
• 99d78f53 - Add changelog

Compare with previous version

added 5 commits

• 99d78f53...f95d975a - 4 commits from branch release-3.0
• 393043e3 - Merge branch 'release-3.0' into...

Compare with previous version

mentioned in commit 65d93ab3

merged