CSS selectors throwing an error

Hi @bigduke6

Thanks for reporting this!

We’ve just released version 1.2 of the plugin, which includes a fix for the issue you encountered.

Please update to the latest version, and the error should be resolved. Let us know if you run into any further issues—we’re here to help!

Thanks for the update! That error message – “Server Error – ElevenLabs is experiencing internal issues” – isn’t something we’ve been able to reproduce on our side, but it could be a temporary issue with ElevenLabs’ API, which our plugin connects to for audio generation.

Another possible cause is that the maximum number of saved voices has been reached. The free plan at ElevenLabs allows for up to 3 saved voices. If you’ve already selected 3 voices, trying to add another may trigger this error.

We’re actively working on improvements. Later today, we’ll push out a new version that includes:

• A dedicated page for Stats and Saved Voices, where you can view and reset your saved voices
• More descriptive and user-friendly error messages
• Better debugging tools

As for the current debug logs:
When debug mode is enabled via advanced.php, logs are shown in your browser’s JavaScript console. Here’s how to view them:

1. Enable debug mode in the plugin settings.
2. Open a page on your site using the Text-to-Speech feature.
3. Open your browser’s developer tools:
   • Chrome/Edge: Press F12 or right-click > Inspect
   • Firefox: Press F12 or right-click > Inspect Element
   • Safari: Enable dev tools in settings, then press Cmd+Opt+I
4. Go to the Console tab – you’ll see logs prefixed with Mementor TTS: including details like:
   • API requests/responses
   • Audio player events
   • Error messages
   • Active settings

You can also enable debug mode temporarily by adding ?mementor_tts_debug=1 to any URL on your site.

For even deeper insight, you can enable WordPress debugging by adding the following to your wp-config.php:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );

This will write full logs to wp-content/debug.log.

If you spot any specific error there, feel free to send it to us at [email protected] – it will help us diagnose and fix the issue faster.

Thanks again for reporting this, and we’ll keep you posted once the update is live!