Wagtail:How to have multiple types of admin
up vote
1
down vote
favorite
I am making a blogging website using wagtail so we have multiple writers so I need that no one can see drafts of other users and only the superadmin can post the blogs but I can't find that setting.
django wagtail
add a comment |
up vote
1
down vote
favorite
I am making a blogging website using wagtail so we have multiple writers so I need that no one can see drafts of other users and only the superadmin can post the blogs but I can't find that setting.
django wagtail
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am making a blogging website using wagtail so we have multiple writers so I need that no one can see drafts of other users and only the superadmin can post the blogs but I can't find that setting.
django wagtail
I am making a blogging website using wagtail so we have multiple writers so I need that no one can see drafts of other users and only the superadmin can post the blogs but I can't find that setting.
django wagtail
django wagtail
asked Nov 11 at 7:20
gaurav jain
61
61
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
Previewing and submitting pages for moderation
The Save/Preview/Submit for moderation menu is always present at the bottom of the page edit/creation screen. The menu allows you to perform the following actions, dependent on whether you are an editor, moderator [...]
Source: http://docs.wagtail.io/en/v2.3/editor_manual/new_pages/previewing_and_submitting_for_moderation.html
Editors (you call them writers) can submit for moderation. Moderators can publish. So this part of your requirements is built in. My advice is to create users for each type and play around to get a feeling for this workflow.
There is no (out of the box) way to show pages to their creators only. However, you can give groups access to parts of the page tree:
- Go to a page in the admin.
- Top right, click the Privacy setting. Public is the default.
- Change to 'Private, accessible to users in specific groups'.
- Choose a group.
Now only users in this group can edit this section. So this page and all it's child pages.
Default there are two groups: Editors and Moderators. You can create new groups via /admin/groups/new/
. If you give each user it's own group, you have what you want. Their pages will live in their own part of the page tree though.
Note that when you create a group it is also possible to limit permissions per content type. So you can make a group of users responsible for content of a specific type.
Wagtail users, groups, permissions, workflows and privacy settings makes it possible to configure permissions in a fine grained way. This will be sufficient in most cases.
When you have a project requirement that is more demanding, you can always add some extra logic to meet your requirement. Python/Django/Wagtail is a flexible software stack. But before going there, I would advice you to see if the standard settings are sufficient. If not, you should describe your requirements in more detail.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Previewing and submitting pages for moderation
The Save/Preview/Submit for moderation menu is always present at the bottom of the page edit/creation screen. The menu allows you to perform the following actions, dependent on whether you are an editor, moderator [...]
Source: http://docs.wagtail.io/en/v2.3/editor_manual/new_pages/previewing_and_submitting_for_moderation.html
Editors (you call them writers) can submit for moderation. Moderators can publish. So this part of your requirements is built in. My advice is to create users for each type and play around to get a feeling for this workflow.
There is no (out of the box) way to show pages to their creators only. However, you can give groups access to parts of the page tree:
- Go to a page in the admin.
- Top right, click the Privacy setting. Public is the default.
- Change to 'Private, accessible to users in specific groups'.
- Choose a group.
Now only users in this group can edit this section. So this page and all it's child pages.
Default there are two groups: Editors and Moderators. You can create new groups via /admin/groups/new/
. If you give each user it's own group, you have what you want. Their pages will live in their own part of the page tree though.
Note that when you create a group it is also possible to limit permissions per content type. So you can make a group of users responsible for content of a specific type.
Wagtail users, groups, permissions, workflows and privacy settings makes it possible to configure permissions in a fine grained way. This will be sufficient in most cases.
When you have a project requirement that is more demanding, you can always add some extra logic to meet your requirement. Python/Django/Wagtail is a flexible software stack. But before going there, I would advice you to see if the standard settings are sufficient. If not, you should describe your requirements in more detail.
add a comment |
up vote
1
down vote
Previewing and submitting pages for moderation
The Save/Preview/Submit for moderation menu is always present at the bottom of the page edit/creation screen. The menu allows you to perform the following actions, dependent on whether you are an editor, moderator [...]
Source: http://docs.wagtail.io/en/v2.3/editor_manual/new_pages/previewing_and_submitting_for_moderation.html
Editors (you call them writers) can submit for moderation. Moderators can publish. So this part of your requirements is built in. My advice is to create users for each type and play around to get a feeling for this workflow.
There is no (out of the box) way to show pages to their creators only. However, you can give groups access to parts of the page tree:
- Go to a page in the admin.
- Top right, click the Privacy setting. Public is the default.
- Change to 'Private, accessible to users in specific groups'.
- Choose a group.
Now only users in this group can edit this section. So this page and all it's child pages.
Default there are two groups: Editors and Moderators. You can create new groups via /admin/groups/new/
. If you give each user it's own group, you have what you want. Their pages will live in their own part of the page tree though.
Note that when you create a group it is also possible to limit permissions per content type. So you can make a group of users responsible for content of a specific type.
Wagtail users, groups, permissions, workflows and privacy settings makes it possible to configure permissions in a fine grained way. This will be sufficient in most cases.
When you have a project requirement that is more demanding, you can always add some extra logic to meet your requirement. Python/Django/Wagtail is a flexible software stack. But before going there, I would advice you to see if the standard settings are sufficient. If not, you should describe your requirements in more detail.
add a comment |
up vote
1
down vote
up vote
1
down vote
Previewing and submitting pages for moderation
The Save/Preview/Submit for moderation menu is always present at the bottom of the page edit/creation screen. The menu allows you to perform the following actions, dependent on whether you are an editor, moderator [...]
Source: http://docs.wagtail.io/en/v2.3/editor_manual/new_pages/previewing_and_submitting_for_moderation.html
Editors (you call them writers) can submit for moderation. Moderators can publish. So this part of your requirements is built in. My advice is to create users for each type and play around to get a feeling for this workflow.
There is no (out of the box) way to show pages to their creators only. However, you can give groups access to parts of the page tree:
- Go to a page in the admin.
- Top right, click the Privacy setting. Public is the default.
- Change to 'Private, accessible to users in specific groups'.
- Choose a group.
Now only users in this group can edit this section. So this page and all it's child pages.
Default there are two groups: Editors and Moderators. You can create new groups via /admin/groups/new/
. If you give each user it's own group, you have what you want. Their pages will live in their own part of the page tree though.
Note that when you create a group it is also possible to limit permissions per content type. So you can make a group of users responsible for content of a specific type.
Wagtail users, groups, permissions, workflows and privacy settings makes it possible to configure permissions in a fine grained way. This will be sufficient in most cases.
When you have a project requirement that is more demanding, you can always add some extra logic to meet your requirement. Python/Django/Wagtail is a flexible software stack. But before going there, I would advice you to see if the standard settings are sufficient. If not, you should describe your requirements in more detail.
Previewing and submitting pages for moderation
The Save/Preview/Submit for moderation menu is always present at the bottom of the page edit/creation screen. The menu allows you to perform the following actions, dependent on whether you are an editor, moderator [...]
Source: http://docs.wagtail.io/en/v2.3/editor_manual/new_pages/previewing_and_submitting_for_moderation.html
Editors (you call them writers) can submit for moderation. Moderators can publish. So this part of your requirements is built in. My advice is to create users for each type and play around to get a feeling for this workflow.
There is no (out of the box) way to show pages to their creators only. However, you can give groups access to parts of the page tree:
- Go to a page in the admin.
- Top right, click the Privacy setting. Public is the default.
- Change to 'Private, accessible to users in specific groups'.
- Choose a group.
Now only users in this group can edit this section. So this page and all it's child pages.
Default there are two groups: Editors and Moderators. You can create new groups via /admin/groups/new/
. If you give each user it's own group, you have what you want. Their pages will live in their own part of the page tree though.
Note that when you create a group it is also possible to limit permissions per content type. So you can make a group of users responsible for content of a specific type.
Wagtail users, groups, permissions, workflows and privacy settings makes it possible to configure permissions in a fine grained way. This will be sufficient in most cases.
When you have a project requirement that is more demanding, you can always add some extra logic to meet your requirement. Python/Django/Wagtail is a flexible software stack. But before going there, I would advice you to see if the standard settings are sufficient. If not, you should describe your requirements in more detail.
answered Nov 11 at 10:36
allcaps
7,3242142
7,3242142
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53246653%2fwagtailhow-to-have-multiple-types-of-admin%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown