Workaround for bug in v. 1.6.18

  • ResolvedModerator Kathryn Presner

    (@zoonini)


    1 year, 3 months ago

    Hi folks, just wanted to share something that users on WordPress.com have tried that seems to help mitigate the stray CSS code appearing on the front end in the latest version of this plugin – without a rollback to a previous version:

    Deactivate?Improve CSS Loading?from?Elementor > Settings > Features.

    It may or may not work for you, but something to try.

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

  • It worked for me! Thank you so much

    Moderator Kathryn Presner

    (@zoonini)

    @manuelecheandia So glad it worked for you!

    Not working for me.

    Weronika

    (@wmasztakowska)

    Hi, have the same problem and solution you gave doesn’t work. When this will be fixed. Plus how to come back to the previous verison of the plug in?

    • This reply was modified 1 year, 3 months ago by Weronika.
    Moderator Kathryn Presner

    (@zoonini)

    @wmasztakowska – I’m not involved with the plugin’s development at all, just sharing a workaround that worked for some other folks. You’ll need to wait for a reply from the plugin developers regarding a fix.

    As for rolling back to an older version, I’d suggest you start a separate thread/topic for that where folks can walk you through it.

    Dang, thanks for the suggestion but it didn’t work for me…

    this works but not 100%

    in my case Icons on “icon list” do not show, on footer and neither the “social media block” works correctly.

    Plugin Support Herman Asrori (BSF)

    (@bsfherman)

    Hi @zoonini, thanks for sharing the workaround.

    We apologize for any inconvenience caused. This issue has been resolved in version 1.6.19. Additionally, we have released a couple of updates for other bug fixes. If you haven’t already, please update the plugin to the latest version, which is currently v1.6.21, and you should be good to go.

    Since this issue has been resolved, I am marking this thread as ‘Resolved’.

    Kind regards,
    Herman ??

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Workaround for bug in v. 1.6.18’ is closed to new replies.