Undergroundact Bug Reporter

Undergroundact Bug Reporter adds a configurable floating bug-report button to WordPress. Logged-in users can report an issue while they are looking at it, attach visual evidence, and automatically include useful browser and WordPress environment details. Reports stay on the WordPress site as private report records. Administrators can choose which users can report bugs, which roles can manage reports, and exactly where the reporter appears on the front end and in wp-admin. Reporting Each report can include:

• Steps to reproduce
• Expected result
• Actual result
• Severity: Low, Normal, High, or Blocking
• PNG, JPG, or WebP screenshot
• MP4, WebM, or MOV screencast
• Current page URL and referrer, with common nonce/token/secret query parameters removed before storage
• Browser, platform, language, time zone, screen, and viewport details
• WordPress, PHP, MySQL/MariaDB, and web-server information
• Site locale and multisite status
• WordPress/PHP memory limits and PHP/WordPress upload limits
• Active theme and active plugin names/versions
• WordPress debug configuration metadata
• wp-admin screen and likely plugin context when detectable

Evidence uploads are limited to 25 MB or the site's WordPress upload limit, whichever is lower. Unfinished report text is saved in the reporter's browser local storage and restored after navigation or reload. Draft text remains in that browser until it is cleared or the report is submitted. Browsers do not allow a file selection itself to be restored, so an attachment must be selected again after a reload. Triage and follow-up Authorized bug managers can:

• View reports under Undergroundact Bug Reporter Reports
• Filter by bug number, reporter, severity, date, and status
• Sort report lists
• Copy a complete bug report
• Export the current filtered and sorted result set to CSV
• Mark a bug resolved with a required resolution note
• View submitted/resolved totals by user
• View average resolution time excluding Saturdays and Sundays

Undergroundact Bug Reporter can email selected WordPress users when a new bug is filed. A still-open bug receives one reminder after seven days. When a bug is resolved, the reporter is notified and configured WordPress users can be copied. Visibility controls Reporter access can be given to all logged-in users or only selected WordPress roles. Front-end display can be configured for:

• The entire front end
• Selected public post types
• Selected individual posts or pages
• Explicitly excluded posts or pages
• No front-end display

wp-admin display can be configured for:

• All admin screens
• WordPress core screens only
• Admin areas associated with selected plugins
• Additional screen or page slugs for plugins with unusual menu structures
• No wp-admin display

Bug-management roles are configured separately from reporter roles. Administrators always retain management access, and plugin settings remain administrator-only. No required external service Undergroundact Bug Reporter does not require an account with an external service and does not send bug reports to a vendor-operated API. Reports are stored on the WordPress site. Notification mail uses the site's normal WordPress email configuration.

1.4.5

• Renamed the public plugin identity to Undergroundact Bug Reporter at the WordPress.org review team's request.
• Changed the requested WordPress.org slug and text domain to undergroundact-bug-reporter.
• Preserved existing bpbr_ data identifiers and legacy report shortcodes for backward compatibility.

1.4.4

• Renamed the public plugin identity to Bug Button Press and changed the text domain to bug-button-press.
• Moved reporter CSS and JavaScript into properly enqueued plugin assets.
• Added the [bug_button_press_reports] shortcode while preserving existing bpbr_ data identifiers and legacy report shortcodes for backward compatibility.
• Added WordPress personal-data exporter and eraser integration for stored bug reports and evidence.
• Removed absolute debug-log filesystem paths from captured diagnostics while retaining safe file-status metadata.
• Improved dialog keyboard accessibility, focus handling, status announcements, and focus visibility.
• Expanded internationalization coverage and hardened CSV formula-injection handling.
• Bounded report/reminder/counter scans in batches and restored accurate historical naming in the release history.

1.4.3

• Removed common nonce, authentication-token, password, secret, and API-key query parameters from captured report URLs, referrers, and admin request URIs before storage.
• Added site locale and multisite status to environment diagnostics.
• Added WordPress and PHP memory limits plus PHP and effective WordPress upload limits.

1.4.2

• Added the WordPress site timezone to captured environment diagnostics.
• Added WordPress and browser timezones to the environment summary so timestamp differences are immediately visible.

1.4.1

• Prepared the standalone Quick Bug Reporter package for WordPress.org directory submission.
• Changed the distributable plugin directory, main plugin filename, and text domain to quick-bug-reporter.
• Added Requires at least and Requires PHP metadata to the main plugin header.
• Added WordPress privacy-policy suggested text describing stored report, diagnostic, email, and evidence data.
• Added explicit privacy and data-retention documentation to the plugin readme.
• Preserved existing bpbr_ options, post metadata, report numbers, and legacy shortcode internally for upgrade compatibility. For earlier private-build history, see changelog.txt.