Features Pricing
Blog Documentation Changelog API Reference
Sign In
Get Started

Player does not appear on the front-end

4 min read

The audio generated fine in the admin, but when you view the post on your site, there is no audio player. This page walks through the common causes.

Quick checklist

Before digging in:

  1. Reload the page with Ctrl+Shift+R (hard-refresh bypasses cache)
  2. Check that the post has audio in the admin TTS column
  3. Check that you are not logged out (some themes hide admin-only elements)

Cause 1: The post type is not enabled

Symptom: Audio exists in the admin, but no player on the front-end. Works on some post types but not others.

Fix:

  1. Go to Text to Speech → Content.
  2. Check that the current post's type is enabled (Posts, Pages, Products, etc.).
  3. Save.
  4. Reload the front-end post.

Cause 2: Theme conflict

Symptom: The player appears on some themes but not yours, or appears but is invisible or broken.

Common reasons:

  • Your theme strips out the the_content filter where TTSWP injects the player
  • Your theme uses a custom template that bypasses WordPress's default content hooks
  • CSS from your theme hides the player (display: none somewhere)

Fix:

  1. Temporarily switch to a default WordPress theme (Twenty Twenty-Four).
  2. Reload the post.
  3. If the player appears on the default theme, the issue is your theme.

Workarounds:

  • Use the [mementor-tts] shortcode inside the post to force placement
  • Use the [tts_player id="123"] shortcode in a custom theme template
  • Add custom CSS to make the player visible if it is being hidden

Cause 3: Placement is set to a view that is not showing

Symptom: Player appears on some pages but not others.

Example: If placement is Before excerpt, the player only shows on archive and blog-list pages, not on single posts.

Fix:

  1. Go to Text to Speech → Player.
  2. Check the Placement dropdown.
  3. Switch to After title or After content for the most universal placement.
  4. Save.

Cause 4: Cache is serving an old version

Symptom: Player appears on a fresh incognito window but not on your regular browser.

Fix:

  1. Clear your browser cache (Ctrl+Shift+Delete).
  2. If you use a caching plugin (WP Rocket, LiteSpeed, etc.), clear its cache.
  3. If you use a CDN (Cloudflare, etc.), purge its cache.

See Caching plugins.

Cause 5: JavaScript blocked

Symptom: The player HTML is there (view source), but it looks broken or static.

Why: The player uses JavaScript for controls. If JS is blocked, the player shows as unstyled HTML.

Fix:

  • Check your browser console for JS errors
  • Disable adblockers or content blockers on your site
  • Check that no other plugin is dequeuing mementor-tts-public.js

Cause 6: Weglot or WPML routing issue

Symptom: Player works on the original language but not on translated pages (or vice versa).

Fix: Make sure the Weglot or WPML integration toggle is on. Go to Text to Speech → Overview → Quick Settings. See WPML integration and Weglot integration.

Cause 7: AMP version of the page

Symptom: Player shows on the regular version but not on AMP.

Why: AMP has strict rules about JavaScript. The TTSWP player does not run inside AMP pages.

Workaround: Link visitors to the non-AMP version, or use a different approach for audio on AMP pages.

Still stuck?

If none of the above fix it:

  1. Check Text to Speech → PRO Support or the support page
  2. Include: your theme name, WordPress version, plugin version, browser, a screenshot of the post and the admin TTS column