Troubleshooting

Troubleshooting

The Reviso panel doesn’t appear in Bricks Builder

1. Make sure you’re in builder mode (URL ends with ?bricks=run).
2. Hard-refresh (Cmd-Shift-R / Ctrl-Shift-R).
3. Check the browser console for JS errors. If you see “Reviso is not defined” or similar, a plugin conflict is preventing Reviso’s scripts from loading — try deactivating other plugins one at a time.

Pins don’t stick where I dropped them

Reviso anchors to Bricks element IDs (brxe-…). If you change a page’s template or rebuild a section from scratch, the IDs change — old pins fall back to their content-hash or position anchor. If the element is gone entirely, the pin shows “Element removed” but the comment is kept in the sidebar.

Reviewer can’t access the link

1. Has the review expired? Default expiry is 30 days. Open the review in admin → check the expiry → reopen / extend if needed.
2. Has the review been closed? Look at the status badge in the Reviews list.
3. Email-restricted mode — make sure they’re clicking the magic link from the email you sent, not pasting the public URL. The public URL gates them out and shows “Open your magic link” instead.
4. Magic link already used on another device — click Resend in the admin. The old activation cookie is invalidated and a fresh link emails out.

Notifications aren’t arriving

See notifications.md → Common issues. The single most common cause is WordPress’s wp_mail() failing silently — install FluentSMTP and configure your sending provider.

“Database Error” on the reviewer landing

Reviso uses 4 custom tables (wp_reviso_*). If your WP-admin shows them missing:

1. Plugins → deactivate Reviso → re-activate. That re-runs the schema migration.
2. If still broken, manually trigger via WP-CLI:
   bash wp eval 'Reviso_Migrations::run("0.0.0"); echo "ok\n";'

License activation fails on a Cloudpanel / nginx setup

If you’re getting a “Database Error” page or a WordPress error during activation, the problem is usually nginx routing the Reviso admin AJAX through WordPress’s index.php (which is fine — but only when the database is reachable). Check that:

1. Your wp-config.php database credentials are correct (a temporary DB outage will surface here).
2. Nginx is serving wp-admin/admin-ajax.php directly, not via a catch-all rewrite.

Comments appear but never trigger AI auto-triage

1. AI must be enabled in Settings → AI with a valid API key.
2. The Auto-triage new comments checkbox must be ticked.
3. Your licence must be active (auto-triage is Pro).
4. Triage runs on WP-cron — if your site has very low traffic, cron may not fire promptly. Set up a real cron job via your host to call wp-cron.php every 5 minutes.

I activated Pro but my settings disappeared

That shouldn’t happen — settings persist across activations. If a tab is genuinely missing:

1. Check the WordPress error log at wp-content/debug.log.
2. If you see “class Reviso_Whitelabel not found” or similar, the Pro plugin’s autoloader can’t find the moved module file. Re-install Pro fresh.

How do I report a bug?

1. Reproduce the issue cleanly (one page, one reviewer if possible).
2. Take a screenshot.
3. Copy the relevant chunk of wp-content/debug.log (enable WP_DEBUG_LOG first if it’s off).
4. Email ben@getreviso.io with: WordPress version, Bricks version, Reviso version (Settings → General → footer), Pro version if applicable, the steps to reproduce, the screenshot, and the debug log excerpt.

Where do I see what version I’m on?

WP-admin → Settings → Reviso → look at the page footer. It shows both Free and Pro versions.

You can also check via the Plugins screen — both plugins appear there with their version numbers.