Can't Manage to add Custom Tonies

Software TeddyCloud
1

I connected to my docker machine via ssh and edited the json file via nano (/var/lib/docker/volumes/teddybox_config/_data# nano tonies.custom.json). now it looks like this:

[
{
“no”: “0”,
“model”: “900001”,
“audio_id”: ,
“hash”: [“c737f9d63752b8f1cf1fb78aa7dabd85b65fd3c4”],
“title”: “Wilma Wolkenkopf”,
“series”: “Wilma Wolkenkopf”,
“episodes”: “Custom Tag”,
“tracks”: ,
“release”: “0”,
“language”: “de-de”,
“category”: “custom”
},
{
“no”: “1”,
“model”: “123456”,
“audio_id”: [“369519776”],
“hash”: [“af9e61a9c1b12138fb060908d595742334b04515”],
“title”: “Custom Tonie Example Title”,
“series”: “Custom Tonies”,
“episodes”: “This is my custom tonie”,
“tracks”: [
“Title 1”,
“Title 2”,
“Title 3”,
“Title 4”,
“Title 5”,
“Title 6”,
“Title 7”,
“Title 8”,
“Title 9”,
“Title 10”
],
“release”: “0”,
“language”: “de-de”,
“category”: “custom”,
“pic”: “https://upload.wikimedia.org/wikipedia/en/6/6b/Hello_Web_Series_(Wordmark)_Logo.png”
}
]

One is my try of creating a custom entry and the other is the one from the wiki. Yet neither after the “reload” button in the settings nor after a full container restart the custom tonies are accessible. What am I missing? The logs also show no errors.

2

Did You use a json validator to verify the json?

Besides some formattings things caused by not using the code makro here in the forum it looks okish for me.

3

And what are you expecting?

If you click on edit on a tonie and search for the title of your entry… is the entry found?

4

the file is considered valid by the validator and I also find no error in the logs after the entry of reading the file. When i click a custom tonie and enter either the title or the model in the search field no results show up. When i directly enter the model into the model field and it will also not show the information.

There is no option to show the raw content that has been processed from the web-ui for debugging, correct?

5

You could inspect the browsers dev mode network tab if there is such thing

6

Problem solved :slight_smile: There were some mapping issues caused by my docker machines SMB settings. With these settings fixed or the files directly edited via the machines terminal it works as inteded.

1 Like