Undefined array key "processing" in Cleantalk\Common\Cron\Cron->checkTasks

Hello blainelang,

Please enable the "Collect debug data" option and send us the log when useful data appears there.

What kind of sensitive information is inside these logs? I see that the API key is in there - anything else I should remove before posting it?

I'll post the "cron_data" part (because this should be the concerning part) and leave out the sent key:

    "cron_data": {
        "cleantalk_cron": {
            "sfw_update": {
                "handler": "\\Drupal\\cleantalk\\CleantalkFuncs::apbct_sfw_update",
                "next_call": 1699951893,
                "period": 86400,
                "params": []
            },
            "sfw_send_logs": {
                "handler": "\\Drupal\\cleantalk\\CleantalkFuncs::apbct_sfw_send_logs",
                "next_call": 1699955433,
                "period": 3600,
                "params": []
            },
            "sfw_ac__clear_table": {
                "handler": "\\Drupal\\cleantalk\\CleantalkFuncs::apbct_sfw_ac__clear_table",
                "next_call": 1699955433,
                "period": 3600,
                "params": []
            },
            "sfw_update_checker": {
                "handler": "\\Cleantalk\\Common\\Firewall\\FirewallUpdater::apbctSfwUpdateChecker",
                "next_call": 1700124146,
                "period": 15,
                "params": [
                    "***APIKEY***"
                ]
            }
        },
        "cleantalk_cron_last_start": 1700124089
    },

no "processing" key in there - I guess this is only checked inside code, and as far as I see, it is only set to TRUE under certain circumstances, but never initialized with FALSE. But there is a check against this value, and that's why we get the warning

About API key, our fault, we will review and fix it. About the issue, we will contact you within 5 business days.

I'm seeing this as well.

chetan 11 → made their first commit to this issue’s fork.

Thank you @chetan 11, this seems to resolve the issue for me.

I'm looking forward to a version that fixes this error. I'm using CleanTalk 9.3.0 on Drupal 10.1.6.

haven't tried it, but checked the changes. That will fix it for sure, thanks!

I created a patch from the MR to be used with composer.

The patch in #13 works for me.

Just updated to 9.3.1 about 6 hours ago and still getting a "Warning: Undefined array key "processing" in Cleantalk..."type error. Was this version supposed to include the patch from #13?

Hello @OMD
Could you please send us the debug log as described above in this thread (please, do not forget to delete your API key from it) and then install the new version: https://www.drupal.org/project/cleantalk/releases/9.3.2 → ?

I think this has been fixed without an issue: https://git.drupalcode.org/project/cleantalk/-/blob/9.1.x/lib/Cleantalk/...

Commit message: "Fix. General. Compatibility with php7.4"
Commit: https://git.drupalcode.org/project/cleantalk/-/commit/512e5364103d28479f...

Approach is a bit different, but the condition in the IF and what is being set is the same in the end. So I think we can set this as fixed.