If commands appear in the terminal but produce no output, no response, or simply do nothing, this guide helps you identify and fix the issue.

This is one of the most common issues caused by JS conflicts, add-ons not loading, or incorrect command syntax.

---

🔹 1. Check for JavaScript Errors (Most Common) #

If the terminal JS fails anywhere, all commands stop working.

To check:

1. Right-click → Inspect
2. Open the Console tab
3. Reload the page
4. Type any command in the terminal
5. Look for errors like:

Uncaught ReferenceError: append_line is not defined
Uncaught TypeError: registry[cmd] is not a function
Failed to load resource: cointacted-social-terminal-terminal.js

If errors are present:

• Another plugin may have broken JS
• Theme optimization removed important scripts
• Add-on script is missing or corrupted
• Browser privacy extensions blocked scripts

Fixes:

• Disable cache/minify plugins
• Clear CDN cache
• Ensure no JS errors remain

---

🔹 2. Commands Not Registered (Add-On or Core Issue) #

Type:

help

If you do not see:

• CORE
• USER
• SITE
• WALLET (if wallet detected)
• FUN
• ADMIN

Or if your add-on group is missing:

• Add-on script did not load
• Add-on PHP file failed
• Metadata not registered
• Add-on is inactive

Fix:

• Reactivate the add-on
• Clear minification caches
• Check Console for loading errors
• Check PHP error logs for add-on issues

---

🔹 3. Shortcodes Duplicated or Terminal Loaded Twice #

If the terminal is accidentally rendered twice, commands may not run.

Symptoms:

• cursor misaligns
• commands do nothing
• history behaves strangely
• no output even though JS fires

Cause examples:

• using two shortcodes on one page
• builder template injecting shortcode automatically
• “dynamic content” widgets duplicating the output

Fix:
Ensure only one terminal exists per page.

---

🔹 4. Command Name Typed Incorrectly #

Some commands require small arguments or exact spelling.

Examples:

gas     (correct)
gass    (incorrect)
txcount (correct)
txCount (incorrect)

Use:

help
help core
help wallet

To verify spelling.

---

🔹 5. Add-On Commands Broken Because Add-On JS Failed #

If only add-on commands fail:

• The add-on JS is not loading
• A syntax error inside the add-on
• Wrong dependencies in enqueues
• Add-on loading before core plugin

Open browser Console → look for:

my-addon.js

If it didn’t load → fix enqueue.
If it loaded but errors → fix code.

---

🔹 6. Command Works in One Browser but Not Another #

This is usually caused by:

• Browser extensions (privacy, adblock, metamask blockers)
• Script blocking extensions
• Shield or DNS filtering
• Browser tracking protection (Safari strict mode)

Try:

• Chrome Incognito
• Firefox without extensions
• Disabling Brave shields

If it works there → browser extension blocked it.

---

🔹 7. Wallet Commands Do Nothing? (Wallet Not Exposed) #

If these commands do nothing:

• wallet
• chain
• gas
• block
• txcount

Check:

✔ MetaMask installed? #

✔ MetaMask unlocked? #

✔ Browser privacy mode disabled? #

✔ “Block third-party scripts” disabled? #

Wallet info only shows if the wallet exposes data through EIP-1193.

Core plugin never requests wallet connection, so if MetaMask is locked, wallet commands show nothing.

---

🔹 8. Commands Blocked Due to Guest Mode #

If you’re logged out and this setting is disabled:

Allow logged-out visitors to use safe commands

Then private commands produce no output.

Test:

whoami

If nothing prints (and you’re logged out), enable:

WP Admin → Cointacted → General Settings → Allow logged-out visitors…

---

🔹 9. Commands Doing Nothing After Plugin Update #

Possible causes:

• Cached JS files (browser or CDN)
• Minifiers serving old JS
• Theme caching engine still delivering old scripts

Fix:

• Clear browser cache
• Clear CDN (Cloudflare)
• Clear page builders’ caches
• Clear WP Rocket/LSCache/NitroPack
• Hard refresh: CTRL+F5

---

🔹 10. Commands Hidden or Overridden Incorrectly #

If a developer override or add-on override is broken:

• Original command becomes unreachable
• New command throws error
• help shows wrong metadata

Solution:

• Remove custom override code
• Deactivate add-on
• Reload page and test core commands again

---

🎯 Summary #

If commands do nothing:

✔ Check Console for JS errors (most common) #

✔ Confirm add-ons loaded correctly #

✔ Ensure only one terminal per page #

✔ Verify command name spelling #

✔ Check browser privacy blockers #

✔ Enable guest commands if logged out #

✔ Clear caches after plugin updates #

✔ Remove faulty overrides #

This resolves 98% of issues.