Troubleshooting TrueCommander

Most problems come down to one of a few things: the plugin not being active or licensed, a keyboard shortcut conflict, or a command being run from the wrong place. Work through the relevant section below. If you are still stuck, every license includes direct support from the dev team.

The navigator won't open

The navigator opens with ++W. If nothing happens:

• Make sure you are inside the WordPress admin (wp-admin). The navigator runs there, not on the public site.
• Confirm the plugin is active under Plugins, and that your license is activated (see the next section).
• Check for a browser or OS shortcut conflict on that key combination. Close any extension that might capture it, or test in a private window with extensions disabled.
• Click once inside the admin page first so the browser tab has focus, then try the shortcut again.

My license won't activate

Paste the license key from your account dashboard at my.trueplugins.com into the TrueCommander settings. If it is rejected:

• Check for a stray space copied before or after the key, and that you used the key from the same account you purchased with.
• You may have reached your plan's activation limit. Deactivate the license on a site you no longer use from your dashboard, then activate here.
• Make sure the site can reach the internet to validate the key. Some firewalls block outbound calls.

Your dashboard shows every active site, so you can always see where the license is in use.

A command looks missing or "can't run here"

Not every command runs in every place. Commands declare where they are allowed to run, so a command might appear in the navigator but not be available to schedule, or only make sense on a specific screen.

• Run the command from the navigator first to confirm it works at all.
• If you are trying to schedule or run it on startup and it is not offered, that command does not support that context. Pick one that does in the Scheduled or Startup Commands module.
• Some commands ask for a detail before they run (a label, a recipient, a target). Fill that in when prompted.

AI commands aren't working

AI commands send a request to an external AI provider, so they need a provider API key saved in the plugin's AI settings. If they fail or do nothing:

• Add a valid AI provider key in the AI Commands settings.
• In advanced mode, AI commands use the tp ai prefix, for example tp ai summarize. In easy mode, drop the prefix.
• If the provider rejects the request, check that the key is active and has remaining quota on the provider's side.

More quick answers