We are experiencing a strange issue with djangocms-blog (Fabians fork for django cms 4.1): When a user who is not admin tries to save new post, the runserver log (in case of a test on the developing machine) shows a 200 OK in the log, but the new post dialogue stays open and the article is actually not saved. There’s no error message.
If on the other hand the user is admin, the post is being saved, so it seems to be a privilege problem. But all blog related privileges have been activated for the editors group, it seems there was one new blog after the update to cms 4.1, and normal pages can be created and edited by a user in the editor group who is not admin.
Steps to reproduce
I’m not sure if it can be reproduced, but what we do:
Create an editors groups with all permissions of the blog app and all other necessary permissions for creating articles.
Open the menu item “Create Article…” and fill out at least the Title
Dialogue should close, article should be saved, and become visible in the list of articles, in admin and in the front end.
Actual behaviour
Dialogue stays open, article apparently isn’t saved, at least it doesn’t show up, neither in the list in the admin section or in the front end. In the log the POST request is being listed with a 200 OK response, though, no error message is shown.
Additional information
On 1st of October a colleague has successfully saved an article with the same djangocms-blog version. So I’m not sure if the issue is really caused by the blog app, maybe something else triggers it.
Users with admin privileges can save blog articles without problem.
Create an editors group and editor user (staff, but not superuser) who is in this group (or just the user) and give all available privileges to the group (or user)
Log in as editor and try to create a blog post. Blog –> New article Add at least a title and click on “Save”.
The dialogue stays open, the blog post is not saved..
Description
We are experiencing a strange issue with djangocms-blog (Fabians fork for django cms 4.1): When a user who is not admin tries to save new post, the runserver log (in case of a test on the developing machine) shows a 200 OK in the log, but the new post dialogue stays open and the article is actually not saved. There’s no error message.
If on the other hand the user is admin, the post is being saved, so it seems to be a privilege problem. But all blog related privileges have been activated for the editors group, it seems there was one new blog after the update to cms 4.1, and normal pages can be created and edited by a user in the editor group who is not admin.
Steps to reproduce
I’m not sure if it can be reproduced, but what we do:
Versions
Python 3.11 Django 5.1.2 django-cms==4.1.3 djangocms-versioning==2.0.2 djangocms-blog @ git+https://github.com/fsbraun/djangocms-blog.git@4efe3ba11ca9f6ff8943a8482359a9e2b2a17288
Expected behaviour
Dialogue should close, article should be saved, and become visible in the list of articles, in admin and in the front end.
Actual behaviour
Dialogue stays open, article apparently isn’t saved, at least it doesn’t show up, neither in the list in the admin section or in the front end. In the log the POST request is being listed with a 200 OK response, though, no error message is shown.
Additional information
On 1st of October a colleague has successfully saved an article with the same djangocms-blog version. So I’m not sure if the issue is really caused by the blog app, maybe something else triggers it.
Users with admin privileges can save blog articles without problem.