• Resolved jdrobertssff

    (@jdrobertssff)


    Hi guys,

    Awesome theme! I use FIFU to grab images from an external url so they don’t load on my site. It’s always played nice with Blocksy. I have version 1.8.36 and it’s fine – I don’t have auto-updates enabled in case of issues. I’ve just made a backup and tried to update to 1.8.38 but when I do the images do not appear on blog posts, archive pages, shop pages, anywhere basically. Do you have any idea what changes in version 1.8.37 or 1.8.38 may have caused this? Unfortunately, I don’t have 1.8.37 to check whether it’s 1.8.37 or 1.8.38 causing the problem, so I cannot narrow it down any further.

    Thanks
    John

Viewing 10 replies - 1 through 10 (of 10 total)
  • Hello @jdrobertssff

    Would you be able to post the website’s URL so we can check a few things out? Also, do you happen to run any optimisation plugins on this one?

    Thanks!

    Thread Starter jdrobertssff

    (@jdrobertssff)

    Hi Eduard,

    My site is https://www.blackdragonbooks.co.uk

    I use the SiteGround Optimizer plugin, which I have run since launch. I’ve had Blocksy and FIFU since launch too. I’ve had no problems for 9 months, it’s only when I update from 1.8.36 to 1.8.38.

    When I update no images show on the shop pages, reviews, news, etc. When I go into a single blog post or product the featured image only shows about 20px or so in height but full width.

    Thanks.
    John

    Hello @jdrobertssff

    Can you please try something? Can you update the theme to the latest version and temporarily disable the SiteGrounds plugin? If it does work after that, I’ll get back to you with more details.

    Thanks.

    Thread Starter jdrobertssff

    (@jdrobertssff)

    Will do. I’ll put the site in maintenance while I try it and roll back if it doesn’t work.

    Thread Starter jdrobertssff

    (@jdrobertssff)

    It works with SG Optimizer disabled. Strange as they’ve worked no problem for the past 9 months.

    Hey @jdrobertssff

    Alright, so this is the issue where these optimisation plugins haven’t been updated to support the latest WebPack features.

    Can you try excluding two files from being processed by site grounds?
    — /wp-content/themes/blocksy/static/bundle/main.min.css
    — /wp-content/themes/blocksy/static/bundle/main.js

    Let me know if this works better.

    Thanks!

    Thread Starter jdrobertssff

    (@jdrobertssff)

    Hey Eduard,

    So, in css, I cannot exclude the file as all .min files are already excluded from minification, but under js I was able to exclude the .js file. I have exluded both paths in caching and have the same error.

    What’s strange is I went to caching and disabled dynamic, file-based and memcached. I also disable minification on html, css, and js, and I disable lazy load, which are all of the featured I was using, so essentially the plugin should be ‘off” though not disabled and I still get the same issue.

    I also cleared the cache each time I made a change.

    Since you’re on SiteGround, is there any way you could create a staging version of the site with the theme updated, so we can take a look at exactly what’s happening? We’ve tried taking a look, but it seems we haven’t synchronised each other, because every time it was on the .36 version.

    Thanks.

    Thread Starter jdrobertssff

    (@jdrobertssff)

    I have to pop out for the day now but I’ll look into creating the staging site when I can. I’ve also created a ticket with SG that has been sent up the line to ask them to look into issues with SG Optimizer so I’ll keep you informed.

    That sounds like a good plan, @jdrobertssff! Please do keep us up to date, as we definitely want to get to the bottom of this.

    Have a good one!

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Issue wuith FIFU’ is closed to new replies.