Hello,
A privacy rule conditional is satisfied, however the page hides the data anyways and it only starts working on page refresh or if any change is made to the privacy rule’s thing.
It is extremely weird because the database change can also be made from another page and the privacy rule suddenly realises that it shouldn’t be hiding the data.
If on the “page load” workflow i add a “refresh page” action, or a useless “make change to thing” action, it works. However both solutions feel quite suboptimal.
yeah i experienced the same issue. I reported it to bubble and they said its known behaviour, and you need to refresh the page.
I’ve found this only happens if you log the user in via a popup, or group on a page, then after login the user stays on the current page.
The strange thing is, some privacy rules do work, but some dont. Quite frustrating, especially as handling a ‘refresh page’ in terms of UI isn’t the greatest experience, unless it’s super quick.
In my case the user is already logged in when they load the page. They land on the page with an invite URL, which then ties the invite to the user and grants them privacy access to the page’s thing.
Its a bit of a convoluted workflow tbf.
I didnt go for the page-refresh option, i added a functionless date-time data field on the thing, and at the end of the workflow i just set it to current date-time. It fixes the issue and it doesnt require a slow page refresh.
