Title: Undergroundact Bug Reporter Author: btolman Published: Сентябрь 9, 2026 Last modified: Сентябрь 9, 2026 --- Search plugins ![](https://ps.w.org/undergroundact-bug-reporter/assets/banner-772x250.png?rev=3688677) ![](https://ps.w.org/undergroundact-bug-reporter/assets/icon-256x256.png?rev=3688677) # Undergroundact Bug Reporter By [btolman](https://profiles.wordpress.org/btolman/) [Download](https://downloads.wordpress.org/plugin/undergroundact-bug-reporter.1.4.5.zip) * [Details](https://os.wordpress.org/plugins/undergroundact-bug-reporter/#description) * [Reviews](https://os.wordpress.org/plugins/undergroundact-bug-reporter/#reviews) * [Installation](https://os.wordpress.org/plugins/undergroundact-bug-reporter/#installation) * [Development](https://os.wordpress.org/plugins/undergroundact-bug-reporter/#developers) [Support](https://wordpress.org/support/plugin/undergroundact-bug-reporter/) ## Description 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. ### Privacy Undergroundact Bug Reporter can store information about the reporting WordPress user, including user ID, login, display name, email address, and roles. Reports can also store page URLs/referrers, browser and viewport details, server/software versions and resource limits, site locale and multisite status, active theme and plugin information, debug configuration metadata, resolution information, and screenshots or screencasts supplied by the reporter. Common nonce, authentication-token, password, secret, and API-key query parameters are removed from captured URLs before storage. This information is stored on the WordPress site and is visible to configured bug- manager roles. Notification emails are sent through the site’s WordPress email configuration to recipients selected by an administrator. Evidence is stored in the standard WordPress uploads location with randomized filenames and may be directly accessible if its URL is known. Reporters should not submit secrets or other sensitive information. Undergroundact Bug Reporter adds suggested privacy-policy text to WordPress under Settings > Privacy so site administrators can incorporate the disclosure appropriate for their site. It also integrates with WordPress personal-data export and erasure requests. A confirmed erasure request removes reports associated with the requested email address, including their stored evidence files. ## Installation 1. Install and activate Undergroundact Bug Reporter. 2. Go to Settings > Undergroundact Bug Reporter. 3. Choose reporter roles, bug-manager roles, front-end visibility, wp-admin visibility, notification recipients, and the optional floating button image URLs. 4. Visit a permitted page or admin screen while logged in and use the floating button to submit a report. 5. Authorized managers can review reports under Undergroundact Bug Reporter Reports. ## FAQ ### Can logged-out visitors submit reports? No. Undergroundact Bug Reporter currently requires a logged-in WordPress user. Administrators can allow all logged-in users or restrict reporting to selected roles. ### Does Undergroundact Bug Reporter send report data to an external service? No vendor-operated reporting service is required or used. Reports are stored on the WordPress site. Notification email is sent through WordPress using the site’s configured mail delivery. If an administrator chooses a floating button image hosted on another domain, browsers that display that image will request it from that host. ### Where are screenshots and screencasts stored? Evidence files are stored in the standard WordPress uploads location with randomized filenames and are not added as Media Library attachments. Like normal files in the uploads directory, they may be directly reachable if the file URL is known. Do not include passwords, payment card information, private keys, medical information, or other sensitive data in a report or attachment. ### Does deleting or deactivating the plugin delete reports? No. Undergroundact Bug Reporter deliberately does not automatically delete existing bug report records or evidence when the plugin is deactivated or removed. This avoids unexpected loss of QA history. Site administrators should apply their own retention policy to stored reports and evidence. ### Can I display the report table somewhere other than the Undergroundact Bug Reporter Reports admin page? Yes. Authorized bug managers can use the `[bug_button_press_reports]` shortcode. The legacy `[quick_bug_reports]` and `[bplanner_bug_reports]` shortcodes remain available for installations upgraded from earlier builds. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Undergroundact Bug Reporter” is open source software. The following people have contributed to this plugin. Contributors * [ btolman ](https://profiles.wordpress.org/btolman/) [Translate “Undergroundact Bug Reporter” into your language.](https://translate.wordpress.org/projects/wp-plugins/undergroundact-bug-reporter) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/undergroundact-bug-reporter/), check out the [SVN repository](https://plugins.svn.wordpress.org/undergroundact-bug-reporter/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/undergroundact-bug-reporter/) by [RSS](https://plugins.trac.wordpress.org/log/undergroundact-bug-reporter/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 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`. ## Meta * Version **1.4.5** * Last updated **23 сахаты ago** * Active installations **Fewer than 10** * WordPress version ** 6.0 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/undergroundact-bug-reporter/) * Tags * [bug reporting](https://os.wordpress.org/plugins/tags/bug-reporting/)[diagnostics](https://os.wordpress.org/plugins/tags/diagnostics/) [q&a](https://os.wordpress.org/plugins/tags/qa/)[support](https://os.wordpress.org/plugins/tags/support/) [testing](https://os.wordpress.org/plugins/tags/testing/) * [Advanced View](https://os.wordpress.org/plugins/undergroundact-bug-reporter/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/undergroundact-bug-reporter/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/undergroundact-bug-reporter/reviews/) ## Contributors * [ btolman ](https://profiles.wordpress.org/btolman/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/undergroundact-bug-reporter/)