django-ya-model-publisher 0.6.0

Features

• Django CMS page support.

• Add request/reject buttons in Django CMS toolbar.

• Django CMS placeholders support.

• Hvad/Parler support.

• Restrict user access to publish functions with user permissions.

base info

We have these three user types:

• A user with only a few rights (we call it ‘reporter’)

• A user with more rights (We call it ‘editor’)

• The superuser with all rights

The user case is following:

• ‘reporter’:

  • can only change draft content

  • can’t change public content

  • can’t delete publisher model entries or CMS pages.

  • can send a (un-)publish request to the ‘editor’ with a text node.

• ‘editor’:

  • can response open publishing request from ‘reporter’.

  • can change drafts and public content, but only if there is no pending request.

  • can delete publisher model entries or CMS pages.

  • can’t delete/manipulate publisher state model entries.

permissions

Permissions for ‘reporter’ who can only create (un-)publish requests:

...
[ ] cms.publish_page
...
[*] cms.add_page
[*] cms.change_page
[ ] cms.delete_page
...
[ ] publisher.add_publisherstatemodel
[*] publisher.change_publisherstatemodel
[ ] publisher.delete_publisherstatemodel
...
[ ] <app_name>.can_publish_<model_name>
...
[*] <app_name>.add_<model_name>
[*] <app_name>.change_<model_name>
[ ] <app_name>.delete_<model_name>
...

Permissions for ‘editor’ who can accept/reject (un-)publish requests:

...
[*] cms.publish_page
...
[*] cms.add_page
[*] cms.change_page
[*] cms.delete_page
...
[ ] publisher.add_publisherstatemodel
[*] publisher.change_publisherstatemodel
[ ] publisher.delete_publisherstatemodel
...
[*] <app_name>.can_publish_<model_name>
...
[*] <app_name>.add_<model_name>
[*] <app_name>.change_<model_name>
[*] <app_name>.delete_<model_name>
...

Important: To prevent a privilege escalation, both users must not have access to these models:

• django.contrib.auth.models.Permission

• django.contrib.auth.models.Group

• cms.models.PagePermission

Test users:

See user permission tests in:

• publisher_tests.test_basics.PermissionTestCase

Django compatibility

Note: See travis/tox config files for current test matrix

run tests

run tests via py.test with current python/environment:

$ make test
or
$ ./setup.py test
or
$ python tests/manage.py test myapp

run test via tox e.g.:

$ make tox
or
$ ./setup.py tox
or
$ tox

$ ./run_test_project_dev_server.sh

$ ./publisher_test_project/manage.py run_test_project_dev_server

$ ./run_test_project_dev_server.sh --help
...
usage: manage.py run_test_project_dev_server [-h] [--version] [-v {0,1,2,3}]
                                             [--settings SETTINGS]
                                             [--pythonpath PYTHONPATH]
                                             [--traceback] [--no-color]
                                             [--ipv6] [--nothreading]
                                             [--noreload] [--nostatic]
                                             [--insecure]
                                             [addrport]
...

$ ./publisher_test_project/manage.py create_test_data --fresh

$ rm publisher_test_project/publisher_test_database.sqlite3

Backwards-incompatible changes

v0.6.0

The permission names changed! Please update your django user permissions, too.

These permissions are removed:

• direct_publisher

• ask_publisher_request

• reply_publisher_request

Please read the information above.

history

• v0.6.0 - 27.12.2017 - compare v0.5.1…v0.6.0

  • refactor permissions and publisher workflow

  • NEW: publisher.views.PublisherCmsViewMixin

  • NEW: publisher.admin.VisibilityMixin

  • bugfix django v1.11 compatibility

  • Expand tests with publisher_test_project.publisher_list_app

• v0.5.1 - 20.12.2017 - compare v0.5.0…v0.5.1

  • fix python package (add missing parts)

  • change travis/tox/pytest configuration

  • minor code update

• v0.5.0 - 19.12.2017 - compare v0.4.1…v0.5.0

  • Skip official support for python v2.7 and v3.4 (remove from text matrix)

  • Implement “request/reject/accept publishing” workflow with a shot messages and logging

  • Add “request/reject/accept publishing” buttons to Django CMS toolbar for cms pages.

• v0.4.1 - 14.11.2017 - compare v0.4.0.dev1…v0.4.1

  • Refactor test run setup

  • bugfix project name

• v0.4.0.dev1 - 14.11.2017 - compare v0.3.1…v0.4.0.dev1

  • Just create the fork and apply all pull requests from andersinno/django-model-publisher-ai/pull/14

links

donation

• paypal.me/JensDiemer

• Flattr This!

• Send Bitcoins to 1823RZ5Md1Q2X5aSXRC5LRPcYdveCiVX6F