Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Rafael Fischmann

    (@rfischmann)

    It looks like it was a conflict with perfmatters’ Remove Unused CSS feature. I’ve added “/instagram-feed/” as an exclusion and it now looks good.

    Plugin Support Smash Balloon Joel

    (@joelsmashballoon)

    Hey @rfischmann,

    Thank you for reaching out to us for assistance. We appreciate you bringing up the issue here and also what resolved it on your end. We try to be compatible with as much optimization as possible, however we do run into issues like this sometimes. We have also recently optimized our CSS further, and it may be that the optimizations on your end needed resetting or updating. ‘Remove unused CSS’ is a specific type of optimization that can often accidentally cause formatting issues, but it may simply need to be rebuilt with the updated plugin files.

    Let us know if you have any other thoughts or issues in the future.

    Many thanks,
    Joel

    Thread Starter Rafael Fischmann

    (@rfischmann)

    I’ll try clearing the Used CSS data instead of adding the plugin as an exclusion then, @joelsmashballoon! Thanks for the tip.

    Exactly the same is happening to me. I dont have the plugin “Perfmatters”

    It started in version 6.3. I had to go back to 6.2.10

    • This reply was modified 6 months, 2 weeks ago by walpap.
    Plugin Support Smash Balloon Joel

    (@joelsmashballoon)

    Hey @walpap,

    You may be running into a similar or separate issue here. The update causing the issue may be related to some CSS changes that we have done on our end to optimize the display of the feed. In some cases, custom CSS rules or specific theme rules will override CSS, or cause compatibility issues. I suggest taking a look at any custom CSS you are using, or if you are able, CSS in the theme.

    If you would like assistance with this please reach out using our support form where we would be happy to provide you with further assistance.

    Best regards,

    Just wanted to say thanks to @rfischmann for posting his fix, I had the exact same issue.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.