The notice `Creation of dynamic property Cleantalk\Common\Firewall\Modules\Sfw::$set_cookies is deprecated` was fixed by getting changes to the common library https://github.com/CleanTalk/_sfw/commit/f4ba5b514c042786156d9152c100a2c... and these changes was loaded into the module code base
The notice `Creation of dynamic property Cleantalk\Custom\Db\Db::$db_result` was fixed by commit https://git.drupalcode.org/project/cleantalk/-/commit/837d2d8ae622f724ac...
We cannot merge these changes - your branch is much behind the target branch. We have implemented your suggestion by our commit https://git.drupalcode.org/project/cleantalk/-/commit/ff139b002089512603...
Thank you so much for this good suggestion!
So, undefined array key 'processing' was fixed -
https://www.drupal.org/project/cleantalk/issues/3401908
🐛
Undefined array key "processing" in Cleantalk\Common\Cron\Cron->checkTasks
Active
What about `undefined array key 'processing'` and other keys - we have changed the format for the cron tasks info store and these issues have appeared. However, the storage format comparison was implemented https://git.drupalcode.org/project/cleantalk/-/commit/8cd24663943c1cd84f...
For now, these issues should not occur anymore.
We have merged the MR https://git.drupalcode.org/project/cleantalk/-/merge_requests/24 contained patch in #13.
Thank you @cgoffin for the solution.
Thank you all for the best conversation!
glomberg → made their first commit to this issue’s fork.
We cannot merge these changes - the target branch does not exist else.
We have implemented your suggestion by our commit https://git.drupalcode.org/project/cleantalk/-/commit/6f4b6e44faf536a24f...
Thank you so much for this good suggestion!
We cannot merge these changes - your branch is much behind the target branch.
We have implemented your suggestion by our commit https://git.drupalcode.org/project/cleantalk/-/commit/2608d3880095845669...
Thank you so much for this good suggestion!
Hello @_kom__ ,
We need to debug these notices in the occurred hosts. We actually understand what sometimes it is impossible to you to give the administrative access to your website.
If it possible, just do some debug stuff what happening in line modules/cleantalk/src/EventSubscriber/BootSubscriber.php:176 (see the screenshot code.png) after the module updated.
This is the another way to fix the issue. Hope to your help!
Hello and thank you for delay!
We have added custom permission to manage CleanTalk settings.
Just apply a patch attached and grant selected user groups "Changing CleanTalk settings" permission.
Does this suit for you? Will waiting feedback from you.