Control Reviso frontend UI visibility

Available in Reviso Free 1.7.1 and later. Developers can use reviso_frontend_ui_enabled to hide Reviso’s frontend feedback controls for a custom integration. Without a callback, Reviso works as before.

Hide the frontend UI

Register the filter in a site plugin or mu-plugin before template_redirect priority 1. This example hides the UI on every frontend request, including client feedback pages:

add_filter('reviso_frontend_ui_enabled', '__return_false');

For a builder canvas, apply the opt-out only when your integration’s verified request condition matches. Return the incoming value for other requests.

Choose a context

The second argument is internal, review, review_chrome, or admin_bar. To hide only the team’s internal overlay:

add_filter('reviso_frontend_ui_enabled', static function ($enabled, $context) {
    return $context === 'internal' ? false : $enabled;
}, 10, 2);

What this changes

The filter controls frontend feedback, pins, the review switcher and chrome, and Reviso’s frontend toolbar controls. It does not remove the entire WordPress toolbar, native editor integrations, wp-admin feedback, stored comments, MCP tools, or review access checks. It is a visibility control, not an access-control mechanism.

Remove the callback to restore normal behaviour. Comments and settings are retained.

Etch and other builders

This is a generic integration hook. Automatic Etch detection and native Etch integration are not included. Use a verified builder request condition; do not assume a particular URL parameter identifies the canvas.