10up

Zack Tollman

At the first sign of trouble, an ostrich buries its head in the sand. Ostrichcize allows a plugin or theme developer to 
bury his or her head in the sand by turning off error reporting for select plugins or the current theme.
If you have ever installed a plugin or worked on a site with a plugin that throws numerous of errors and notices, but do 
not have the time to fix the issue, you can turn off those notices with this plugin. By simply filtering the plugin, you 
can add to the list of plugins for which no notices will be shown.
To add to this list simply write something like:
<pre><code>function my_ostrichcized_plugins( $slugs ) {
 $slugs[] = 'debug-bar-cron';
 return $slugs;
}

function my_pre_my_ostrichcized_plugins() {
 add_filter( 'ostrichcized_plugins', 'my_ostrichcized_plugins' );
}

add_action( 'plugins_loaded', 'my_pre_my_ostrichcized_plugins', 1 );
</pre>
</code></pre>
Note that the filter must be added before any offending code is run in order to redefine the error reporting function 
before it is first called. The means that in most cases, this code will need to run from a plugin and not a theme.
To turn off PHP error reporting for a theme, run:
<pre><code>function my_ostrichcize_theme() {
 add_filter( 'ostrichcize_theme', '__return_true' );
}
add_action( 'plugins_loaded', 'my_ostrichcize_theme', 1 );
</pre>
</code></pre>
Thanks to Jeremy Felt (@jeremyfelt) for assistance naming the plugin!

Ostrichcize

Hide PHP error reporting for specified plugins or the current theme.

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.

Ostrichcize vs BugPost