Monthly Community Update - August 2020

Exciting! Will this fix the issues with focus management when an input has currency or thousands separators? Super frustrating and meant a pretty significant rebuild of my app when I realized I couldn’t work around it.

My bug report that never got a response:

Other reports:

As an interim measure, is there any chance we could be given control over:

  • The wording of that message.
  • The color of the bar.
  • The color of the text.

That would at least give us some control over the UX so that it’s more consistent and/or appropriate for the app we’re developing.

Ok, given @rukevweb’s and @nomorecode’s reponses, there are obviously settings and/or work-arounds to achieve each of the things above. That’s great!

I believe the wording of the message is changeable in the language settings of your Bubble app.

I didn’t realize that. Thanks! It makes sense that it would be, but I never checked. :+1:

You can manipulate it @sudsy as seen here

Nice! Did you just use custom CSS/JS, or is there another app setting that I’ve overlooked?

And/or mate… but for simplicity I just pull the CSS tag on this occasion:

Custom 1

.bad-revision {
    padding: 30px 0 30px 0;
    font-family: "-System","Roboto",Verdana;
    font-size: 16px;
    background-color: #0E6EFD;
    font-weight: 400;
    color: #fff;
    position: fixed;
    text-align: center;
    top: 0px;
    width: 100%;
    z-index: 20000;
    line-height: 1;
    cursor: pointer;
}

Custom 2

.bad-revision {
    margin: 20px;
    padding: 30px 0 30px 0;
    font-family: "-System","Roboto",Verdana;
    font-size: 16px;
    background-color: #0E6EFD;
    font-weight: 400;
    color: #fff;
    position: fixed;
    text-align: center;
    top: 0px;
    width: 100%;
    z-index: 20000;
    line-height: 1;
    cursor: pointer;
    border-radius: 10px;
}

Custom 3 -pseudo /class

.bad-revision {
margin: 20px;
padding: 30px 0 30px 0;
font-family: “-System”,“Roboto”,Verdana;
font-size: 16px;
background-color: #6610F2;
font-weight: 400;
color: #fff;
position: fixed;
text-align: center;
top: 0px;
width: 100%;
z-index: 20000;
line-height: 1;
cursor: pointer;
border-radius: 10px;
}

.bad-revision:before {
content: “:v:”;
}

Obv you can adapt this to your colors, font, styling etc… enjoy :sunglasses::sunglasses::sunglasses:

This looks like a great solution in the meantime, thanks :sunglasses:

Thanks, @nomorecode. That’s what I suspected. It’s not exactly a no-code solution, but it works.

Never one content with the status quo, however, I’d like to make an even more ambitious request that would provide even greater flexibility…

Is there any chance Bubble could simply fire an event instead of showing that message at the top of the page?

That way, we could handle the situation in a completely customized and app-specific manner (even if such handling was restricted to client-side workflows). If no event handler is defined, the current behavior would be the default.

(Ah well, it’s worth a shot… :wink:)

I suppose you could do this using a “An element had an error running a workflow” workflow, as Bubble diagnoses page updates as “errors”, which is why they’re in the languages tab. The code for this “error” is BAD_REVISION.

quo was just a hackly ex. If you know flex and svgs then you can go crazy lol

Understood.

Going crazy is easy. Preserving sanity is what I’m after. :wink:

Not tried it yet mate but will explore further :nerd_face:

I also think there are plugins for this that allow you to replace the banner with images

plugins… meh

Not everything in the languages tab represents an error. Those are simply UI strings - some of which are error messages.

In any event (no pun intended), a Bubble native solution requiring no code and providing more flexibility would be welcome.

Gotcha :ok_man:

Now that would be too easy and make us all equal :sweat_smile: :rofl:

Thanks for the update @josh !

Regarding search logic - I’m wondering if there is any progress or plans to address this long awaited request to allow for “partial word searches”. Basically when my users search “pro”, I would like results containing the word “product” to show up. Right now there will be no results unless my users finish typing the whole word (which most users don’t do if they see no results) . Is this related to what you’re referring to as “fuzzy match”?

More context in this post: Searching Repeating Group with Wildcard - #23 by nomads32n

Hi @zenter,

We recently released the code improvement last week, and I just booted up a test app and could not reproduce the issues in the linked threads - could you please confirm if the issue still exists? Thank you.