SOLVED: Component Property allowed in dynamic data (Conditions)

Bugs
1

Currently, I can set component property in conditions (which would be an awesome feature btw). My property is a plain text field. I tried comparing it with “==” to text and sadly the condition is always evaluated to false.

1 Like
2

Hey,

thank you for your report. I replicated the issue, but just to confirm that it’s the same setup, can you take a screenshot of the condition?

Thanks.
Matej

3

Hi Justin,

We fixed this issue in Bricks 2.0 alpha, now available as a manual download in your account (see changelog).

Please let us know if you are still experiencing issues.

As with any pre-stable release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.

4

hello @timmse is it possible to install the fix on 1.12.4 stable?

5

No, unfortunately not.

6

I’m just adding that getting some kind of fix in 1x would be nice.

I have a header component where I thought the user could have properties where they turn features off and on and then I can use conditions to hide those things based on the properties.

Then the whole thing fell apart since we can’t reference properties from conditions.

I don’t know why this is difficult to add. When I put in a condition, it literally lets me select properties as the field to test against, there is a little “+” sign to inject the property. So it can do that, but it can’t just read the property to check the value even though I can select the dynamic data field as part of the condition?
In other words, Bricks lets me choose the dynamic field as if I could test against it, but it can’t. This is misleading feature that feels like a bug. Why would it let me choose the dynamic field to test against if it’s just going to treat it as false in all cases?

test property values

Maybe there is some other purpose for the dynamic data to be selected here??

7

Hi @vigilante,

this works in 2.0 versions, so once you will update, it will work. There will be no fix for 1.12.X version.

Best regards,
Matej

8

When does 2x release for production use? And are there any breaking changes we should think about?

9

Hi @vigilante,

there will be another release before stable one, then based on an additional bugs found. I can’t give you timing though.

As for breaking changes, there were some in alpha:

  • Cascade layers enabled by default
  • Deprecation of global elements.

But check all three changelog, to see what changed:

Best regards,
Matej