Page Header Not Showing up

[keith]

@boston85719

Neither expression is available in the page header section by default and had been copied and pasted into the header area. By removing them, the page html header is now coming through.

How many times have I noted that this is bad practice, as noted by Bubble? Lots.

http://forum.bubble.io/t/so-this-is-messed-up-and-cool-at-the-same-time/270670/2?u=keith

Changing "and" to "or" in a Condition - Now Need to Re-Enter Condition

It was noted by @josh that doing this trick (copying an expression and pasting it to a place that would NOT let you construct that same expression) is unsupported behavior and subject to breakage. I had mused about this here: And Josh explains why this is a no-no here: I know this isn’t helpful to you now, @antony , but wanted to point this out to other intermediate to advanced Bubblers as a warning.

Memory Issues: What Data is Loaded when a Page Element has a Type?

Yeah: couple of observations: The issue with page level privacy is the interface simply isn’t designed to enable that. You can craft these expressions (somewhere else) and paste them, but then ANY condition that passes unlocks a permitted value so you wind up with some very wonky expressions (and lots of them to cover all the cases). Implicit OR having to be worked around! Not a good approach. (Though it DOES prohibit data loading… so it’s an option, but a fragile one.) it’s fairly easy to tes…

Showing alert message when another element is focused

Just an aside: There are other expressions like this that can be composed in one place but not in another. While in this case this looks like a bug to me, Bubble has said of other such expressions that if you can build it in one place but not in another, this “build there, paste here” is fragile and subject to breaking at any time (presumably because they really don’t support the thing you’re trying to do and may fix the “bug” that allows it). FYI!

Assigning Concatenated Values to a State

Total aside which may or may not be relevant here: @josh has noted that situations where you can do this (compose an expression somewhere and paste that expression in a field where such expressions CANNOT normally be composed), but there MAY he good reasons that such functionality is not supported in the target field. (And, this workaround or hack MAY be prone to being “fixed”, so it’s potentially fragile.)

Do arithmetic for items from # selection

Ah! Ummm… I think I accidentally stumbled upon a workaround for that recently. (But I need to research to re-uncover what that was…) However, the “non-hacky” workaround is this: Presumably, API Workflows don’t need custom states as they have the database (perma-storage). So, in the workflow, you can create a new thing (of whatever type you need) and reference its unique ID (via “results of”) to delete it when done with it. Obviously this slows things down over temporary (in-memory) storage, b…

I’m sure there are more, but I’m tired of pasting.