409 Error when attempting to edit Profile Highlight Color
See original GitHub issueIf you attempt to edit the Highlight Color on your Profile, you get an error:
Web error: 409 (Conflict) on PATCH of <https://khoward5.dev.inrupt.net/profile/card>
To Replicate
- Log into a dev.inrupt.net Pod.
- “Edit your profile”.
- Edit the Highlight Color.
Expected Behaviour
- The Highlight color is updated to the selected color.
Actual Behaviour
- Error
Web error: 409 (Conflict) on PATCH of <https://khoward5.dev.inrupt.net/profile/card>is displayed.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
How To Fix the “409 Conflict” Error (5 Methods) - Kinsta
1. Check the Requested URL ... As we mentioned earlier, the “409 Conflict” error can arise from incorrect information in a PUT request....
Read more >HTTP 409 Conflict errors when updating profiles
Our education domain is receiving intermittent HTTP 409 Conflict errors when updating user profiles, and the profiles themselves are not updated.
Read more >Error status 409 while updating profile - Stack Overflow
After reading this I saw that 409 response status error was happening because contact/profile entry was being updated from two sources, so the...
Read more >Can't change border color in "Format Cells" window in
In my business I routinely have to change the type and color of cell borders ... I always get a "Font size must...
Read more >Error code: 409 - Google Classroom Community
Error code: 409. I go to classroom and try to download a photo one of my friends posted and I get the 409...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

The bug is in the logic of handling of the logic of a field in the form system. Why would it be there? The line may have been put there in the past when the system used PUT to save back the edited data. In that case, one can imagine it working so that is the data was save, that all values with defaults would be set to those defaults. (Which may or nor have been a good idea!). But in fact the code (now) uses PATCH and sends the diffs using update(), and when you do that it is important that the local quad store is in sync with the web.
That’s basically what the form fields do. They first read the file, and set the UI to the set value if there is one, or otherwise the default in the form, if any. If the user sets anything, then the update function deleted the existing to be deleted statements (ds) before it adds in the new ones (is). ((The tristate checkbox is more complicated in that user can opt for saying true or false or not saying anything.))