Notice: Undefined offset: 1

Thanks for the report! 2 other Jetpack users reported the same issue, and proposed a patch here:
https://plugins.trac.www.ads-software.com/ticket/1979

We’ll examine the patch and get this fixed in a future version of Jetpack. In the meantime, I’m afraid I can only recommend that you set the WP_DEBUG constant (#) to false on that site.

I’ll post again here as soon as the problem gets fixed.

Hai Jeremy,

You have everything documented very well, thumbs up!

But, to be honest, I don’t understand the English explenation there. Can you explain the problem in simple english for me, so I understand what is wrong here?

Because the problem started only after I installed WPML plugin, and removing WPML did not make it dissapear again. But with restoring it back to older database file, the problem is not there anymore…

So, I know it’s going to be fixed, and thank you for posting here when that is done, but I would really apreciate it when you can explain me in simple English what the problem actually is.

Thanks.

Before to edit the widget visibility, Jetpack first gathers a list of each widget area on your site, and the widgets that are included in each widget area.

When building that list, Jetpack assumes that each widget name is composed of a name, and a number at the end. Unfortunately, some plugins (like WPML, it seems), use a different name convention or edit the existing widget names. That’s what causing the notice when WP_DEBUG is set to true on your site.

I hope this clarifies things a bit.

Hi Jeremy, it is. Thanks.

The problem start when WPML want to include the ‘language-switch’ in one of the widget area’s.

I did not tried the patch from the ticket you mentioned, but for othere readers, this is what WPML said about it (also not tried yet):

Dear Willem,

I agree when you activate WPML, the warning appears, I think the code is not handled properly in /www/web2738/www.caesarsbeauty.nl/http/wp-content/plugins/jetpack/modules/widget-visibility/widget-conditions.php on line 251

To suppress the warning you can add ‘@’ to the variable
For ex.
1

@$a = 'some value';

I also have this error. And since the purpose of debug being on is to locate, see, and remove problematic plugins during developement, I’m not sure simply turning “off” debug is the answer.

This issue is months old. Is there no fix yet? What about that patch? Is it good? Where to copy it?

development site: https://worship101live.com

Is there no fix yet? What about that patch? Is it good? Where to copy it?

You can see the fix here: the red lines have to be removed, the green ones have to be added.
We’re still in the process of testing the fix, but we’ll add it to Jetpack as soon as it’s tested and if it doesn’t create any more bugs. Feel free to apply the patch to your development site and let us know how it goes!

Thanks!

Thank you for the very quick response. Seems to have worked…Though I still have much work to do. Thank you again Jeremy!!

My Jetpack pulls up a warning that shows on the front and backend. How to fix this issue ASAP? I have wordpress 4.0

Warning: Invalid argument supplied for foreach() in /home/content/p3pnexwpnas06_data02/35/2263335/html/wp-content/plugins/jetpack/modules/widget-visibility/widget-conditions.php on line 280

Jetpack version 3.1.1 installed. Cannot disable or uninstall because I’m running a plugin called comic-easel and it seems to only work when Jetpack is Enabled.

@lenity2 I replied in the other thread you started about this issue.