Hello, I have an issue in the "my voices" section. Who can help?

[polar meteor]

AI-generated Answer for pixberlin

I'm here to assist you! However, I need more specific details about the issue you're facing in the "my voices" section. Could you please describe the problem in more detail? This will help me provide the most accurate and helpful information.

[umbral bobcat]

I have no access to just ONE of my two voices. Clearing Cache didn't make a difference. I got a few page errors when I tried to get access to one of my 2 slots under "my voices".

[polar meteor]

AI-generated Answer for pixberlin

I'm sorry to hear that you're having trouble accessing one of your voices. The information provided suggests that unless you explicitly share a voice with another account or to the Voice Library, the voices in your VoiceLab are only accessible to you.

If you're encountering client-side errors, these typically point to issues within your browser or the cached data and cookies related to the website. It's recommended to clear your browser cache. If you're using browser-based translation tools like Google Translate, these can sometimes trigger these errors.

If you encounter a message regarding client-side errors after using the “Generate” feature in Speech Synthesis, your audio should have been successfully generated and will be available in your History.

If you see a client-side error message and you are not using translation in your browser, you can try to resolve the issue by clicking “Try again”. If the issue persists, it can usually be resolved by clearing the cache for the website by pressing CTRL + F5.

If none of these solutions work, please contact Support by submitting a request here.

[umbral bobcat]

This is the first of 3 or 4 error messages: Looks like this: The Content Security Policy (CSP) prevents the evaluation of arbitrary strings as JavaScript to make it more difficult for an attacker to inject unathorized code on your site.
To solve this issue, avoid using eval(), new Function(), setTimeout([string], ...) and setInterval([string], ...) for evaluating strings.
If you absolutely must: you can enable string evaluation by adding unsafe-eval as an allowed source in a script-src directive.

[polar meteor]

AI-generated Answer for pixberlin

The error message you're seeing is related to a security feature in modern web browsers called Content Security Policy (CSP). CSP is designed to prevent certain types of attacks, such as Cross Site Scripting (XSS), by not allowing the execution of unsafe JavaScript code. The methods mentioned in the error message (eval(), new Function(), setTimeout([string], ...) and setInterval([string], ...)) are considered unsafe because they can execute arbitrary JavaScript code.

However, the error message you're seeing is likely not the cause of your issue with accessing your voices. It's more likely that there's an issue with the website or the server it's communicating with.

Unfortunately, the information provided in the knowledge base does not include a specific solution for this issue. It would be best to contact the support team directly for further assistance. They should be able to help you troubleshoot the issue and provide a solution. You can submit a request to the support team here.

[umbral bobcat]

here's more: 1 directive
Source location Directive Status
script-src blocked
Learn more: Content Security Policy - Eval
Incorrect use of <label for=FORM_ELEMENT>
The label's for attribute doesn't match any element id. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.
To fix this issue, make sure the label's for attribute references the correct id of a form field.