Worked just fine
Maybe the old document didn't got the new permissions some how
Any ideas on what I can do?
For the old one? Is this a self-hosted?
Yes self hosted, 1.3.8, DigitalOcean
You can try connecting to your MariaDB using this gist https://gist.github.com/byawitz/885510a4d9789e97424337e9472276d7
Then you can bulk edit the permission of the collection inside the meta
and collection
tables
I'll see what I can do :) Thanks
Looking in the database all the permissions seem to be correct. I've not changed anything yet.
That one empty array should be empty
I removed the permissions and then added them back and am getting this.
I can fetch the document I'm looking to update and see it has the correct permissions. I've put both my get and updates here, maybe I'm just blind and not seeing something?
Did you upgrade to 1.3.8?
Do you have relationships on the collection?
Yes and yes
I guess the new record that was created has no actual relationships made, is the issue authorization on the relationship?
Possibly. Does the user have update access to the related document?
no only read
That's probably it then
:( I knew it would be something easy I just overlooked.
Yep, that fixed it. Thank you very much!
[SOLVED] Document Authorization
We're working on a ton of updates to relationships. One of which is allowing updating a document that has a relationship as long as you're not updating the related document
Sounds awesome! :) Excited for the upcoming updates.
Was out Already got solved by Steven as usual 😉
Thanks for all your help though! I appreciate the assistance :)
Recommended threads
- Invalid document structure: missing requ...
I just pick up my code that's working a week ago, and now I got this error: ``` code: 400, type: 'document_invalid_structure', response: { message: 'Inv...
- custom domain with CloudFlare
Hi all, it seems that CloudFlare has blocked cross-domain CNAME link which made my app hostname which is in CloudFlare, unable to create a CNAME pointing to clo...
- Type Mismatch in AppwriteException
There is a discrepancy in the TypeScript type definitions for AppwriteException. The response property is defined as a string in the type definitions, but in pr...