Bug: Visibility configuration (elements and pages)

[khalil.io]

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

SaaS

What are the exact steps to reproduce this issue?

A non-visible element overrides the visibility of subsequent visible elements. This occurs with elements configured with Visibility Logged-out visitors / Logged-in visitors.

1. Add a container.
2. Inside it, add a Heading.
3. Add a text element with the Visibility configured as: Logged-out visitors
4. Add a text element with the Visibility configured as: Logged-in visitors
5. Publish the application.
6. Enter credentials on the login page.
7. Go to the page with the configured containers.

The result: Only the Heading is displayed. The elements after the element with Visibility configured as: Logged-out visitors are not displayed.

Important:

• This occurs with published applications and not in Preview mode.
• It occurs within elements, columns, containers.
• When configuring page Visibility, it takes about 10 minutes for the content to appear and not all the content finishes appearing (the “Back” button is missing).

[picklepete]

Thank you for the bug report @khalil.io, we’ll investigate this ASAP!

Cheers,

Peter

[khalil.io]

Thank you very much @picklepete. In a few minutes I’ll share the zip with the application and database again, as I noticed some strange behavior with pages before and after logging in regarding visibility, and I can’t find the behavior pattern to report it clearly. The only thing I’m sure of is that in the application Preview everything works correctly compared to the Published application.

Screenshots

Application preview before logging in:

Published application before logging in:

Application preview after logging in:

Published application after logging in:

Application preview after logging in:

Published application after logging in: