Skip to content

Commit

Permalink
Version 2.8 Changed the default for use_for_concrete
Browse files Browse the repository at this point in the history
  • Loading branch information
RamezIssac committed Sep 15, 2020
1 parent 8845a55 commit 735d10e
Show file tree
Hide file tree
Showing 4 changed files with 10 additions and 5 deletions.
3 changes: 3 additions & 0 deletions CHANGELOG.rst
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
----------
CHANGELOG
----------
v 2.8 (15 September 2020)
- Changed default of use_for_concrete

v 2.7 (16 August 2020)
- Assert Django 3.1 Support.
- Adds Django 3.1 to travis matrix.
Expand Down
8 changes: 5 additions & 3 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ Tabular_permissions possible configurations and their default::
'function':'tabular_permissions.helpers.dummy_permissions_exclude'
},
'auto_implement': True,
'use_for_concrete': True,
'use_for_concrete': False,
'custom_permission_translation': 'tabular_permissions.helpers.custom_permissions_translator',
'apps_customization_func': 'tabular_permissions.helpers.apps_customization_func',
'custom_permissions_customization_func': 'tabular_permissions.helpers.custom_permissions_customization_func',
Expand Down Expand Up @@ -90,9 +90,11 @@ auto_implement
See ``tabular_permissions.admin`` for information.

use_for_concrete
There is an inconsistency with proxy models permissions (Django ticket `11154 <https://code.djangoproject.com/ticket/11154>`_).
Default: False (new in version 2.8)

So in case you have proxy models and you created their permissions by hand (via this `gist <https://gist.github.com/magopian/7543724>`_ maybe), then turn off this option in order to correctly assign your newly created permissions.
There was an inconsistency with proxy models permissions (Django ticket `11154 <https://code.djangoproject.com/ticket/11154>`_) which got fixed in Django 2.1
In case you're on an django <2.1 and you have proxy models and you created their permissions by hand (via this `gist <https://gist.github.com/magopian/7543724>`_ maybe), then turn off this option in order to correctly assign your newly created permissions.
For django > 2.1, leave it as is you should be good.

custom_permission_translation
A dotted path function to translate the custom permission.
Expand Down
2 changes: 1 addition & 1 deletion tabular_permissions/__init__.py
Original file line number Diff line number Diff line change
@@ -1 +1 @@
__version__ = '2.7'
__version__ = '2.8'
2 changes: 1 addition & 1 deletion tabular_permissions/app_settings.py
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
'function':'tabular_permissions.helpers.dummy_permissions_exclude'
},
'auto_implement': True,
'use_for_concrete': True,
'use_for_concrete': False,
'custom_permission_translation': 'tabular_permissions.helpers.custom_permissions_translator',
'apps_customization_func': 'tabular_permissions.helpers.apps_customization_func',
'custom_permissions_customization_func': 'tabular_permissions.helpers.custom_permissions_customization_func',
Expand Down

0 comments on commit 735d10e

Please sign in to comment.