Connecting a Toggle to Visibility hides an element in the editor completely, regardless of the state.
In the frontend, the logic appears to be reversed. If enabled, it hides, if disabled, it is visible.
Connecting a Toggle to Visibility hides an element in the editor completely, regardless of the state.
In the frontend, the logic appears to be reversed. If enabled, it hides, if disabled, it is visible.
When the toggle is on, it returns “true”. So “hide element” is set to “true”, which leads to hiding the element on the frontend. It makes sense to me?
Hi Alan,
Thanks so much for your report!
We already received a report via ticket about this issue. It’ll be fixed in the next version.
Best regards,
timmse
That is true when think from a coder brain
From a UI for end users, the logic appears opposite.
So instead of labelling our Toggles to show elements, we need to label them to hide instead. Now the logic makes perfect sense
We’ve fixed this issue in Bricks 2.0, now available as a one-click update in your WordPress Dashboard.
Please take your time to read the changelog entry before updating: Bricks 2.0 Changelog – Bricks, and let us know if you continue to experience issues.