Editing Attributions in Avatar admin panel breaks the whole avatar system #4704
Replies: 2 comments 1 reply
-
Local install normally won't connect to admin pages due to being unable to connect to the reticulum server. I would have to look into the error code for both problems you have stated because it seems that your reticulum server is having issues accepting the request on your AWS setup. Do you remember any modifications to the existing code base? |
Beta Was this translation helpful? Give feedback.
-
Ok, I have a partial fix, courtesy of @netpro2k (if I knew React, perhaps I could have figured this out):
to
This "mostly works", enough for me to fix the issues with my avatar. Now when I go look at the "attribute" field I edited to be The remaining problem is that if the field is not valid JSON you can't edit; your only option is to paste valid json in. So a "complete" fix would be to check if the field is valid; if it isn't valid, show an error and disallow saving. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This is related to #3412
If I go to the avatars admin page, and hit edit, I will see something like this:

Notice that attributions is showing as "[Object object]" which looks like how JS would print an array of one objects in the console.
I had entered "readyplayerme" when I uploaded the object, and back in the object list, Attributions shows as {"creator":"readyplayerme"}
I I edit that field and enter "{"creator":"readyplayerme"}" in text, things break. I no longer see any avatars in the Avatar selection panel for the server, and if I go and look at the server logs I see:
It doesn't matter what I enter, it's impossible to change that field back to anything that isn't borking the server.
I suspect what is happening is that the things being received from the server is JSON, which is what is printed in the listing. But, the edit panel is operating on the Object created from the JSON; when a string is entered, and it's converted BACK to JSON, it's invalid (since it's an escaped string, not a valid JSON).
I would try and fix this but I don't really know React (!) (so I don't understand how the admin code is getting the data from the server, or how it's connected to the React panels), and when I run the client locally, any time I try to got to the admin panel is just shows me the homepage.
Beta Was this translation helpful? Give feedback.
All reactions