Skip Navigation

[Resolved] PHP Deprecated: Required parameter $params follows optional parameter $step in

This thread is resolved. Here is a description of the problem and solution.

Problem:

Deprecation notice in Module Manager

Solution:

Module Manager is a legacy plugin and if you do not want to migrate legacy module you will not need it.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

This topic contains 3 replies, has 2 voices.

Last updated by Christopher Amirian 9 months, 2 weeks ago.

Assisted by: Christopher Amirian.

Author
Posts
#2688207

HI Support

Our debug.log file is being flooded (!) with the following message:

PHP Deprecated: Required parameter $params follows optional parameter $step in /<redacted server info>/wp-content/plugins/toolset-module-manager/classes/ModuleManager.php on line 611

The message is being logged approx 2-7 times a minute! Please advise how this can be cured!

Thanks and kind regards
Simon

#2688231

Christopher Amirian
Supporter

Languages: English (English )

Hi Simon,

The info is a deprecation message mentioning that the update of PHP on the newer versions might have issues, but the current version works with no issues.

The Toolset Module Manager plugin is a legacy plugin, if you do not use it you can have it deactivated.

Thanks.

#2688232

Hi Christopher

We installed it way back, to create a Toolset Messaging system. For me it just looks like a group of Toolset objects bundled together, right?!

I would say that all the items in the module have probably since been modified. Is there any danger in deactivating the plugin, or would that disable our messaging system for users?!

Thanks and regards
Simon

#2688282

Christopher Amirian
Supporter

Languages: English (English )

Hi Simon,

As I am not sure what was the changes you would need to test, I suggest you test it on a staging version of the website.

If it has no issues then you can deactivate it.

Thanks

#2688330

Hi Christopher

Having re-read the documentation it would appear that the legacy Modules plugin was simply used to bundle objects to "copy and paste" them between sites.

I tested in dev and it appears to be working with the plugin deactivated. Have deactivated in production as well.

I don't think I need any more help here.

Thanks and kind regards
Simon