added another custom-function-point to run after cleanup is completed (#29)

Co-authored-by: Fabian Braun <[email protected]>

Author: wfehr

README.md

@@ -81,14 +81,15 @@ If you have a custom user model, you should designate a "migration user" by spec
 CMS_MIGRATION_USER_ID = <user id>
 ```
 
-If you want to adjust data to get the migration running in your project, there are 2 function-points available:
+If you want to adjust data to get the migration running in your project, there are 3 function-points available:
 
 ```
-CMS_MIGRATION_PROCESS_MIGRATION_PREPARATION = "mymodule.myfunction2"
-CMS_MIGRATION_PROCESS_PAGE_REFERENCES = "mymodule.myfunction"
+CMS_MIGRATION_PROCESS_MIGRATION_PREPARATION = "mymodule.myfunction"
+CMS_MIGRATION_PROCESS_PAGE_REFERENCES = "mymodule.myfunction2"
+CMS_MIGRATION_PROCESS_POST_CLEANUP = "mymodule.myfunction3"
 ```
 
-The latter function is supplied with parameters `page` and `replacement_page`.
+`_PROCESS_PAGE_REFERENCES` is supplied with parameters `page` and `replacement_page`.
 
 ## Running
 Simply run the following command to run the data migration.

djangocms_4_migration/management/commands/migration_cleanup.py

@@ -170,6 +170,16 @@ def _get_page_contents(page):
     return PageContent._base_manager.filter(page=page)
 
 
+def _post_cleanup():
+    custom_function = getattr(settings, "CMS_MIGRATION_PROCESS_POST_CLEANUP", None)
+    if custom_function:
+        module, function = custom_function.rsplit(".", 1)
+        getattr(
+            __import__(module, fromlist=[""]),
+            function,
+        )()
+
+
 class Command(BaseCommand):
     help = "Run after migrations are applied"
 
@@ -224,4 +234,6 @@ def handle(self, *args, **options):
                 for url in page.urls.filter(language=language).order_by("pk")[1:]:
                     url.delete()
 
+        _post_cleanup()
+
         logger.info("Stats: %s", str(stats))