tiled-gallery.php line 424?

Thanks for the report! We’ll have a look at the problem.

Notice: Undefined offset: 3 in /<path>/wp-content/plugins/jetpack/modules/tiled-gallery/tiled-gallery.php on line 454

Notice: Trying to get property of non-object in /<path>/wp-content/plugins/jetpack/modules/tiled-gallery/tiled-gallery.php on line 454

this is the error I am getting on my jetpack install upon using tiled gallery. any help?

@ahmu83 Could you try to update to the latest version of Jetpack? I believe we fixed this issue in Jetpack 2.6.

Thanks!

I am running the latest version of jetpack but I am still getting that error. I tried deactivating, deleting and re-installing the plugin. Here is the shortcode for the gallery.

[gallery type="rectangular" link="file" ids="1153,1154,1155,1156,1157,1158,1159,1160,1161,1162,1163,1164"]

@ahmu83 Could you post a link to your gallery so I can have a look?
If you want it to remain private, you can also contact us via this contact form:
https://jetpack.me/contact-support/

here is the link to the gallery.

https://dev.pavilionsatpantanoapts.com/resident-reviews/

Thanks!

Do you see the notices for each one of the galleries you create? It might be worth trying to upload smaller pictures and create another gallery in another post. That could help us understand if the problem happens with each one of the images, or when something wrong happens during the image upload.

Let me know how it goes.

Thanks alot, that seems to fix the problem. I tried deleting the shortcode that is already there and replacing it with the new one. Thanks again ??

guess I was wrong. An image that is processed for tiled mosaic gallery seems to trigger the notice message.

Rearrange the images turn the notice message on and off. take a look at the following links.

https://dev.pavilionsatpantanoapts.com/resident-reviews/
https://dev.pavilionsatpantanoapts.com/resident-reviews-2/

the first order of images triggers the notice and the second one works fine.

Thanks for the extra details. We’ll take a closer look and try to reproduce.

In the meantime, I’m afraid I can only recommend that you set WP_DEBUG to false on your production site.