-
-
Notifications
You must be signed in to change notification settings - Fork 810
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] Can't delete a record from dashboard listing #5009
Labels
Milestone
Comments
Not really helpful mate. I can only presume that this is for a non-root user, etc. Can you update this with configuration details. Relevant parts of the |
Standard roles, working from Relevant part of
|
Right! Got you now, you're correct this is nothing to do with Escalating and ping @rarila |
GwendolenLynch
added a commit
that referenced
this issue
Apr 6, 2016
Fix for #5009 – Can't delete a record from dashboard listing
Fixed in #5131 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When i go to dashaboard and try to delete something
![2016-03-12 11-17-49](https://cloud.githubusercontent.com/assets/2145313/13721062/5d0769e6-e844-11e5-9918-59a67217cbde.png)
it gives me an error
![2016-03-12 11-11-01](https://cloud.githubusercontent.com/assets/2145313/13721065/6143bc8a-e844-11e5-9a43-c0feef4df71f.png)
in compressed it's here (at first i changed
![2016-03-12 11-11-33](https://cloud.githubusercontent.com/assets/2145313/13721067/7d734cb8-e844-11e5-8085-3550b1ab3358.png)
.parents()
from original to.closest()
but it doesn't affect)that leads me here:
![2016-03-12 11-15-49](https://cloud.githubusercontent.com/assets/2145313/13721069/91809e86-e844-11e5-9baa-e54bbcd6056f.png)
But there's no
![2016-03-12 11-16-11](https://cloud.githubusercontent.com/assets/2145313/13721070/96616674-e844-11e5-8794-e01b12956c63.png)
id
attribute in<tr/>
.Probably because of
![2016-03-12 11-19-59](https://cloud.githubusercontent.com/assets/2145313/13721072/9edeec36-e844-11e5-931c-ef97d36f73ae.png)
For me it looks like a bug.
The text was updated successfully, but these errors were encountered: