Merge pull request #4048 from GeotrekCE/fix_menu_item_migration_trans…

…lator_error

Ensure migration steps for menu items can be run separately

docs/changelog.rst

@@ -8,6 +8,7 @@ CHANGELOG
 **Bug fix**
 
 - New menu items targeting static page now open it in the same tab
+- Ensure migration steps for menu items can be run separately
 
 
 2.104.1 (2024-04-03)

geotrek/flatpages/migrations/0011_migrate_flatpage_data.py

@@ -9,7 +9,7 @@
 from django.conf import settings
 from django.db import migrations
 from django.utils import translation
-from modeltranslation.translator import translator, TranslationOptions
+from modeltranslation.translator import translator, TranslationOptions, AlreadyRegistered
 from modeltranslation.utils import build_localized_fieldname
 
 from treebeard.mp_tree import MP_Node
@@ -94,8 +94,12 @@ class FlatPageTO(TranslationOptions):
     # modeltranslation registration is not run on historical models available during migrations.
     # We register FlatPage for translations now so `title_fr`, `title_es`, etc are defined.
     translator.register(FlatPage, FlatPageTO)
-    # MenuItem is already translation-registered from the previous migration
+    # MenuItem is already translation-registered from the previous migration so we cautiously try
     # (it will be needed to copy values in translation fields)
+    try:
+        translator.register(MenuItem, MenuItemTO)
+    except AlreadyRegistered:
+        pass
 
     # Those fields are copied from FlatPage to MenuItem.
     # Dict keys are FlatPage's fieldnames, dict values are MenuItem's fieldnames.