Warning: Missing argument 1

I too am having the exact same warning issues with debugging turned off.
I’m using the latest PHP version of 7 + so it shouldn’ be that.

Regards

Micheala

I’m also seeing these errors with MaxiCharts 1.0.4, WordPress 4.8.1 and PHP 5.5.38. I have debugging on (including define(‘WP_DEBUG_DISPLAY’, true);).

Warning: Missing argument 1 for MAXICHARTSAPI::getLogger(), called in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_data_conversion_plugin.php on line 19 and defined in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_utils.php on line 47

Notice: Undefined variable: logger_category in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_utils.php on line 52

Notice: Constant PLUGIN_PATH already defined in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_custom_criteria_plugin.php on line 7

Warning: Missing argument 1 for MAXICHARTSAPI::getLogger(), called in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_custom_criteria_plugin.php on line 20 and defined in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_utils.php on line 47

Notice: Undefined variable: logger_category in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_utils.php on line 52

Notice: Constant PLUGIN_PATH already defined in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_table_plugin.php on line 6

Warning: Missing argument 1 for MAXICHARTSAPI::getLogger(), called in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_table_plugin.php on line 15 and defined in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_utils.php on line 47

Notice: Undefined variable: logger_category in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_utils.php on line 52

Warning: Missing argument 1 for MAXICHARTSAPI::getLogger(), called in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\maxicharts.php on line 65 and defined in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_utils.php on line 47

Notice: Undefined variable: logger_category in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_utils.php on line 52

Warning: Missing argument 1 for MAXICHARTSAPI::getLogger(), called in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\maxicharts.php on line 49 and defined in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_utils.php on line 47

Notice: Undefined variable: logger_category in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_utils.php on line 52

Hi guys,

Sorry for the delay, this is a bug in maxicharts, but that shouldn’t produce more problems than this warning line.

It will be fixed in next released.

Thank you all for your feedback

Can you please tell if this is fixed in 1.0.5 version ?

Hi,

Thanks for the update.

When activating MaxiCharts v1.0.5, I get the following messages on the screen:

Notice: Constant PLUGIN_PATH already defined in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_custom_criteria_plugin.php on line 7

Notice: Constant PLUGIN_PATH already defined in C:\inetpub\wwwroot\wpfiresidetheatre\wp-content\plugins\maxicharts\mcharts_table_plugin.php on line 6
Skip to main contentSkip to toolbar

The plugin generated 380 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

The top two messages appear on every page.

I still do not see the MaxiCharts graph on our test page.

Thank you for your help with this. I’m afraid I’m going to have to let this go for now. I will be uninstalling the plugin and won’t be able to do more testing.

Ok, sorry about that, cannot reproduce on my side.
Please give me an access to your site (use maxicharts contact form) if you need me to check this problem.

@pablowprs : still the same problem with v1.0.5 ?
Thanks

@larrydaniele : still buggy ? Can i help ?

@munger41 : Thanks for asking. We’re not using the plugin currently, so I don’t have any more information for you.

Ok @larrydaniele thanks for your feedback. I’ll stay available in case you need. ??