BrightLeaf Digital

PHP Compatibility Scanner helps you assess whether your site’s code (plugins and themes) is likely to run on newer versions of PHP. It performs static analysis using PHP_CodeSniffer and the PHPCompatibilityWP ruleset to flag code patterns that are incompatible with the selected target PHP version.
What the plugin does (at a glance): 
– Compares your current runtime PHP (baseline) to a selected target PHP version (8.0–8.4). 
– Scans plugins and themes, then highlights only the new issues that would appear on the target version (the “delta”). 
– Shows results in a clear report on the Tools screen and adds small badges on the Plugins list screen. 
– Lets you pause, resume, or stop a running scan.
Important limitations of static analysis: 
– Static analysis can miss issues in dynamic code paths and can generate false positives. Treat results as guidance, not guarantees. Always test site functionality on a staging environment before upgrading PHP in production.
<h3>Features</h3>
<ul>
<li>Select a target PHP version (8.0, 8.1, 8.2, 8.3, 8.4)</li>
<li>Scan all plugins or select specific ones</li>
<li>Scan all themes or select specific ones, with an option to also scan a parent if a child theme is selected</li>
<li>Pause/Resume/Stop controls for long scans</li>
<li>Clear report of only the new issues between baseline (current runtime) and target</li>
<li>Plugin list badges showing a quick summary for the last scan</li>
</ul>
<h3>Privacy</h3>
All analysis runs locally on your server. No data is sent to external services by this plugin.

BrightLeaf Digital PHP Compatibility Scanner

This plugin scans your installed plugins and themes for potential PHP compatibility issues when upgrading to newer PHP versions.

jgorres

Problem:
With “Safe SVG” alone, uploading SVG files into the WordPress Media Library works fine. As soon as you try to replace an existing file with an SVG via the “Enable Media Replace” plugin, the operation aborts with the message “Sorry, this file type is not permitted for security reasons.”.
Root cause: EMR calls <code>wp_check_filetype_and_ext()</code> directly from its own submenu (<code>upload.php?page=enable-media-replace/...</code>) without going through the standard upload path (<code>wp_handle_upload</code>). Safe SVG, however, registers its MIME-type fix only on certain admin page hooks — and those do not reliably fire on the EMR replace page in practice.
Solution:
This plugin registers the two required filters (<code>upload_mimes</code>, <code>wp_check_filetype_and_ext</code>) globally so that SVG uploads work through EMR as well.
Safety guard:
So that this plugin does not open an unsanitized SVG upload path, the filters are active only when the “Safe SVG” plugin itself is active. Safe SVG then handles the SVG sanitization on <code>wp_handle_upload_prefilter</code> / <code>wp_handle_sideload_prefilter</code>. Without an active Safe SVG, SVG remains non-uploadable.

Compatibility Fix for Safe SVG

Fixes a conflict between "Safe SVG" and "Enable Media Replace" when replacing existing media files with SVG uploads.

BrightLeaf Digital PHP Compatibility Scanner vs Compatibility Fix for Safe SVG