Dev.to
7/20/2026

The original title is: "I Added Sentry to a WooCommerce Membership Site. It Caught a Real Bug Within the Hour."
Original: I Added Sentry to a WooCommerce Membership Site. It Caught a Real Bug Within the Hour.
Short summary
A lead developer integrated Sentry into a plugin-heavy WooCommerce/Divi/LearnDash membership site using the wp-sentry-integration plugin, catching a silent REST endpoint error loop within the first hour. Key decisions include splitting PHP and browser JS into separate Sentry projects, configuring via wp-config.php constants (not UI), and setting replay to capture only on errors. The post includes exact configuration snippets and gotchas like using the DSN not the CDN loader URL.
- •wp-sentry-integration plugin configures both PHP and browser SDKs via wp-config.php constants — zero UI configuration by design
- •Split PHP and browser JS into separate Sentry projects to avoid browser noise drowning out server-side errors
- •Session Replay set to 0% ambient / 100% on-error captures full user journey leading to checkout errors
Generated with AI, which can make mistakes.
Is this a good recommendation for you?



