Troubleshooting a publishing issue with a website

Both were ok yesterday, so something happened "today"

we need to see the failing one

https://bs2025-ot94g1.wstd.io or "internally" ?

can you post a share link or share in dm?

publish is going through fine, but production site has application error

can you hide things with show switch or eye button and get to the bottom of what's causing it?

most likely contenders are html embeds and resources making something bad

hmm, as far as i remember the only things I changed today were to hide (eye) two background images, let me try to show them back..

unlikely the issue

damn, I'm out of free published today.
i returned both these backgrounds, but cant check (

https://p-20350b74-1f1e-4539-949b-26f2a899405b.apps.webstudio.is/?authToken=59f9fc65-497d-41eb-b2df-fe4924770a4b&mode=design

here is a clone from my account

I recommend bisecting: turning half of the page off then another half until it works

It seems I have tracked it.
In Body / Content / Container / Grid:
"Nearest" has problem (unhide to return app.error after publishing)
"Latest" is fixed now

These both contain collection of some "events", every contain collection of "tags", and data source of inner collection is "broken":

It contains garbage instead of "collectionItem.tags"

now the question is how could we do better to show it in the builder, the info is there, just can't be seen easily

Is this some kind of syntax error that can be detected in design time? If yes - visual indication in Navigator, like red text color or small orange warning triangle at every item from root Body down to problem item may work as a very clear sign and pathway.

Also, specific property in right panel may also have same sign/indicator, for cases when problem is in component with many properties.

navigator wouldn't work always because you might not have the item open

I guess it needs to be in the top bar with a button to jump to the right navigator item

My idea was to bubble warning from problem item up to root. But dedicated button/list of problem items is good too.

@just_dmitry can you reproduce how you get this "garbage" variable in collection? This is definetely a bug though I don't have an idea how you get it. If you replace it with collectionItem the issue seems fixed.

Unfortunately, I can't.
I don't know what I did to make this happen - maybe some accidental keypresses, maybe "it itself". I didn't noticed when this happened.

Alright. We will add warnings and fix runtime failing at least

Reproduced the issue. Fixing