NO BUG: Builder is not saved after logout

Bugs
1

Browser: Chrome 137.0.7151.104
OS: Windows

Hi team,

If we are in the builder and for some reason we are logged out in another tab, the builder will not save and will display an error until we reload it. If you try the same scenario in Gutenberg, there will be no problem saving.

Please watch the video below.

2

Hi Hosein,
Thanks so much for your report!

I’m not quite sure how this is related to custom auth pages :thinking:
However, I don’t see a bug. If I have two tabs open in parallel (Gutenberg post and WP Dashboard) and log out, I am prompted with the WP login screen, so I can’t save before logging back in and reloading.

image
image1920×1087 79.4 KB

Best regards,
timmse

3

Hi Timmse,

I’m not quite sure how this is related to custom auth pages :thinking:

Yes, you are right. I confused this with another similar report I published at the same time. So Custom auth pages has nothing to do with it.

so I can’t save before logging back in and reloading.

That’s exactly the point. In Gutenberg, there’s no need to reload. You can save immediately after logging in. But in Bricks, you get an error And it is not possible to save until the builder is reloaded.

4

For Matej and me, there is a need to reload. That’s what I intially said:

I’m not sure why it’s different for you, since the reload has always been required as far as I know :thinking: