Automattic / jetpack

Security, performance, marketing, and design tools — Jetpack is made by WordPress experts to make WP sites safer and faster, and help you grow your traffic.
https://jetpack.com/
Other
1.59k stars 798 forks source link

PHP Warning: Illegal string offset 'id' in grunion-contact-form.php:1288 #5810

Closed slaFFik closed 7 years ago

slaFFik commented 7 years ago

[06-Dec-2016 20:58:42 UTC] PHP Warning: Illegal string offset 'id' in /wp-content/plugins/jetpack/modules/contact-form/grunion-contact-form.php on line 1288 [06-Dec-2016 20:58:43 UTC] PHP Warning: Illegal string offset 'id' in /wp-content/plugins/jetpack/modules/contact-form/grunion-contact-form.php on line 1288

https://github.com/Automattic/jetpack/blob/master/modules/contact-form/grunion-contact-form.php#L1288

jeherve commented 7 years ago

I can't seem to reproduce on my end. Could you tell me more about your setup, as well the steps you follow to trigger that warning on your site?

slaFFik commented 7 years ago

The only thing I did - tried to upgrade to WordPress 4.7 (had some issues with Siteground and their SuperCacher, more details here: https://twitter.com/slaFFik/status/806231426085560320). Then visited several pages on front-end (including the one, that has the form).

jeherve commented 7 years ago

Do you still see the errors today? If so, could you try to deactivate each one of your plugins, starting with SuperCacher, and let me know if you find a conflicting plugin?

Thanks!

neo22s commented 7 years ago

Hello,

same issue here... disabled all plugins except woocommerce and jetpack. Still error :(

Warning: Illegal string offset 'id' /wp-content/plugins/jetpack/modules/contact-form/grunion-contact-form.php on line 1288

PHP 7.1

jeherve commented 7 years ago

Also reported here: https://wordpress.org/support/topic/contact-forms-in-4-4-2-not-working/

neo22s commented 7 years ago

Using contactform7...

jeherve commented 7 years ago

It appears the bug is limited to PHP 7.1. We'll see about including #6102 in Jetpack 4.5.1 to fix this.

jeherve commented 7 years ago

6106

jeherve commented 7 years ago

Fixed in #5821