Hi everyone, We’re excited to share that we will be improving runmode performance of your Bubble apps with our wide release update for the new elements rendering feature . This feature was originally on our experimental features panel, but we are now releasing it to everyone later today as Bubble Version 21, which you can upgrade to in the Settings > Versions tab. This feature uses a more optimal rendering pipeline to improve runmode performance of your apps. More specifically, we no longer add a canvas for invisible elements on page load, whereas before we would still have a canvas even when it wasn’t loaded. This should only break if there’s any plugins or custom code that rely on this functionality. If you are using this feature from the experimental feature panel already, you should still upgrade to the new version. We are not removing the feature, so your apps won’t downgrade before you get the chance to upgrade, but we are deprecating the experimental feature, meaning it will only be available for apps that have used it in the past, and will be removed for apps that never used it. Please let us know if you have any questions!

Hi rushi - do you mind checking to see if your app is back to working as expected? The team just rolled out a fix for a regression that was unrelated to this new Bubble Version [image] [Upgrade to Bubble Version 21] Improved Runtime Performance Announcements @guarav Sorry about that! @dorilama you are correct, this was caused by a recent fix that went out this morning to color fields in custom plugins. A fix for this empty color field messing up plugin rendering issue has just been rolled out, so it should be working as expected now!

@nick.carroll Add the Heroicons plugin to the list of broken plugins. Every one of our buttons is horked on build 21. I’ve already alerted @Kayami. Was there documentation released by the product team to plugin authors before this was released? I just got an upcoming updates doc from Microsoft to prevent a similar issue from occurring in their ecosystem with our code.

Confirming that the probability of this Bubble Version causing issues in an application that has not upgraded to it is about as close to 0 as possible.

In my experience, a calmer, more streamlined approach than this is more effective in sparking action by the Bubble team.

[image] gaurav: I also think bubble should explicitly make it clear to users that (1) Bubble rolls out minor changes to live apps regardless of version (2) Plugin developers can’t randomly push code into client apps in reality. Code changes occur only when clients update a plugin version from their bubble app → plugins tab. While I’m sure we’ll never be able to properly educate Bubble users about your very cogent point #2, @gaurav, plugin users (many of whom I see affected by the color default issue today) should be advised of the following: If a plugin just “breaks” suddenly in an existing page and you haven’t upgraded it nor attempted to use some new functionality in it, then the malfunction is due to some change in Bubble. Your first stop should be filing a Bubble bug report and then pinging the plugin dev for assistance. (Also, you can open your console to see what error(s) are being thrown. Not that this is informative to you, but it’s informative to Bubble.) In the case of my experience with this today, I was only able to check out what was happening right as Bubble was already fixing the problem and so it went away even before I could do a screenshot for my own bug report.

@nick.carroll it wasn’t version 21 but an error in a bugfix Bubble had rolled out in color picker: [image] Plugin Elements failing when color-fields are unconfigured (fixed as of 21:40 UTC) Bugs Just a heads up - Over the past few hours i received a few e-mails from plugin-users having issues with their applications. Basically they complain about specific widgets not being rendered at all. It turned out to be caused by unconfigured color fields (even though they are Optional). I figured i should share the heads-up in this forum. Here’s what to look for when you encounter failing elements: [image] The workaround solution would be to configure the “empty” color-values. For the code-…

Hi @mghatiya - lets take a step back so I can try to better understand your concern. The “non-backwards compatible” change this version introduces is that elements that are set to be invisible on page load will not have a div on the page until they become visible. This means that any custom code (including a plugin) that tries to reference that hidden element on page load before it is made visible, may not behave as expected. I say may because it depends on how the code is written. Now, it is nearly impossible to tell just by looking at the code whether or not a plugin/custom code would break or not, so the guidance is to keep an eye out for any plugin or code that references a specific element’s custom id and test to see if the app behaves as expected with the Bubble version turned on. If there is an issue, then the guidance is to adjust the custom code or notify the plugin developer or file a bug report with the team and not deploy any updates to Live on that bubble version until the issue is resolved (as is the nature with any Bubble version). In your case, custom css that is applied to an element via its custom id should not cause any issues, but please do report any unexpected behavior you may see or use cases in your app that you are concerned about. I hope this helps.

Noted, thanks @treb.gatte. No, plugin authors were not made aware of this change before the Bubble version was released. This was an oversight by our team that we will rectify. For what its worth, our team is currently in the process of creating better documentation on our plugin editor api so (1) what is possible / not possible is known and (2) when we do need to issue a breaking change to the plugin api, we can properly notify plugin authors.

Comments like the below are a little infuriating. It is only custom code/plugins that may have different behavior since we have no control over those. Of course you don’t have control over the code of the plugins, but you certainly have control over breaking them. So bubble should 100% be reviewing common plugins for damaging issues prior to releasing code. Get a group of testers, we will test free of charge for credits or something. But bubble needs to stop acting like their updates don’t have implications, and they need to work with the community.

Understood, thanks for clarifying. So in all fairness, we did review and address the 100s of bug reports and pieces of feedback that came in during the time when this update was an experimental feature, and we did do testing with commonly used plugins (for example, the drag and drop plugin). I think our misstep in releasing this bubble version was not giving plugin authors a heads up about the change to give them time to make updates to their plugins before GA (which we will rectify asap). That being said, you are definitely correct that we have a long way to go in terms of improving the reliability of our releases. In this case, the buggy release was a bug fix from earlier today, but the point stands. fwiw, we are hiring team members that will focus their time on this exact issue - and I do like your idea about crowdsourcing testing…

[Upgrade to Bubble Version 21] Improved Runtime Performance

Announcements

keith January 10, 2023, 10:05pm 44

@nick.carroll it wasn’t version 21 but an error in a bugfix Bubble had rolled out in color picker:

Topic		Replies	Views
Monthly Community Update - August 2020 Announcements	61	8337	August 19, 2020
Monthly Community Update -- May 2022 Announcements	25	5176	May 10, 2022
New Experimental Performance Enhancements New features	59	7256	September 28, 2022
Monthly Community Update -- July 2023 Announcements	30	10832	August 5, 2023
Monthly Community Update -- December 2021 Announcements	27	6559	March 18, 2023

[Upgrade to Bubble Version 21] Improved Runtime Performance

Related topics