Beta 6 "broke" one of my sites (cache clear fixed it)

Beta
#1

Just an FYI. Updated to Beta 6 on one of my sites, and every page started giving me this (whether they were created with a previous beta, or prior production build):

It went back to normal with a cache clear.

I’m assuming it’s because you changed something in the builder code that had been cached, and this might not affect users in the regular launch. But just sharing so you’re aware, because it scared the $h!* out of me for a minute. (I was living dangerously, and had created a new page on a staging site that I wanted to eventually use on a production site… but hadn’t exported it yet :grimacing:)

#2

Were you seeing that on the front end at all? Or just in the builder? Just wanted to confirm. If it was only the builders we should be in the clear. If that was on the front end at all there are some things I’d want to look at more closely. The symbol using to be {{children}} but I added the %% characters to make it more distinct and less likely to clash with the new {{max}} and {{rating}}` directives added with the countdown element. In general it’s probably better we use something less like a popular template system for our internals.

#3

Unfortunately, I can’t tell you with any certainty.

I tried to load the front end, but it wouldn’t load at all. However, afterwards I discovered a separate issue where my staging environment will not load my homepage. And unfortunately, I don’t remember whether I clicked the pop out preview button from the builder, or whether I typed in the homepage directly.

#4

That’s ok. Thanks for letting me know. I’ll keep an eye out for anything like this. This is definitely something that would happen if you’re running the latest code PHP side with the previous javascript - so it’s most likely just a matter of the new scripts not kicking in until the cache was cleared.

#5

:thumbsup: