• conman

    (@normaldenker)


    I’m experiencing a critical conflict between this CTA plugin and Slider Revolution.

    Problem description:
    When the CTA plugin is active, Slider Revolution does not render correctly on the front page for non-logged-in visitors. Only the background (video or image) is visible, while all rows, images, and text layers are missing or not initialized.

    When logged in as an administrator, the slider often appears correct, which makes the issue harder to detect.

    Observed behavior:

    • Slider works correctly on a test subpage.
    • Slider breaks only on the front page when the CTA plugin is enabled.
    • Disabling the CTA plugin immediately fixes the issue.
    • No cache plugin is active.
    • Background video/image loads, but slider layers (rows, images, text) do not appear.
    • Issue occurs across browsers (including Safari).

    Likely cause:
    It appears that the CTA plugin applies CSS or JavaScript (e.g. transform, z-index, overlays, or DOM manipulation) that interferes with Slider Revolution’s layer rendering or initialization, especially on the front page.

    Environment:

    • WordPress 6.9
    • Slider Revolution (latest version)
    • CTA plugin enabled → issue occurs
    • CTA plugin disabled → slider works as expected

    Expected behavior:
    The CTA plugin should not interfere with third-party sliders or modify parent containers in a way that breaks positioning, z-index stacking, or JavaScript initialization.

    Please let me know if you need additional details, screenshots, or a minimal reproducible example.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter conman

    (@normaldenker)

    Update: Finally got it. CTA was “Sticky” what broke the site. I had to change to HTML INLINE … NO IT WORKS.

    Thread Starter conman

    (@normaldenker)

    The “Sticky CTA” template changes the DOM structure and wraps custom HTML content, which can break complex components like sliders or custom links. The UI does not make this behavior clear. A warning or restriction for custom HTML in this mode would prevent a lot of confusion.

    CLOSED.

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

You must be logged in to reply to this topic.