Log Has Fatal Errors with Newsletter Plugin

[CollectiblesCat]

Hello. My website is at https://collectiblesandmoreinstore.com and I discovered today when reviewing the log that there are tons of fatal errors in connection with the Newsletter Plugin which say:

Critical Uncaught TypeError: Unsupported operand types: int – string in /home/collec26/public_html/wp-content/plugins/newsletter/includes/module.php:1090
Additional context
{
“error”: {
“type”: 1,
“file”: “/home/collec26/public_html/wp-content/plugins/newsletter/includes/module.php”,
“line”: 1090
},
“remote-logging”: true,
“backtrace”: [
“”,
“#0 /home/collec26/public_html/wp-content/plugins/newsletter/subscription/subscription.php(228): NewsletterModule::antibot_form_check()”,
“#1 /home/collec26/public_html/wp-includes/class-wp-hook.php(341): NewsletterSubscription->hook_newsletter_action()”,
“#2 /home/collec26/public_html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()”,
“#3 /home/collec26/public_html/wp-includes/plugin.php(522): WP_Hook->do_action()”,
“#4 /home/collec26/public_html/wp-content/plugins/newsletter/plugin.php(305): do_action()”,
“#5 /home/collec26/public_html/wp-content/plugins/newsletter/plugin.php(273): Newsletter->do_action()”,
“#6 /home/collec26/public_html/wp-includes/class-wp-hook.php(341): Newsletter->hook_wp_loaded()”,
“#7 /home/collec26/public_html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()”,
“#8 /home/collec26/public_html/wp-includes/plugin.php(522): WP_Hook->do_action()”,
“#9 /home/collec26/public_html/wp-settings.php(764): do_action()”,
“#10 /home/collec26/public_html/wp-config.php(105): require_once(‘/home/collec26/…’)”,
“#11 /home/collec26/public_html/wp-load.php(50): require_once(‘/home/collec26/…’)”,
“#12 /home/collec26/public_html/wp-blog-header.php(13): require_once(‘/home/collec26/…’)”,
“#13 /home/collec26/public_html/index.php(17): require(‘/home/collec26/…’)”,
“#14 {main}”,
“thrown”
]
}

How can this be fixed? Your assistance is appreciated.

[Stefano]

Hi, probably your PHP configuration has activated the “strict_type” mode, or a plugin is enabling it. Anyway, we’ll fix that in our code for the next release.

The strict_type option is not recommended right now, since some code written for PHP 7 could give that error.

[Author]

Posts