PHP Warnings in debug.log

  • Resolved rruyter

    (@rruyter)


    4 months, 3 weeks ago

    Hello,

    I have the latest version of Jetpack as per today 20240705. In my debug.log file I am getting these PHP warning. Can that be fixed?

    PHP Warning: Attempt to read property “user_email” on bool in /xxx/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-forms/src/contact-form/class-contact-form.php on line 118

    PHP Warning: Attempt to read property “post_author” on int in /xxx/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-forms/src/contact-form/class-contact-form.php on line 117

    PHP Warning: Attempt to read property “ID” on int in /xxxx/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-forms/src/contact-form/class-contact-form.php on line 116

    PHP Warning: Attempt to read property “post_title” on int in /xxx/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-forms/src/contact-form/class-contact-form.php on line 100

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @rruyter,

    I’m sorry to hear about the trouble, but thanks for reaching out. The good news in looking at the PHP logs you reported is that you’re getting warnings, which are generally harmless as they’re not errors. this is a great place to start ??

    That said, I checked your Jetpack connection (which is working beautifully), and I seem to see that you’re not running the latest PHP version – I see version 8.0.30.

    Can you try updating the PHP version, clearing the site cache, and seeing how it goes? If nothing changes, we may need to check for any potential plugin conflict, as the PHP warnings are related to the Jetpack contact forms.

    Let’s take one thing at a time, and let’s see if the PHP update helps out. I recommend performing a site backup before doing the upgrade, to stay on the safe side.

    Let us know how it goes!

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hey @rruyter,

    Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

    Thread Starter rruyter

    (@rruyter)

    Sorry, no updates yet. I’ll keep php 8.3 running for a week and then will get back to you

    Thread Starter rruyter

    (@rruyter)

    I had to change it to 8.2 because of deprication warnings. Update still within a week

    Thread Starter rruyter

    (@rruyter)

    With php 8.2 the issue is still present.

    Plugin Support Ajay Kumar Jain (a11n)

    (@akumarjain)

    Hi @rruyter, As you mentioned, you see the warning messages in your logs with PHP 8.2, and when upgrading to PHP 8.3, you see deprecation warnings. Is that correct?

    I wonder if you have WP_DEBUG set to TRUE on your site. If so, could you change it to FALSE? Please let us know how it goes!

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hey there, @rruyter,

    Any other updates to share with us? As said, threads get closed after one week of inactivity, and we want to make sure we don’t if you still need help. Thanks!

    Thread Starter rruyter

    (@rruyter)

    Hi @erania-pinnera,

    Of course when I set WP_DEBUG to FALSE the messages aren’t shown anymore.

    I opened this thread to help you improve the quality of your product. I don’t think the issue functionally results in errors.

    I have done on my side what I can do to support you with investigating the issues.

    Let’s close this thread unresolved.

    Hi @rruyter,

    Thanks for the update and letting us know that the issue with PHP warnings on your website is now resolved.

    Let us know if you have any other questions.

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.