If TranslateSense is missing from the WordPress editor, first check whether the current post type is supported by Polylang and whether you are editing the original post or an existing translation. TranslateSense adds its editor tools to supported editing screens; it does not display the same translation panel on every post.
Check the plugin and post type
- Confirm that both TranslateSense and Polylang are installed and active.
- Open the affected post type in WordPress and check Polylang settings to confirm that this post type is enabled for translation.
- Open an eligible source post. TranslateSense intentionally suppresses its editor integration for posts that it identifies as already translated; open the source post if you need to start another translation.
- Confirm that TranslateSense is up to date and that the post is being edited in a supported screen: the block editor, Classic Editor, or Elementor editor.
Check language and provider setup
Make sure the source post has the intended language in Polylang and that the language you want to translate into is configured on the site. If the panel appears but a translation cannot start, check that a provider is available and configured separately; a provider problem is not the same as an editor integration problem.
See Install TranslateSense, Configure Polylang Languages, and Verify Provider Configuration.
Check browser and WordPress errors
- Reload the post editor after confirming the plugin and post-type settings.
- Open the browser developer tools and check the Console and Network panels for failed TranslateSense scripts or requests.
- If a request to the TranslateSense REST API fails, note the HTTP status and error message. Check WordPress or server logs for a matching error and review whether a security, caching, or optimization plugin is blocking the request.
- Retest with a small source post before changing additional settings.
When asking for support, include the WordPress version, TranslateSense version, editor type, post type, and a redacted error message. Never include API keys, authentication tokens, cookies, or other secrets.
Screenshot to add: [TranslateSense editor panel on an eligible source post]