Blog
Why "works on my machine" fails for WordPress plugins
Your stack is not your user's stack. Here is why single-environment testing misses the failures that become one-star reviews.
Every plugin developer has shipped a release that passed local QA and still broke production sites. WordPress makes this easy.
Your stack is an outlier
You run a recent PHP release, current WordPress, your theme, and a curated plugin set. A user may run an older supported PHP release, the previous supported WordPress release, another theme, and plugins you never installed.
Their fatal error is your one-star review — and the ticket rarely includes a stack trace.
Activation is not enough
Many plugins pass a quick activation test but fail when:
- Another plugin registers the same hook first
- A page builder enqueues scripts your code assumes are absent
- WooCommerce loads checkout templates your plugin mutates
You need execution across combinations, not a smoke test on one site.
Support tickets hide the matrix
“White screen after update” and “conflicts with some other plugin” are compatibility bugs described as mysteries. Without a matrix, you guess which combo to reproduce.
Test the matrix before you ship
Folt expands a scan into selected environment runs across PHP, WordPress, themes, and conflict plugins, then groups the failing combinations in one report. The current full matrix is broader than the 100 monthly runs included on Free.
See a sample report, compare Folt with manual VM testing, or review plan allowances.