When an add-on feature misbehaves with no obvious error, run a conflict test: default theme, all other plugins off, then bring them back one at a time until the problem returns.
Back up first (or use staging). Keep the whole Coupon Creator stack active throughout — free core, Pro, and Add-ons — since Add-ons requires both and deactivating them only produces dependency notices.
The elimination procedure #
- Theme: activate Twenty Twenty-Five under Appearance → Themes and test. Front-end features (reveal overlays, email forms, MultiPrint buttons) are the most theme-sensitive — a theme that strips scripts or rewrites markup breaks them first.
- Plugins: bulk-deactivate everything except the three Coupon Creator plugins. Clear browser and site caches. Test.
- Reintroduce: reactivate one plugin at a time, testing after each; the one that brings the problem back is the conflict.
- Report: check that plugin's support channel and let us know — known conflicts get documented.
Before you run the full test #
Two add-ons checks that masquerade as conflicts:
- The feature's toggle may simply be off — check Coupons → Options → Add-Ons first.
- Email problems are usually deliverability, not conflicts — the health panel and log under Coupons → Options → Email tell you more than a conflict test will (see Email Gate troubleshooting).
For script errors surfaced during testing, see Troubleshooting JavaScript Errors; for 404s, Troubleshooting 404 Errors.
