selimenesdev

ReviseFlow turns vague bug reports into actionable issues. Your visitors click the floating button, take an annotated screenshot, write a comment, and submit. The bug arrives in your ReviseFlow Board — embedded right inside wp-admin — with full browser, console, network and WordPress context, and syncs automatically to Jira or ClickUp.
This plugin embeds the ReviseFlow widget on your WordPress site. No theme edits, no copy-paste of script tags. Per-page hide, role-based visibility, an admin-bar shortcut, the full feedback board inside wp-admin, and rich WordPress context (post, theme, user role, active plugins, WooCommerce, multilang) come out of the box.
<h4>Why ReviseFlow on WordPress</h4>
<ul>
<li>Manage everything inside wp-admin — the kanban board lives in a dedicated ReviseFlow menu so you never have to leave the WordPress admin to triage bug reports.</li>
<li>One-click install — no need to paste script tags into header.php or use a code-snippet plugin.</li>
<li>Per-page control — hide the widget on specific posts or pages from the editor.</li>
<li>Role-based visibility — show the widget only to admins and editors during staging, or to all visitors in production.</li>
<li>Admin Bar shortcut — report a bug from any front-end page.</li>
<li>Rich WordPress context — every report includes the environment (production/staging/local), active theme, child-theme parent, post, user role, language, active plugins, cache plugin and page builder.</li>
<li>Works with all themes and page builders — Elementor, Divi, WPBakery, Beaver Builder, Bricks, Oxygen, Gutenberg.</li>
<li>Privacy-respecting — no tracking cookies, no third-party analytics injected.</li>
</ul>
<h4>Free plan included</h4>
ReviseFlow’s free plan gives you unlimited feedback on 1 project — no credit card required. Sign up at https://reviseflow.io to get your widget token.
<h3>External services</h3>
This plugin connects to the ReviseFlow service at https://reviseflow.io. ReviseFlow is a visual feedback and bug-reporting platform used to load the feedback widget, validate the widget token, create a secure embedded board session in wp-admin, upload submitted feedback files, and show submitted feedback in the ReviseFlow dashboard.
The plugin loads the ReviseFlow widget JavaScript bundle from https://reviseflow.io/widget/bundle.js on public pages when the widget is enabled and a widget token is configured.
After the bundle initializes, it calls https://reviseflow.io/api/widget/config to read the widget configuration. This request sends the configured widget token and, only if the administrator enabled it, the explicit ReviseFlow credit opt-in flag.
The plugin calls https://reviseflow.io/api/widget/health when a site administrator clicks “Test connection” in the plugin settings. This request sends the configured widget token so ReviseFlow can confirm that the token is valid and return the workspace, project, and plan details.
The plugin calls https://reviseflow.io/api/widget/embed-session when a site administrator opens the embedded ReviseFlow Board in wp-admin. This request sends the configured widget token and may send the current WordPress administrator’s email address and display name so ReviseFlow can create a short-lived admin board session.
When a visitor opens the widget and submits feedback, the widget calls https://reviseflow.io/api/widget/presign for file uploads and https://reviseflow.io/api/widget/feedback to create the feedback report. These requests send the feedback comment, screenshot or annotation files when captured, optional session recording or voice-note files when provided, browser and device metadata, viewport and screen size, page URL, console and network error summaries captured during the feedback session, and the WordPress context emitted by this plugin. WordPress context can include site URL, WordPress version, PHP version, environment type, locale, page type, permalink structure, REST API base URL, theme name/version, logged-in user ID and roles when available, active plugin summary, cache/page-builder detection, current post ID/type/permalink/template, WooCommerce page/cart/payment-gateway context when WooCommerce is active, and active language context when WPML or Polylang is active.
The ReviseFlow service is provided by ReviseFlow. Terms of Service: https://reviseflow.io/terms. Privacy Policy: https://reviseflow.io/privacy.

ReviseFlow — Visual Feedback & Bug Reports

Add a visual feedback widget so visitors and clients can take screenshots, draw on them, and report bugs — synced to your ReviseFlow dashboard.

WikiFleeksMedia

wikifleeksmedia

BugPost adds a lightweight bug reporting button to your site’s frontend. When clicked, it opens a clean overlay panel where visitors or team members can describe an issue. Browser details, operating system, viewport size, page URL, page load time, and JavaScript console errors are captured automatically — no extra effort needed from the reporter.
Key Features:
<ul>
<li>One-click reporting — A “Report” tab on the right side of every page opens a simple form.</li>
<li>Auto-captured context — Browser name and version, OS, viewport dimensions, page URL, page load time, and console errors are sent along with every report.</li>
<li>Console error capture — JavaScript errors and unhandled promise rejections are logged automatically and attached to the report.</li>
<li>Reporter fields — Optional name and email fields let reporters identify themselves.</li>
<li>Honeypot spam protection — A hidden field traps bots without annoying humans with CAPTCHAs.</li>
<li>Rate limiting — 3 reports per IP per hour prevents abuse.</li>
<li>“Me too” duplicate grouping — When multiple reports target the same page, earlier open reports get a +1 count so you can see which issues affect the most people.</li>
<li>Visibility modes — Choose Beta (logged-in users only) or Public (everyone). Turn it off entirely when not needed.</li>
<li>Admin dashboard — All reports in a familiar WordPress list table with status badges, reporter info, page URL, and date columns.</li>
<li>Report detail view — Each report has a full meta box showing all captured context data.</li>
<li>Status workflow — Mark reports as New, Acknowledged, In Progress, Resolved, or Closed.</li>
<li>CSV export — Download all reports as a CSV file for use in spreadsheets or external tools.</li>
<li>Customizable button color — Match the report button to your site’s brand via a color picker.</li>
<li>Fully translatable — All strings use WordPress i18n functions with the <code>bugpost</code> text domain.</li>
</ul>
What this plugin does NOT do (by design):
<ul>
<li>No external API calls, no tracking, no phoning home.</li>
<li>No CDN dependencies — all assets are bundled locally.</li>
<li>No account required to use the plugin.</li>
</ul>

BugPost

Simple frontend bug reporting overlay for WordPress. Visitors submit reports with auto-captured browser context and console errors.

ReviseFlow — Visual Feedback & Bug Reports vs BugPost