Fix issues where logged-out users cannot run commands or see expected output.

Guest Mode controls whether logged-out visitors can use terminal commands.
If commands work for logged-in users but not for visitors, this guide explains why and how to fix it.

---

🔹 1. Check the Guest Mode Setting (Most Common Cause) #

Go to:

WP Admin → Cointacted → General Settings

Look for:

Allow logged-out visitors to use safe commands

If disabled, guests cannot run any commands that are:

• private
• user-specific
• wallet-specific
• admin-specific

This means many commands will appear to “do nothing.”

Fix: #

Turn it ON if you want visitors to use public-safe commands.

---

🔹 2. Understanding Public vs Private Commands #

Each command has metadata:

public: true   // visible to guests
public: false  // only for logged-in users

Guest mode does not make all commands public.

It only enables public-safe commands such as:

• help
• hostname
• dns
• ping
• browser
• fortune
• quote
• menu
• social
• contact
• legal

Commands marked public: false will always require login.

For example:

whoami
lastlogin
wallet
chain
txcount
admin

…are never available to guests for privacy and security reasons.

---

🔹 3. Guest Mode Enabled but Commands Still Silent #

If you have guest access enabled but safe commands still produce nothing:

Possible issues: #

✔ Theme or builder blocking input #

(see Article “Terminal Input Not Typing”)

✔ JS error stopping execution #

Check console for errors.

✔ Add-on commands are private #

Some add-ons require login because they access:

• usermeta
• REST data
• Web3 wallet
• community plugin data

Fix:
Log in or adjust add-on configuration (if supported).

---

🔹 4. Help Output Looks Empty for Guests #

If guests see fewer command groups in help, this is normal.

The help system automatically hides:

• private commands
• add-on commands that require login
• admin-only commands
• commands not marked public: true

Example guest help output might show:

CORE – 4 commands
SITE – 2 commands
NETWORK – 1 command
CLIENT – 2 commands
FUN – 3 commands

And logged-in help might show:

CORE – 9 commands
USER – 2 commands
WALLET – 6 commands
ADMIN – 1 command

This is correct by design.

---

🔹 5. Guest Mode Affected by Caching Plugins #

If your site uses:

• WP Rocket
• LiteSpeed Cache
• Cloudflare cache
• NitroPack
• SG Optimizer

Visitors may be served cached HTML from a logged-in session or logged-out session, causing inconsistent terminal behavior.

Fix:

• Exclude the terminal page from caching
• Or disable caching for logged-out users (recommended)

---

🔹 6. Guest Cannot Use Commands on Pages Restricted by Membership Plugins #

Some plugins block all frontend JS for guests:

• BuddyBoss private pages
• RestrictContentPro
• Paid Memberships Pro
• Wishlist Member
• FluentCRM/FluentCommunity restricted pages
• WooCommerce MyAccount page (when not logged in)

If terminal is placed inside restricted content:
Guests cannot interact with it.

Fix:

• Place the terminal shortcode on a public page
• Or configure your membership plugin to allow access

---

🔹 7. Guest Mode Affects Wallet Commands (Expected) #

Wallet commands will never run for guests.

Examples:

wallet
chain
gas
block
txcount

This is enforced by:

• the plugin
• WordPress.org policy
• privacy and security requirements

Wallet info is only readable when:

• user is logged in
• wallet is exposed
• user not in guest mode

---

🔹 8. Guest Mode Disabled but You Still Want Certain Commands Public #

If you want to override specific commands:

Example: Allow browser but not whoami.

Add custom JS:

CointactedSocialTerminalTerminal.commands_meta.browser.public = true;

Or for your own commands:

commands_meta.mycommand.public = true;

Note:
Private core commands cannot be made public (for security reasons).

---

🔹 9. Guest Mode Conflicts With Add-Ons #

Some add-ons (like Social Mining, myCred, EVM) require:

• authentication
• wallet connection
• usermeta

Because guests do not have:

• user IDs
• reward logs
• wallets connected

These commands will be hidden for guests.

This is normal.

---

🎯 Summary #

If guests cannot run commands:

✔ Enable “Allow logged-out visitors to use safe commands” #

✔ Only public: true commands work for guests #

✔ Some commands never work for guests (wallet/admin/user-specific) #

✔ Caching plugins may cause inconsistent behavior #

✔ Membership plugins may block terminal scripts #

✔ Check JS console for errors #

✔ Help output is intentionally reduced for guests #

Guest mode is designed to be safe, controlled, and privacy-respecting.