Security release. Fixes a stored XSS reachable by any user with the reporter capability against managers viewing the admin bug list. Updating is recommended for every install.<\/p>","2.0.0":"
First public release. Per chi viene da PaneStudio Debug v1.x: migration data automatica all'attivazione. Tutti i bug esistenti restano accessibili.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3573025,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3573025,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3572616,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3572616,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["2.0.10","2.0.11","2.0.12"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"On-page floating widget for creating bugs directly on the page","2":"Admin list with filters by status, priority, author","3":"Keyboard shortcut configuration with free-form capture","4":"Settings: reporter \/ manager roles, feedback, REST integration","5":"Pin selector cascade documentation"}},"plugin_section":[],"plugin_tags":[14783,94,108,39803,7615],"plugin_category":[42,59],"plugin_contributors":[267182],"plugin_business_model":[],"class_list":["post-322450","plugin","type-plugin","status-publish","hentry","plugin_tags-bug-tracker","plugin_tags-debug","plugin_tags-feedback","plugin_tags-pre-launch","plugin_tags-qa","plugin_category-contact-forms","plugin_category-utilities-and-tools","plugin_contributors-abiagio","plugin_committers-abiagio"],"banners":{"banner":"https:\/\/ps.w.org\/breadbugger\/assets\/banner-772x250.png?rev=3572616","banner_2x":"https:\/\/ps.w.org\/breadbugger\/assets\/banner-1544x500.png?rev=3572616","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/breadbugger\/assets\/icon-128x128.png?rev=3573025","icon_2x":"https:\/\/ps.w.org\/breadbugger\/assets\/icon-256x256.png?rev=3573025","generated":false},"screenshots":[],"raw_content":"\n
Breadbugger<\/strong> is a bug tracking tool built for the pre-launch phase of a WordPress site \u2014 the moment when designers, QA, developers and clients walk through the site looking for issues before go-live.<\/p>\n\n Three complementary surfaces:<\/p>\n\n Client site pre-go-live: 5-10 people testing in parallel. Each one loads the site, opens the widget with a shortcut, pins the issue directly on the affected element. The PM \/ dev watches the admin list, sorts by priority, assigns fixes, marks resolved.<\/p>\n\n Standalone. No external SaaS required. No data sent to third-party servers. Your bugs stay in your database.<\/p>\n\n\n No. All data stays in your WordPress database. The only optional exception: the \"Feedback\" form in settings, when submitted, sends an email to the author through your site's mail system ( Yes, but it is designed for pre-launch. For end-user support tickets there are better solutions (Zendesk, Freshdesk, etc.).<\/p><\/dd>\n No, it is opt-in. Without it the plugin cascades to id, class, positional CSS. It is useful only on 5-10 cornerstone blocks of the site to get extremely stable pins.<\/p><\/dd>\n Settings \u2192 \"REST API for external clients\" \u2192 generate an app-password \u2192 use the header Yes, Settings \u2192 Visibility \u2192 \"Reporters see only their own reports\". Managers always see everything.<\/p><\/dd>\n uninstall.php removes everything (bugs, settings, capabilities, attachments owned by the plugin, app-passwords containing \"Breadbugger\" in the name). If you want to keep your data, deactivate<\/strong> instead of uninstalling.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
Key features<\/h4>\n\n
\n
data-breadbugger-name<\/code> (opt-in dev), then stable id<\/code>, then semantic class, then positional CSS. Pins survive refactors.<\/li>\ngetDisplayMedia<\/code> (HTML2Canvas-Pro as a fallback for modern CSS like oklch<\/code> \/ color-mix<\/code>).<\/li>\nwp_mail<\/code>.<\/li>\nUse case<\/h4>\n\n
\n
breadbugger<\/code> folder to \/wp-content\/plugins\/<\/code>, or install from WP Admin \u2192 Plugins \u2192 Add New \u2192 Upload Plugin.<\/li>\n\u2318+E<\/code> \/ Ctrl+E<\/code>) \u2192 create your first report.<\/li>\n<\/ol>\n\n\n\n
Does the plugin send data to external servers?<\/h3><\/dt>\n
wp_mail<\/code>).<\/p><\/dd>\nCan I use it in production, not just pre-launch?<\/h3><\/dt>\n
Do I have to add `data-breadbugger-name` everywhere?<\/h3><\/dt>\n
How do I integrate Breadbugger with my AI coding assistant?<\/h3><\/dt>\n
Authorization: Basic <user:app-password><\/code> in REST calls. Base endpoint: \/wp-json\/breadbugger\/v1\/bugs<\/code>.<\/p><\/dd>\nCan I restrict reporters to see only their own bugs?<\/h3><\/dt>\n
Will uninstalling delete my data?<\/h3><\/dt>\n
2.0.12<\/h4>\n\n
\n
line<\/code> and col<\/code> fields of a captured JavaScript error were interpolated into the diagnostics panel without escaping, so a user holding only the breadbugger_report<\/code> capability could store markup that executed in a manager's session when the list was opened. Both fields are now escaped at render time. Reported to the WordPress.org plugins team by a third party.<\/li>\nsanitize_textarea_field()<\/code>, errors[].line<\/code> \/ errors[].col<\/code> cast to integers, and depth and item count bounded \u2014 so no current or future diagnostics field reaches an output sink unfiltered. Existing reports stored before this release are covered by the output escaping above.<\/li>\nsrc<\/code> and the REST error message rendered on a failed list load, matching the escaping already applied to their sibling fields.<\/li>\n<\/ul>\n\n2.0.11<\/h4>\n\n
\n
2.0.10<\/h4>\n\n
\n
breadbugger_report<\/code> capability), where they see only their own reports when \"reporters see own only\" is enabled. The Settings page remains manager-only.<\/li>\n2.0.9<\/h4>\n\n
\n
2.0.8<\/h4>\n\n
\n
categoria<\/code> value before rendering it in the admin list (prevents stored attribute-injection in the device chip).<\/li>\n2.0.7<\/h4>\n\n
\n
2.0.6<\/h4>\n\n
\n
\/me\/preferences<\/code> (GET + POST) backed by user_meta<\/code> for per-user UI preferences.<\/li>\n<\/ul>\n\n2.0.5<\/h4>\n\n
\n
load_plugin_textdomain<\/code> call \u2014 WordPress.org auto-loads translations since WP 4.6.<\/li>\n.distignore<\/code> itself to its own exclude list (no longer leaks as a hidden file in the ZIP).<\/li>\nphpcs:ignore<\/code> comments with rationale on legitimate direct DB queries (uninstall cleanup, migration UPDATEs, sequential bug numbering, queue dispatch enumeration) and on the file-scope variables in admin views (which are method-scoped via include, not global).<\/li>\n<\/ul>\n\n2.0.4<\/h4>\n\n
\n
\n
Breadbugger_Notifications<\/code> con queue per-utente in user_meta + cron breadbugger_5min<\/code> per dispatch batched. Daily a 8:00 UTC, weekly luned\u00ec 8:00 UTC.<\/li>\nBreadbugger_Mailer::event_email()<\/code> (nuovo bug \/ risolto) + digest_email()<\/code> (recap con elenco eventi cliccabili, etichette colorate, ordinati per timestamp).<\/li>\ncreate_bug<\/code> \u2192 dispatch 'new_bug' e su update_bug<\/code> quando lo status passa a done\/done_by_ai\/closed \u2192 dispatch 'resolution'.<\/li>\ndone_by_ai<\/code> invece di done<\/code> \u2014 il developer promuover\u00e0 manualmente a done<\/code> dopo review.<\/li>\n<\/ul>\n\n2.0.3<\/h4>\n\n
\n
#bug-{id}<\/code> in URL (es. dal link nelle email) \u2014 il bug viene scrollato in vista e segnato con un accento cream a sinistra che pulsa 3 volte. Funziona anche su hashchange (clic su un altro link senza ricaricare).<\/li>\nBreadbugger_Mailer<\/code> con template dark theme: pane logo + wordmark, blockquote nota su cream accent, CTA \"Vai al bug \u2192\", footer co-branded \"a PaneStudio tool\".<\/li>\n[Breadbugger \u00b7 NomeSito] Autore ti ha menzionato su \"Bug\"<\/code>. Stesso pattern su feedback form.<\/li>\n<\/ul>\n\n2.0.2<\/h4>\n\n
\n
2.0.1<\/h4>\n\n
\n
\\u00XX<\/code> (mancava wp_slash + JSON_UNESCAPED_UNICODE in set_array_meta).<\/li>\n2.0.0<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n