Skip to main content
WP HealthKit

Designed2Use Convert to WebP/AVIF — Known Conflicts & Compatibility

Medium Conflict Risk

This plugin has some potential conflict points that may cause issues with certain other plugins.

Conflict Summary

Unprefixed Functions

6

Global functions without a unique prefix

Handle Conflicts

0

CSS/JS handles that may clash

Namespace Conflicts

0

PHP namespace or class name collisions

Shortcode Conflicts

0

Shortcode names that may conflict

What This Means

Unprefixed functions are global PHP functions that do not use a unique prefix (e.g., my_plugin_). When two plugins define a function with the same name, PHP throws a fatal error. The more unprefixed functions a plugin has, the higher the chance of conflicts.

Handle conflicts occur when plugins register CSS or JavaScript assets with common names like style or script, causing one plugin to overwrite another's assets.

Namespace and shortcode conflicts can cause class autoloading failures or shortcode output from the wrong plugin.

View Full Security Audit Check Your Own Plugin

Frequently Asked Questions

Does Designed2Use Convert to WebP/AVIF conflict with other plugins?

Designed2Use Convert to WebP/AVIF has a medium conflict risk. WP HealthKit detected 6 unprefixed functions, 0 handle conflicts, 0 namespace conflicts, and 0 shortcode conflicts.

Is Designed2Use Convert to WebP/AVIF compatible with popular plugins?

Based on static analysis, Designed2Use Convert to WebP/AVIF has 6 potential conflict points. Some unprefixed functions may clash with other plugins.