RT Advance Order Reporting adds a powerful reporting section under WooCommerce in the WordPress admin. Version 2.0 rebuilds the dashboard interface in React (charts via Recharts) while keeping the same server-side data layer and AJAX endpoints.
Features
<ul>
<li>Sales Summary – revenue, order count, AOV, items sold + daily revenue/orders chart</li>
<li>Orders by Status – doughnut chart + breakdown table</li>
<li>Top Products – ranked by revenue with visual bar meters</li>
<li>Top Customers – ranked by lifetime value in the selected period</li>
<li>Refunds & Cancellations – summary KPIs + full order table with direct admin links</li>
<li>Period filters: Today, Yesterday, This Week, This Month, Last Month, This Year, Custom Range</li>
<li>Advanced filters: billing email, country & state (billing or shipping scope), payment gateway, shipping method, and tax class — applied across every report tab and the CSV export</li>
<li>CSV Export for every report tab</li>
<li>Auto-refreshes every 60 seconds (live badge) + manual refresh</li>
<li>WordPress Dashboard Widget showing today’s totals at a glance</li>
</ul>
<h3>For developers</h3>
The React source lives in <code>src/</code>. To rebuild the bundle after editing it:
<pre><code>npm install
npm run build # builds assets/css/dashboard.css (Sass) + assets/js/dashboard.js (esbuild)
npm run watch:js # rebuild JS on change
npm run watch:css # rebuild CSS on change
</code></pre>
Build tooling: esbuild (JS bundling) + Dart Sass (styles). Styles are authored 
in src/dashboard.scss as hand-written, custom CSS — no utility framework — with 
every rule scoped under <code>.rtao-aor-app</code> so wp-admin styling is never affected. 
React, ReactDOM, Recharts and icons are bundled into a single self-contained 
file, so the script declares no WordPress JS dependencies.
The data contract is unchanged from 1.x: the React app POSTs to admin-ajax.php 
(<code>action=rtao_aor_data</code>) and reads <code>window.rtaoAOR</code> (ajaxurl, nonce, currency). 
CSV export reuses <code>action=rtao_aor_export</code>.

RT Advance Order Reporting

Real-time advanced order reporting dashboard for WooCommerce, with a React interface.

Guilherme Dumas Peres

CSP Violation Reporter adds a public WordPress REST endpoint for browser Content Security Policy violation reports and stores received violations in a local database table.
Reports can be reviewed from Tools > CSP Violations. The plugin supports the modern Reporting API payload format as well as the older <code>csp-report</code> JSON shape.
Endpoint:
<pre><code>/wp-json/csp-violation-reporter/v1/report
</code></pre>
The plugin does not create or modify Content Security Policy headers. Site owners should configure CSP headers in their web server, hosting dashboard, theme, or security tooling.
Example report endpoint configuration:
<pre><code>Content-Security-Policy: default-src 'self'; report-uri https://example.com/wp-json/csp-violation-reporter/v1/report
</code></pre>
For the modern Reporting API, use an HTTPS endpoint:
<pre><code>Reporting-Endpoints: csp-endpoint="https://example.com/wp-json/csp-violation-reporter/v1/report"

Content-Security-Policy: default-src 'self'; report-to csp-endpoint
</code></pre>
<h3>Privacy</h3>
This plugin stores CSP violation reports submitted by browsers. Stored fields can include the document URL, referrer URL, blocked URI, violated directive, source file, line and column numbers, a user agent string, a salted hash of the remote address, and the raw report payload.
The plugin does not store raw IP addresses and does not transmit report data to external services.

CSP Violation Reporter

Collect Content Security Policy violation reports through a WordPress REST endpoint and review them in the admin dashboard.

RT Advance Order Reporting vs CSP Violation Reporter