NO BUG: Bricks 2.0 Toggle Element Not Working

Bugs
1

Browser: Safari/Firefox/Chrome
OS: Tried on multiple Devices
URL: Parkerdentalstudio.com
Video: Short screen recording that illustrates this issue (free tool: jam.dev)

after the 2.0 update the Toggle Element is not opening my off cavas element. I have the CSS pointed at the off canvas in the toggle element

2

HI @V1kTri and welcome to the community :partying_face:

As for the issue, I can’t replicate it locally, and I still see that the toggle adds the brx-open class to the offcanvas, which is correct. But the the offcanvas doesn’t show becasue our style does not override the .brxe-offcanvas visibility:hidden.

CleanShot 2025-07-16 at 15.19.58@2x

Can you try those things:

  1. Disable all optimization and performance plugins and clear the cache (LiteSpeed for example)
  2. In Bricks settings, under the “Performance” tab, enable the Disable Bricks cascade layer (discouraged) toggle. If this works, please let us know, because this can only be temporary solution.

Do any of those solve the issue?
Matej

3

Disabling the Cascade Layer fixed the problem! What is the long term solution to fix this?

4

Perfect, thank you for checking it out. Then we need to identify the issue and then fix it.

Can you send temporary login credentials to your test/staging website and a link to this topic to help@bricksbuilder.io using the email address you used during the purchase so we can take a look?

Thank you,
Matej

5

I’m going to add my 2.0 issue here too because it seems to be related.

Off-canvas menu toggle isn’t showing up on mobile (should be triggered from tablet on down). Note, that it works on a resized Chrome window on desktop even if it’s mobile dimensions. You have to actually view it on a phone.

URL is https://stg-edifye-dev.kinsta.cloud/

Confirmed that disabling Cascade Layer fixes it.

This CSS seems to be the culprit -
.brxe-nav-nested .brxe-toggle {
display: none;
}

Thanks y’all. Excited for what I’m seeing in 2.0 so far!

6

Any word on the fix for this?

7

Hi,

we have not yet received the access to the @V1kTri staging website, but he is in touch with the dev team. Once we identify the issue and have more data on that, we will update this topic.

Best regards,
Matej

8

Hi @V1kTri,

Thank you for sharing access. Seems like this is an issue caused by Litespeed Cache (not sure if it’s tied to a specific setting). Disabling Litespeed Cache resolves the issue on your site (even with cascade layer enabled). Best to get in touch with their team so they can look into it but let me know if there’s something we can help with on our end.