• Resolved ecaron

    (@ecaron)


    We recently upgraded from 3.4.6 to 3.5.0. In our page editor, all our responsive hidden blocks are no longer editable in the main view. If we disable the .ghostkit-d-none class in style.css, the previous functionality returns (where the elements are semi-transparent, but accessible).

    Downgrading from 3.5.0 to 3.4.6 fixed the problem.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The new inline-css that WordPress has introduced is wiping out lots of Ghostkit styling on our sites. Ghostkit said that 5.0 introduced ‘improve assets loading to native way’, so maybe that has allowed WordPress to erase Ghostkit styling.

    Thread Starter ecaron

    (@ecaron)

    That’s a great point!

    I’m going to investigate if this issue – https://github.com/nk-crew/ghostkit/issues/226 – is related. I’ll follow-up here with what I find.

    Thread Starter ecaron

    (@ecaron)

    @urbansoul-design and @nk – No luck. I tracked down the other plugins using apiVersion 2 blocks and removed them, but the iframed editor still is doing the display: none thing (rather than just adjusting the opacity in the editor)

    Plugin Author nK

    (@nko)

    Hi guys,

    Thank you for letting us know. This issue has been resolved in v3.5.1. Please check again and let us know if you still experience any problems.

    Regards,
    Nikita.

    Thread Starter ecaron

    (@ecaron)

    We can confirm that v3.5.1 fixed it – thanks for the great work!

    Phew. So enqueueing isn’t always the best way. Thanks for fixing.

    Actually, this didn’t fix it for my client. I will start a different thread.

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

You must be logged in to reply to this topic.