Error message "Unsupported operand types" after installing plugin

Hi,

I do not get the error when I run the plugin on a multi-site network.

If you are using a custom Task Scheduler action module, can you temporarily disable it to see if the problem still occurs?

No, I have the error before installing an action module, out of the box after installing Task Scheduler.

I have tested the combination of Task Scheduler with Auto Post on another machine without any problems. Then I have installed both on my productive server and now I have this behaviour.

Hi,

What you say is unclear to me.

You say you get the error before installing an action module. But you also say it started to occur after installing the Auto Post action module.

Let’s clarify the situation.

Do you have an action module besides Auto Post? If so, what is it?

OK, sorry for that mismatch.

Answer to your last question: No, there is no installed module. I’m installing Task Scheduler and when I’m activating it my WordPress instance runs in that error message.

I have installed Task Scheduler and Auto Post earlier (!) on this instance and both ran without problems.

What I can do in a first step: Deleting any settings and options of Task Scheduler and Auto Post. Could you give a hint to identify settings of these Plugins in the options tables?

Did you modify the plugin options not via the plugin setting pages (Dashboard -> Task Scheduler -> Settings)?

If yes, delete a row named ts_option in the options table.

If no, can you tell me the steps to reproduce the error?

Ha… deletion of the row ts_option fixed it. Activation of Task Scheduler is now functioning. Maybe a thing for your plugin FAQ. ??

I haven’t modify the row manually. I have only installed Task Scheduler with Auto Post in an earlier stage of my website and deleted both plugins during development. I’m now productive and wanted to install the ensemble again but the installation of Task Scheduler failed with above error message.

Maybe a solution: An option to cleanup the ts_option during a deinstallation of the plugin for development purposes.

resolved.

Glad to hear it.

I really do not think it occurred naturally. There must have been some kind of manual modifications to the plugin options. Otherwise, it is almost impossible to get such an error.

I’ll make sure to implement a mechanism to clean up options upon plugin uninstall. Thanks for your suggestion.