| 开发者 | benelwoods |
|---|---|
| 更新时间 | 2026年6月20日 09:34 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
No — the free plugin is fully functional. A license key is only needed if you also install the Pro addon.
No. Share a review link and your reviewer comments as themselves — Reviso captures their name and email when they leave their first comment.
Reviso is native to the Bricks and Elementor builders and the Gutenberg block editor, and it works on any WordPress theme or site. Pins anchor to each builder's elements (Bricks brxe-* IDs, Elementor element IDs, Gutenberg block IDs), with content and position fallbacks so they survive page edits.
Yes. A valid review link opens the page for your invited client even while Bricks or Elementor maintenance mode is on, with no login. The site stays hidden from everyone else, and revoked, expired or out-of-scope links still see the maintenance screen.
In your own WordPress database (wp_reviso_* tables). Reviso doesn't transmit comment content anywhere unless you opt in to the optional telemetry ping (which only sends version numbers + feature-enabled flags — never comment content or PII).
reviso_bypass_maintenance_mode (default true) to turn the behaviour off.reviso_notifications_settings_save / reviso_notifications_settings_extra / reviso_notifications_integrations_section); add-ons that used reviso_general_settings_save for notification fields should move to these (Reviso Pro 1.2.0 does).reviso_pre_add_comment and reviso_allow_comment_uploads filters let add-ons cap comments per review or disable file uploads for specific reviews.reviso_review_auto_open_sidebar filter.)trial_state field, so we can understand how the Pro trial is working without collecting anything identifying.Reviso_Comments::count_all() and Reviso_Review::is_pro_locked() read APIs used by the Pro add-on.__() call inside sprintf() (the rule treats the comment as belonging only to the line immediately following it), and the raw $_POST['author_email'] read in the comment-submit handler is now routed through sanitize_text_field() purely to satisfy the input-sanitization scanner (the value is still email-validated via sanitize_email() for storage).reviso_review_auto_open_sidebar filter — site-specific extensions can suppress the FE's "open the comment sidebar on page load" behaviour per-review. Default true (existing behaviour preserved). Receives the boolean and the Review row; return false to make the reviewer click the FAB themselves.identified() check still required email to be truthy — so a name-only reviewer would pass the gate, then the engine's "are we identified yet?" check would fail on the next render and re-open the gate in a loop. Fixed: identified() now returns true for any reviewer with a name (or a logged-in WP user)./reviso-review/<slug>/item/<id>/ instead of the bare permalink, so the session re-bootstraps on every navigation and the overlay appears reliably even when the destination page is cached.reviso_review_exclude_name_prefixes filter on Reviso_Review::find() and count() — site-specific extensions can hide ephemeral Reviews (e.g. an auto-generated demo) from the admin list without patching core. Pass an array of name prefixes; rows whose name LIKE prefix% are excluded./page/<id>/ → /item/<id>/. The /page/N/ segment collides with WordPress's built-in pagination, so canonical-redirect handlers (core's redirect_canonical, Rank Math, etc.) were stripping it and bouncing reviewers back to the dashboard URL. Rewrites flush automatically on first admin load after upgrade.wp_head-enqueued click handler (smooth page transitions, AJAX nav, etc.) was eating the navigation. Page cards now use a capture-phase listener that forces a hard browser navigation, plus inline onclick + target="_top" as belt-and-braces.WP_DEBUG) added to the review page-handoff path so the redirect chain is traceable from the PHP error log when something does go wrong.get_queried_object_id().review_id column on wp_reviso_comments lets the all-comments admin filter by Review, so you can see exactly which round of feedback belongs to which engagement. Legacy review-mode and builder-direct comments stay accessible (stored with NULL review_id).review_id column + index. Safe upgrade — no existing rows are altered (NULL is the documented legacy/builder-direct case).#bricks-toolbar.is-previewing.get_permalink() redirected to home, which is what reviewers were seeing. Site-specific CPTs can be added back via the reviso_reviewable_post_types filter.reviso_whitelabel_logo, reviso_whitelabel_accent) so agency branding never reached the dashboard. Portal background mode (light/dark/custom) properly applied to CSS variables./reviso-review/<slug>/ dashboard URL — the Reviews module owns that template and renders its own page list.?tab=approvals deep-links auto-redirect.Reviso_Settings::pick_logo() resolver). Added an optional email-header override + portal-background mode selector. Existing single-logo uploads keep working as a fallback./reviso-review/<slug>/ landings and emailed activation links 404'd. Added a version-keyed one-shot flush on init so this self-heals.