The view is displayed, no error message.
The view is actually changed accordingly, but the user get an error message :
UI : Trouble processing request. Try again after refreshing the page.
Web console : code: 302, message: "Updating item from "directus_collection_presets" collection was denied"
The user is not an admin.
Hey @alrick! Did you change any of the default permissions settings for this user role? Could you check if the role has permissions to update / create in directus_collection_presets?
hey @rijkvanzanten
Nope, the user is brand new, here is the permissions of his role :

I have to add that I may have changed the "user" (set to null) of my collection presets (admin) in the database in order to create global default views.
Is there a way to proper reset the collection presets in order to test further what's triggering the error message ?
I see, the app might be trying to update the one that doesn't have a user attached to it which could cause this issue 馃 Although if update is set to full permissions that shouldn't be the case either.
You can safely delete the rows in collection_presets if you want to debug individual rows
Ok thanks for the tip, I'll try to debug next week and keep you updated.
So, after further testing it seems that the user can't determine if the preset belongs to him or not.
Here is what I've done :
Another note : if I change the collection presets to "All" for the user's role, I can't set it back to "Mine" via the app, the only options are "None" or "All".
Here are the error messages, I hope it helps :
# web console
code: 302, message: "Updating item from "directus_collection_presets" collection was denied"
# api/logs
api[diatheque].ERROR: Directus\Permissions\Exception\ForbiddenCollectionUpdateException: Updating item from "directus_collection_presets" collection was denied in /var/www/api/src/core/Directus/Permissions/Acl.php:1072
Ah! We had a very similar problem with directus_users.. https://github.com/directus/api/pull/828
@bjgajjar could you do the same fix for directus_collection_presets and any other collection that is related to users?
@alrick @rijkvanzanten
I'll fix the issue and send the PR ASAP!
@alrick @rijkvanzanten I and @bjgajjar both are not able to reproduce this issue at our end!
@alrick can you update the API & APP to the latest version and check if the issue persists? Also, don't forget to run the database update script after updating codebase.
@theharshin just to confirm, you tried the
I have to add that I may have changed the "user" (set to null) of my collection presets (admin) in the database in order to create global default views.
part as well? That might be the reason it's causing problems right now
@theharshin just to confirm, you tried the
I have to add that I may have changed the "user" (set to null) of my collection presets (admin) in the database in order to create global default views.
part as well? That might be the reason it's causing problems right now
Yes, I've changed the ID in user column from admin to another user so the user can directly see the preset set by Admin. The user was able to change the preset later.
Thanks for your tests @theharshin
Did you try with the user set to null too ?
I'll update the app next monday and test everything again.
Just a follow-up that I'll not update everything before the problem with the files is fixed as this is a deal-breaker for my clients.
I'll update and test everything as soon as this is fixed, next update according to a conversation on your Slack.
This seems indeed fixed with the last version.
Most helpful comment
So, after further testing it seems that the user can't determine if the preset belongs to him or not.
Here is what I've done :
Another note : if I change the collection presets to "All" for the user's role, I can't set it back to "Mine" via the app, the only options are "None" or "All".
Here are the error messages, I hope it helps :