Don't inject model admin default if it is not set

javrasya · Nov 17, 2019 · e283b48 · e283b48
1 parent 229b727
commit e283b48
Show file tree

Hide file tree

Showing 3 changed files with 7 additions and 5 deletions.
diff --git a/README.rst b/README.rst
@@ -163,7 +163,9 @@ to create the hooks.
     * ``/admin/river/ontransithook/`` to hook up to a transition
     * ``/admin/river/oncompletehook/`` to hook up to the completion of the workflow
 
-* To create one for a specific workflow object you should use the admin interface for the workflow object itself. One amazing feature of ``django-river`` is now that it creates a default admin interface with the hookings for your workflow model class. If you have already defined one, ``django-river`` enriches your already defined admin with the hooking section. It is default enabled. To disable it just define ``RIVER_INJECT_MODEL_ADMIN`` to be ``False`` in the ``settings.py``.
+* To create one for a specific workflow object you should use the admin interface for the workflow object itself. One amazing feature of ``django-river`` is now that
+it creates a default admin interface with the hookings for your workflow model class. If you have already defined one, ``django-river`` enriches your already defined
+admin with the hooking section. It is default disabled. To enable it just define ``RIVER_INJECT_MODEL_ADMIN`` to be ``True`` in the ``settings.py``.
 
 
 **Note:** They can programmatically be created as well since they are model objects. If it is needed to be at workflow level, just don't provide the workflow object column. If it is needed

diff --git a/docs/hooking/hooking.rst b/docs/hooking/hooking.rst
@@ -12,9 +12,9 @@ to create the hooks.
     * ``/admin/river/ontransithook/`` to hook up to a transition
     * ``/admin/river/oncompletehook/`` to hook up to the completion of the workflow
 
-* To create one for a specific workflow object you should use the admin interface for the workflow object itself. One amazing feature of ``django-river`` is now that it creates a default admin interface
-with the hookings for your workflow model class. If you have already defined one, ``django-river`` enriches your already defined admin with the hooking section. It is default enabled. To disable it
-just define ``RIVER_INJECT_MODEL_ADMIN`` to be ``False`` in the ``settings.py``.
+* To create one for a specific workflow object you should use the admin interface for the workflow object itself. One amazing feature of ``django-river`` is now that
+it creates a default admin interface with the hookings for your workflow model class. If you have already defined one, ``django-river`` enriches your already defined
+admin with the hooking section. It is default disabled. To enable it just define ``RIVER_INJECT_MODEL_ADMIN`` to be ``True`` in the ``settings.py``.
 
 
 **Note:** They can programmatically be created as well since they are model objects. If it is needed to be at workflow level, just don't provide the workflow object column. If it is needed

diff --git a/river/config.py b/river/config.py
@@ -18,7 +18,7 @@ def __getattr__(self, item):
             'USER_CLASS': settings.AUTH_USER_MODEL,
             'PERMISSION_CLASS': Permission,
             'GROUP_CLASS': Group,
-            'INJECT_MODEL_ADMIN': True
+            'INJECT_MODEL_ADMIN': False
         }
         if item in allowed_configurations.keys():
             default_value = allowed_configurations[item]