Fix timeout when deleting a language with many translations #4084
+7
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the Internal Server Error that occurs when deleting a language with many translations.
Problem
When deleting a language, all translations (pages, events, POIs) with that language get cascade-deleted. For each deletion, the linkcheck library's
pre_deletesignal fires and callsget_absolute_url(). With thousands of translations, this causes a timeout before the DELETE query reaches the database.Evidence
region_actions.pyalready usesdisable_listeners()when deleting regionslanguage_tree_actions.pywas missing this patternSolution
Wrap
language_node.delete()withdisable_listeners()- the same pattern already used for region deletion.Test plan
Fixes #3997
🤖 Generated with Claude Code