I didn’t have to go very deep to see the problem reproducing from a blank slate. Here’s a video showing my set up:
And I’ve confirmed I have both slugs and usernames set to everyone being able to view them in privacy settings.
Turn that text field to “current page user username” if that doesn’t work, it’s 100% privacy rules on the user level.
1 Like
Only chiming in here because the new responsive engine makes this a bit complex: Yeah the chain of parents can get a little complex when you might arbitrarily add new rows, columns, or groups on new responsive. This used to be more doofus-proof. BUT, if you have a need to reference some state, just look for the highest level state you can possibly see. For example, the page’s something. You don’t have to be lazy and just look at “parent’s something”.
Alternatively, put frequently-referenced data in a custom state on the page (or anywhere, really) on page load, and just reference that.
None of this is complicated. Bubble just wants you to think it’s complicated.
You were correct about privacy settings, just not in the way I expected. I was checking that the right data fields were checked off as “everyone else” can “view all fields.”
What made the difference was adding "find this in searches."
The layout and naming of data rules in Bubble just isn’t helping in terms of clarity, but it’s working now so thank you!
2 Likes
This topic was automatically closed after 70 days. New replies are no longer allowed.