@daviorocha, thanks for the update on this. We will check this and do all necessary update in future version
This is what I did, it’s working fine, but you may find a better solution.
File: wp-ultimate-csv-importer/index.php on line 47
$get_debug_mode = get_option('wpcsvfreesettings');
if(isset($get_debug_mode['debug_mode']) && $get_debug_mode['debug_mode'] != 'enable_debug' && !WP_DEBUG) {
error_reporting(0);
ini_set('display_errors', 'Off');
}
Thanks
Sure, the work has been scheduled. Will be updated soon. Thanks for your kindness.
I found that your plugin (also) interferes in the opposite way. index.php:49-50 has
error_reporting(0);
ini_set('display_errors', 'Off');
which turns off my php errors >:(
Those functions shouldn’t be used lightly in plugin releases, it messes up everyone’s debugging. Unfortunately you’re not the only plugin doing it…
So for others who read this consider disabling the ini_set and error_reporting functions completely, at least on production.
There is an option available under additional feature in Settings menu of our plugin.You can choose to enable the debug mode & save it.
OK but by default the plugin disables debug output when activated. What if I bulk activate it on 100 sites? I’m not going to manually re-enable debug mode in the plugin page > settings > additional features a hundred times.
I think the point of WordPress having WP_DEBUG on is so that debug output is shown, the plugin is interfering with that expected behavior. I suggest you change that.