Redefining already defined constructor

Hi there. Thanks for the info. We will check the next days and come back to you.

This error still happens. And furthermore, it can conflict with some plugins.

When I’m setting up WPML for the first time I have to disable this plugin because if not I can’t end the configuration process.

Hi there,

We are using this plugin on several sites with WPML and never saw this error.

The error you get is the same as first time?

Strict Standards: Redefining already defined constructor for class ip_address_memory_usage in eclypse.org\wp-content\plugins\server-ip-memory-usage\server-ip-memory-usage.php on line 40

If you confirm or send the exact error you got, we will have a look into it next week.

Sorry for the inconvenience.

Hi, thanks. The error is the same. Both in the backend and in the frontend, when WP_DEBUG is set to true:

Strict Standards: Redefining already defined constructor for class ip_address_memory_usage in /home/---/public_html/wp-content/plugins/server-ip-memory-usage/server-ip-memory-usage.php on line 40

The thing is I no longer saw the error in the site I’m working on, but that was because I just installed the plugin Query Monitor, which redirects those errors to the firebug console:

"=== PHP Error in AJAX Response ===" query-monitor.js:157:4
10:05:53.125 Object { type: "strict", message: "Redefining already defined constructor for class ip_address_memory_usage", file: "/home/---/public_html/wp-content/plugins/server-ip-memory-usage/server-ip-memory-usage.php", line: 40, stack: Array[1], component: "Core" }

I checked that using Query Monitor plugin the error no longer conflicts with wpml setup. But if I disable it, reset & reactivate WPML and re-run its config wizard, the stopping error is still there. I made a screenshot of that moment. If I try to press the next button that page reloads again because of the error in your plugin. To continue I must either disable your plugin, or activate the Query Monitor one.

thank you very much for your time!

Hi there,

We just uploaded another version of the plugin that doesn’t use the __construct.

It’s version 1.0.3 that you can find here: v1.0.3.

This should fix the problem.

Please advice if it has solved the problem and works for you. Once you have tested and found ok, we will reléase it.

Thank you. Can confirm the new version works well in all the previous cases. Gracias

Thanks for the feedback. Gracias.