Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG Hierarchie / Baum verändern kaputt #314

Closed
timbuktutimbuktu opened this issue Oct 25, 2023 · 2 comments · Fixed by #316
Closed

BUG Hierarchie / Baum verändern kaputt #314

timbuktutimbuktu opened this issue Oct 25, 2023 · 2 comments · Fixed by #316
Assignees
Labels
bug Something isn't working

Comments

@timbuktutimbuktu
Copy link
Collaborator

BUG
ich kann die Hierarchie von Tasks nicht mehr verändern.
Selbst wenn ich als admin angemeldet bin, führt ein verschieben per drag&drop nur zu einem freundlich gelben blinken.
Es wird erst "as sibling" "as child" und die violette graphische Vorhersage angezeigt, aber wenn ich den mouse button loslasse, ist die task nicht verschoben, sondern blinkt gelb.
Help! 🚁

@timbuktutimbuktu timbuktutimbuktu added the bug Something isn't working label Oct 25, 2023
@kleins05
Copy link
Collaborator

Cannot be reproduced on local installation. Cannot test online because I do not have a user and don't know how to get one (I missed out on some information here, I think)

@fblampe
Copy link
Collaborator

fblampe commented Oct 25, 2023

I could reproduce it on the production and testing instances.

As @cafischer suggested, this might be related to errors logged in the browser console regarding our content security policy. I'm not so sure about that though because those errors also occur when just loading any admin page through a GET request.
There are no errors in the app log and the nginx logs only show the same 403 Forbidden status (which does look like a CSP issue..) as the browser debug tools network tab:

"POST /admin/cpmonitor/task/?city__id__exact=11 HTTP/1.1" 403

I'm not really sure what to make of this. Maybe the easiest way to find the commit that caused this is to use git bisect, provided the bug is reproducible in a local setup (probably running in Docker).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
4 participants