Sample report

WordPress plugin compatibility report example

Select an environment to inspect the verdict, the cause, and the evidence captured from that exact WordPress stack.

Product

Explore a completed compatibility scan.

Select an environment, filter failures, and inspect the same evidence available in a Folt report.

scan · accordion-blocks 2.4.1

accordion-blocks 2.4.1

209/216 passed

7 failed~41m wall clock

PHP 8.2 · WordPress 7.0

hello-elementor · with elementor

Failed

Compatibility failures

Finished in 1m 38s · node-run-013

Activation

Passed

PHP

1 fatal

0 warning/notice

HTTP failures

Console

1 errors

0 warnings

Checkout

fail

Duration

1m 38s

Environment

PHP: 8.2
WordPress: 7.0
Theme: hello-elementor
Other plugin: elementor
Worker node: node-run-013
Slowest phase: total run · 1m 38s

Timeline

preparing
provisioning database
downloading plugin
starting environment
configuring wordpress
activating plugin
running checks
collecting results
uploading artifacts
cleanup
finished

Report evidence

Every scan answers three questions.

The verdict, the failing combination, and the likely impact.

Did it work at all?

A pass/fail count across the entire matrix, with per-environment timing.

209/216

What specifically broke it?

The exact combo, the stack trace, and the file/line that triggered it.

Fatal error: Uncaught TypeError: array_map(): Argument #1 ($callback) must be a valid callback

in /var/www/html/wp-content/plugins/accordion-blocks/includes/render.php:147

env: php 8.2 · wp 7.0 · hello-elementor · elementor + woocommerce

What's the blast radius?

Popularity-weighted impact estimate — fix what hits the most sites first.

elementor + woo on php 8.2~4.1M sites

woo checkout on wp 6.9~1.8M sites

super cache deprecation~0.9M sites

$ folt scan ./your-plugin.zip

Test the combinations that matter before you ship.

100 environment runs per month on Free. No credit card required.

Start free

4 PHP versions · current and previous WordPress releases · 7 themes · 20 conflict plugins