Editor is embarrassing

[lizzie]

The editor is embarrassing currently. It is super slow. It creates errors and when you push something to live with new data fields, if you click live and go to edit these new fields, they won’t show unless you refresh.

I created a new data type, tried to add a new field and saw it added the field to the first thing in my data list which already had that field so now I had a duplicate and had to play Russian roulette on which was the duplicate to delete. I chose wrong so wasted time having to fix that up afterwards.

Why is the editor in such a ridiculously bad state at the moment ? It makes developing even harder and errors which are caused by the editor cost us time and WFUs… maybe it is on purpose.

[mikeloc]

No exaggeration here… this thread is at least the 15th new/active thread about the editor in the past 30 days, and I know that because I am a nut job who went and found all of those threads.

I know it’s probably frustrating when folks are asked/told to submit bug reports (and maybe you already did in this case), but those reports really are the way to get Bubble’s attention. That being said, I am going to drop a message to Bubble in the background and link to every one of those 15 threads so they have a better idea of how much this matter is affecting the community. Who knows, maybe that will help in some way, shape, or form.

[rico.trevisan]

Thank you for your service, Mike. 🫡

Back in the days – like a couple of months ago - I used to think I was the root cause of whatever problem I was facing. It has flipped now. Any sign of trouble and I open the console to see a red river of errors.

So sad. Soooo sad </trump voice>

[emmanuel]

Thank you for your patience here and very sorry for some of the recent issues - we did indeed push quite a few things lately in the editor to improve both performance and functionality, but it seems like some releases are leading to issues that have been reported here multiple times.

The team is investigating, and as @mikeloc is saying, the best you can do is submit a bug report with reproduction steps (or a copy paste of what is in the console, if you can’t reproduce). Our battery of tests (automated and manual) haven’t revealed the issues being reported on the forum, so the more we can look at this in details, the better.

Again, very sorry about this, we’re actively looking into this.
Emmanuel

[homegrown]

Yes i have noticed that in my single page app recently it is nearly impossible to get anything done as the editor constantly freezes and crashes.

Adding workflows / switching between pages in the editor, it will also crash when loading my single page app most times. It’s super weird.

I probably have to refresh from crash every 5 min. it’s nearly impossible to get anything done no joke!

[christo1]

My editor seems a lot snappier this morning (Australia time). Hopefully this is not my imagination as the last few weeks have been challenging to say the least even with issues_off=true

[cmendoza]

It is a lot snappier this time! I thought I was the only one

[mikeloc]

FYI… folks might want to give this new experimental feature a shot.

[Experimental Feature] Edit-mode performance enhancement

Hi all, We just released a new feature to the experimental settings panel. This feature is designed to help out editor performance for large pages containing lots of hidden elements. The way it works is by not rendering or allocating any memory for hidden elements in the editor, similar to what we do in runmode for elements not initially visible. In our performance testing, this has reduced memory usage drastically, especially for very large single-page apps - one page I was testing went down f…

[jmfcristo]

Thanks! The editor’s performance improved significantly.

[jonah.deleseleuc]

Many bugs… many, many bugs are still being observed. I’ve held back my complaints about the editor since WU’s came out since I thought they’d be ironed out at this point.

1. Here’s today’s latest example: Deleted API calls showing us a data source!

2. Error checking stopped working! After deleting API calls I know for a fact are being used, no errors show up, This isn’t the only thing either, I’ve seen other things that should cause errors not cause them

it’s been really hard to develop over the last few weeks. Performance down the drain, more bugs keep showing up

[jonah.deleseleuc]

3. Updating the names of API calls does not reflect in data source

[tylerboodman]

I think it has to be reinitialized after the rename

[jonah.deleseleuc]

I reinitialized it. Now, the same api call’s is showing up twice. Also, api call set as “action” showing up as a data source

[tylerboodman]

Lmao, yea I’ve had that before, no idea…

[jonah.deleseleuc]

The are two api calls, one is an action, the other is a data

[jonah.deleseleuc]

And there’s a bunch more. I can’t be expected to make a bug report for each one

Edit: More bugs

1. Unclickable condition expression after clearing one. Required refresh
   

[dorilama]

number 2 is happening since many months. Actions using a deleted API call are not flagged as issues and you can deploy to production with the errors

[chad]

I had so many issues today, I’ve been experiencing a lot of buggy editor behaviour but it’s been workable. Today when working with backend workflows the dropdowns to select data source and operators kept freezing and I had to refresh the page.
Pay more get less at this point

[jonah.deleseleuc]

As I develop throughout the day, I find more bugs that require refreshing every time.

Edit:

Another one