Help & troubleshooting¶
Answers to common questions. The user manual has the full details.
Pairing and connection¶
"Test connection" fails, or the menu shows "Configure…"¶
The extension talks only to the desktop app over the local loopback, so all of these have to line up:
- The app is running. TextTemplateManager must be open on the same PC as the browser.
- The connector is on. In the app: Settings ▸ General ▸ Browser extensions (beta) — turn it on.
- The port matches. Copy the port shown there (default
47615) into the extension's options exactly. - The token matches. Copy the token too; it's sent as
x-ttm-token. If you regenerated it in the app, update the extension.
Then click Test connection again — it should report Connected: TextTemplateManager, with the app's version. A security tool that blocks loopback connections can also get in the way; allow the app's local port if you use one.
The submenu shows only "Configure…"¶
That means the extension isn't paired yet, or it lost the connection to the app. Open the options page and follow Pair it with the app. The submenu fills with your template tree as soon as the connection succeeds.
"Create template from selection" isn't offered, or does nothing¶
Saving a selection needs TextTemplateManager with API protocol 2 or newer. Update the desktop app to the current version, then try again.
Inserting templates¶
I picked a template but nothing was pasted¶
- RTF into a web editor. Most web editors ignore RTF. Set the template (or the default paste mode) to HTML or Jira for rich web paste — see Paste modes.
- SHIFT+F10 on Firefox. Opening the menu with SHIFT+F10 on Firefox is not yet supported — that path doesn't expose the target field to the extension, so nothing is inserted. Use the keyboard context-menu key or the mouse there instead.
- The field lost focus. Insertion goes to the field you opened the menu in. If focus moved, click back into the field and open the menu again.
Ctrl+click → plain text does nothing on Chrome or Edge¶
That's expected. Ctrl+click to force plain text works on Firefox only. Chromium doesn't pass modifier keys to context-menu clicks, so on Chrome/Edge a click always uses the configured default mode. To paste plain text there, set the template's mode (or the default paste mode) to plain text.
A new or renamed template isn't in the menu yet¶
The menu refreshes on its own — when the menu opens on Firefox, when you switch back to or change tabs on Chrome/Edge, and on a short timer during active use. If it still lags, switch tabs (or reopen the menu) to trigger a refresh, or reopen the browser.
Reporting a problem¶
Report it by e-mail, or as an issue on GitHub if you have an account. Both ask for the same details; GitHub issues are public, so don't post private text there. For a security vulnerability, use Reporting a security vulnerability instead.
Report by e-mail Report on GitHub
The more exactly you describe what happened, the faster it can be fixed:
- Which browser and version (Chrome, Edge or Firefox), and the extension version.
- The desktop app version (Help ▸ About), and whether the connector is enabled.
- What you did, step by step: which site and field, which template, and the paste mode.
- What you expected and what happened instead — with the exact text of any message.
- For a connection problem, what Test connection reports on the options page.
Suggesting a feature¶
Ideas are welcome, by e-mail or, with a GitHub account, on GitHub. Both open with a short form: what you'd like to get done, how you do it today, and how it could work.
Suggest by e-mail Suggest on GitHub
Reporting a security vulnerability¶
Report a vulnerability privately, never as a public issue: by e-mail (no account needed), or on GitHub with an account through the repository's private vulnerability reporting. Include the extension version, the browser, what is affected and how to reproduce it. A fix ships as an update to each store; the security policy says what's supported.