PHP Warning message started upon implementation of v1.2.5

  • Resolved Mike Price

    (@fairfieldphoto)


    4 years, 1 month ago

    I updated this plug-in from 1.2.4.1 to 1.2.5 on 27 January 2021. Shortly after the update, I started getting the following error message clusters repeatedly in my server logs:

    [27-Jan-2021 20:54:05 UTC] PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, cannot access private method kmcf7_message_filter\CF7MessageFilter::add_custom_messages() in /home/fairfiel/public_html/wp-includes/class-wp-hook.php on line 287
    [27-Jan-2021 20:54:05 UTC] PHP Warning: array_merge(): Expected parameter 1 to be an array, null given in /home/fairfiel/public_html/wp-content/plugins/contact-form-7/modules/date.php on line 152
    [27-Jan-2021 20:54:05 UTC] PHP Warning: array_merge(): Expected parameter 1 to be an array, null given in /home/fairfiel/public_html/wp-content/plugins/contact-form-7/modules/file.php on line 207
    [27-Jan-2021 20:54:05 UTC] PHP Warning: array_merge(): Expected parameter 1 to be an array, null given in /home/fairfiel/public_html/wp-content/plugins/contact-form-7/modules/number.php on line 144
    [27-Jan-2021 20:54:05 UTC] PHP Warning: array_merge(): Expected parameter 1 to be an array, null given in /home/fairfiel/public_html/wp-content/plugins/contact-form-7/modules/quiz.php on line 193
    [27-Jan-2021 20:54:05 UTC] PHP Warning: array_merge(): Expected parameter 1 to be an array, null given in /home/fairfiel/public_html/wp-content/plugins/contact-form-7/modules/really-simple-captcha.php on line 237
    [27-Jan-2021 20:54:05 UTC] PHP Warning: array_merge(): Expected parameter 1 to be an array, null given in /home/fairfiel/public_html/wp-content/plugins/contact-form-7/modules/text.php on line 204
    [27-Jan-2021 20:54:05 UTC] PHP Warning: Invalid argument supplied for foreach() in /home/fairfiel/public_html/wp-content/plugins/contact-form-7/includes/contact-form.php on line 885

    The timing of the first occurrence of this matches the timing of the plug-in update to 1.2.5.

    How do I correct this?

    -Mike

Viewing 5 replies - 16 through 20 (of 20 total)
  • Thread Starter Mike Price

    (@fairfieldphoto)

    What I can confirm is that with 1.2.5.1, I am no longer getting the server log error messages. Blocked messages are still blocked, but not causing server errors in the process.

    I can also confirm that the word “online” is not being caught as part of the filter. I have used “.online” and “online” and I am still getting messages through that use a TLD of .online similar to the example I sent you via email.

    The “online” filter issue is a different issue from the server log error messages. Should we start a separate thread for that issue?

    Plugin Author kofimokome

    (@kofimokome)

    I want to be sure if the blocked messages page shows all the recent messages blocked.
    Yes, please. Let’s start a new thread for the online and .online issue

    Thread Starter Mike Price

    (@fairfieldphoto)

    yes, I checked the “blocked message” section and I see several messages blocked from earlier today. Thank you.

    Plugin Author kofimokome

    (@kofimokome)

    ok. one last question.
    Is the new settings page easier to use or do you prefer the way it was before?
    Before, there were no tabs. Now, Similar settings are grouped under a tab

    Thread Starter Mike Price

    (@fairfieldphoto)

    I had the original plug-in installation and configuration done by my web developer. I have just been making the adjustments to the words to be screened out. I do not remember what the previous version looked like, but I am fine with how the current settings options are presented. I don’t see a reason to go back.

    -M

Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘PHP Warning message started upon implementation of v1.2.5’ is closed to new replies.