Unable to Assign Tags and Custom Properties to TTS Voices

[Adrian-Serna]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Cloud or Self Hosted

Cloud

Steps to reproduce

1. Create a new TTS voice using the web interface or the API.
2. Attempt to add tags during the creation process or update tags afterward.
3. Check the response or resulting model - the tags field remains empty.
4. Attempt to assign custom properties via the API by including them in the request body.
5. Observe that the properties are not applied or saved.

✔️ Expected Behavior

Tags and custom properties should be saved and appear correctly in the response after creating or updating a TTS voice, both through the web interface and via API requests.

❌ Actual Behavior

Tags and custom properties are not being saved or reflected in the model after the creation or update attempts.

[Adrian-Serna]

Update on Issue: Tags and Custom Properties Not Saving

After some additional investigation and communication with support, I wanted to provide an update on the current status of this issue.

1. Tags Issue: It turns out that when adding tags in the web interface, pressing enter after typing each tag is required for them to be saved. I must admit, I had a bit of a "facepalm" moment when I realized this step was missing. Now that I know, it's working perfectly! Thanks for pointing out what was probably obvious to everyone else.

2. API Tags Issue: I have managed to successfully add tags through the API, but only one tag at a time by voice. The suggested curl command in the documentation seems to have an incorrect format for tags. When attempting to add multiple tags, the following format was given:

   --form 'tags=["Tag1", "Tag2"]'

   However, this format does not work as expected:

I have been able to format it to obtain a tag correctly with:

 --form 'tags=Tag1'

But I have not been able to add more than one tag as it can be done in the web interface, by pressing enter after each one, of course!
3. Custom Properties: Custom properties still do not seem to be assigned through the API. Despite including them in the request body, these properties are not visible when retrieving the model list with "List Models".

I appreciate the support team's responsiveness and would like to share this information in case others are experiencing similar issues. Any additional guidance on how to properly assign multiple tags or custom properties would be greatly appreciated.