We are rolling out a new Bubble version that will affect the way condition order is stored and rendered within your app.
We solved a bug within the Bubble editor where for an element that has a large list of conditions ordered in a specific way (via the move up/ move down buttons), adding a condition may sometimes mess up the preexisting order of the conditions list. That has been fixed with this change to ensure that the conditions order you set is respected and do not abruptly jump to a different order.
Why this matters:
For an element set up with distinct conditions that do not overlap, the order is mostly organizational. However, for an element that has competing conditions, where equivalent logical expressions are trying to set the same attribute in different ways, the condition lower down on the list will override the condition higher up on the list.
After you enable this version, if you had experienced the bug of jumpy conditions order, you will see that a condition that had previously jumped unintentionally to a different place on the list will be restored to the place where you had intended to put it. Furthermore, adding new conditions to a long list of conditions will no longer risk messing up the order that you had laid out for the elementâs conditions.
We are rolling out this change as a breaking version so that you have the chance to review any changes to the conditions list order that may have resulted from previously noticed or previously unnoticed order shifts. If you do notice that after updating to this version, conditions are set in an order that is unintended, you can always re-order them in the editor and expect that the lower down conditions will override any conflicting higher up conditions. The order you set will be stable and respected.
There are so many elements that have multiple conditions. How do we check all of them and how do we remember all of them as to what was the condition order that was intended?
Condition order will only actually matter if you have multiple conditions that set the same attribute under the same condition evaluation. For example, if you had a text element, with condition âWhen this text is hoveredâ, to set text to âHelloâ, and another further down the list, a condition âWhen this text is hoveredâ to set text to âWorldâ. Both will technically get applied, but the latter one will be the one that will be visible, the resulting text you will see on hover is âWorldâ. If you have any elements that carry conflicting conditions, that is where I would recommend you to review the order that is intended.
As a further note, this change is only really going to affect elements that have greater than 10 conditions. So that may help narrow down what youâd want to check.
For the most part, this change should be pretty mild. If you donât even quite remember what order you wanted your conditions to be, then itâs likely that the conditions were neutral to order and it likely shouldnât break anything for you to upgrade the version for your app.
canât download development version. we are downloading your app. new update announcement behind. It takes a lot of times and the page is stopping to loading. Tried 4 different browsers. My other app has the same issue. Pls help asap
I can no longer load the Bubble editor on development version. Freezing at âWeâre loading your appâ. The live version is also really buggy.
We need to find a better way of rolling out updates. This seems to be a recurring problem. A pretty mild change like this shouldnât be knocking out critical development infrastructure. If this is an ongoing risk due legacy tech debt, I would say itâs not even worth pushing out such minor updates at all.
Really sorry about the glitch, deployed a fix that should resolve that for apps unable to load directly due to BV15. For anyone who was unable to load, are you still facing that problem?
So just to clarify, if I create an object with 25 conditions, but only 1 condition can be a match (so organizational ordering) Iâm assuming Bubble will continue to check all the remaining conditionsâŚIs there a way to instruct Bubble to stop checking the remaining conditions for performance purposes (i.e. âdo until a condition is metâ), or would it not really have a noticeable impact on performance? (One of the projects Iâm working on has a page with several (10+) text objects, and eventually Iâm anticipating 25+ conditions per object, but kinda worried about performance)
On the topic of multi conditions elements, could you share a bit more about how performance is impacted by the number of conditions you have?
I have always tried minimise the number of conditions an element have to work though, generally avoiding more than 4-5 conditions. Sounds like this fix is for elements with more than 10 condisitons. What is the technical upper limit of the number and types of conditions an element can have?
@miri
One question/concern though. Why did you guys decide to have the order applied, be the reverse from everything else in the world? In your example of the âHelloâ and âWorldâ, if the condition to show âWorldâ is 2nd on the list, it gets applied first, this doesnât make sense for a natural flow.
In general normal reading, you read top to bottom. Even in programming, like java script, it executes the line of code from top to bottom. You guys are going against the grain here and the normal flow of things. Can we get this reversed so it executes/applies top to bottom?
I could be wrong, but I believe it is because you are setting CSS rules via bubble. CSS- cascades AKA the last applicable rule is the ones that gets applied
An update on this topic - in light of issues that users have reported due to this change we are temporarily disabling the effects of Bubble Version 15 until we iron out some of the kinks and make sure this change does not negatively affect anyone. As of right now, if you are on Bubble Version 15, it will behave the same as version 14. We will follow up soon once weâve fixed the issues and let you know when Bubble Version 15 is operational.
Sorry about the confusions here, and thanks for the patience!
