Thumbnails broken and JSON error

Hi @akateejay
Thanks for the extensive amount of debug info and screenshots. It really does help.

We are looking into this now. Could you please enable debug mode in FooGallery settings which will help us out.

thanks

We think it has something to do with the spaces in your image filenames.

We are looking into it more to figure out if we can cater for spaces and fix this bug

Awesome, thank you. I’ve enabled debug mode now. I’ll try later to redo this gallery with the spaces in the file names removed. If that solves the problem, that’ll be easy to deal with. Thank you for looking into it so quickly!

I tried it again with files that didn’t have a space and the same blank-page thing happened when creating the gallery, including the JSON error on the post page, but interestingly the thumbnails work now. FooGallery also gave me debug text when I added the gallery, not sure if that’s normal. This is the new page I made: https://www.virtual-dreams.org/photoroom/2021/01/06/austria-2012-2/

Preview Debug Arguments:
Array
(
[template] => justified
[attachment_ids] => 3356,3357,3355,3353,3352,3354,3348,3351,3350,3349,3345,3346,3347,3344,3342,3343,3339,3341,3340,3338,3334,3337,3336,3335,3333,3332,3331,3330,3329,3327,3328,3325,3326,3323,3324,3322,3321,3318,3319,3320,3317,3316,3315,3313,3314,3312,3311,3310,3309,3308,3307,3305,3306,3304,3302,3303,3299,3300,3301,3297,3296,3298,3294,3295,3293,3292,3290,3291,3287,3289,3288,3285,3286,3284,3283,3282,3280,3281,3277,3279,3276,3275,3274,3273,3272,3271,3270,3268,3269,3267,3265,3266,3263,3264,3261,3262,3258,3259,3260,3256,3257,3255,3254,3253,3252,3251,3250,3249,3248,3247,3246,3245,3244,3243,3242,3241,3240,3239,3237,3238,3236,3233,3234,3235,3232,3231,3230,3229,3228,3226,3227,3223,3224,3225,3221,3222,3220,3219,3218,3217,3216,3215,3214,3212,3213,3211,3210,3209,3207,3208,3205,3206,3204,3203,3202,3199,3201,3200,3198,3196,3195,3193,3192,3194,3191,3190,3189,3188
[preview] => 1
[thumb_height] => 280
[row_height] => 280
[max_row_height] => 150%
[margins] => 0
[lightbox] => foobox
[lastrow] => justify
[theme] => fg-light
[border_size] => fg-border-thin
[rounded_corners] =>
[drop_shadow] => fg-shadow-outline
[inner_shadow] =>
[loading_icon] => fg-loading-default
[loaded_effect] => fg-loaded-fade-in
[hover_effect_type] => normal
[caption_invert_color] =>
[hover_effect_color] =>
[hover_effect_scale] =>
[hover_effect_caption_visibility] =>
[hover_effect_transition] => fg-hover-fade
[hover_effect_icon] => fg-hover-zoom2
[caption_title_source] => none
[caption_desc_source] => none
[captions_limit_length] =>
[paging_type] => dots
[paging_size] => 60
[paging_position] => both
[paging_theme] => fg-light
[paging_scroll] => true
[paging_output] => html
[lazyload] =>
[datasource] =>
[datasource_value] =>
)

It is showing you all the extra debug info, because you are now in debug mode.

But I can see difference when viewing the new gallery : https://www.virtual-dreams.org/photoroom/2021/01/06/austria-2012-2/

All the images are now showing as expected, whereas the previous gallery https://www.virtual-dreams.org/photoroom/2021/01/06/austria-2012/ would not show all images.

I have a question about the filenames, as I tested it out by uploading a file with spaces, and WP does not allow it. The spaces are renamed to dashes. So how are you uploading images with spaces? Are you using a plugin to upload outside of the default media library?

Yes, indeed, I’m using a plugin that imports the files into the WordPress media library from FTP upload, which I have found is faster when managing large numbers of images and also lets me put the images in separate FTP folders that have meaningful names. But knowing about this issue now, I will make sure not to FTP upload any images with spaces in the file names.

The JSON error still appears for me in the WordPress post, though. Anything that can be done about that?

You’ll have to check what the WordPress save call is actually returning. To do this, you’ll have to view the actual call response in your browser’s developer tools.

For Chrome:
Right click anywhere on the page, then select “Inspect” or “Inspect Element” to bring up the browser’s developer tools.

Navigate to the “Network” tab of the developer tools

Click on “XHR” in order to view only ajax calls

Once you’re there, save your page in WordPress admin, then check the last of the newly added entries in the network tab.

Check the “Headers” tab of the new entry and you should see “/wp-json/…” in the “Request URL” to indicate that it’s a rest API call.

Check the “Response” tab, the contents of that may give a clue on what’s happening.

Hi @akateejay

We haven’t heard from you in a while, so we presume the problem has been resolved and we’re closing this support ticket.

If you are still experiencing the problem, then please open a new support ticket.

Regards,
Elvis.

Thanks for asking. I haven’t actually had time to do any more work on my online gallery, so I’m not sure if it’s fully resolved, but I’m happy for you to close the ticket. Thanks again for your help!