Workaround for Rules that use "This Thing's X's Y" can't grant search access right now limitation

Need help Database
1

Greetings, all. Really hitting a blocker with the current state of Privacy Rules and hoping someone out there has found a viable solution. I’m trying to create publicly accessible content, but the content is made up of multiple data types that are connected via parent-child relationships, and I can’t get the privacy rules to cooperate. I don’t have a User to attach these to as this content will be browsed anonymously.

Here is a sample:
Article
ID: 1 Title: An Intro to Bubble Publish State: Published
Content
ID: 1 Article: 1 Text: Overview
ID: 2 Article: 1 Text: This is the text that will appear in the article.

I need the logic to enable the Content data type to be viewed when the linked Article data type is published, but I keep getting the dreaded “This Thing’s X’s Y” can’t grant search access" error. I THOUGHT this could be solved by doing the search on the Article and then displaying a List of Content from the Article in an RG, but the “Search” limitation apparently impacts the display of items even if they aren’t being “searched.”

Any help would be greatly appreciated as I’m about at my wit’s end.

2

Could you not syncronize their published status via database triggers?

When Article state changes to published, do a search for its children and change their status to published, too?

3

This does sound like a Data Privacy issue

Go to Data → Privacy and select the ‘Content’ data type from the list on the left.
Then you should be able to see some details.
If you want this to be public, delete the rules there.

If you want it to be conditionally accessible, set the ‘default permissions’ as needed

screensh
screensh716×478 30.5 KB

Here’s an example of my setup

4

@rico.trevisan, thanks for the reply. That’s what I’m considering, but I was hoping there was an alternative as there are a number of additions types that will have to be updated too. :frowning:

5

crazy that Bubble still has not updated this. this is an issue from 2018

1 Like
6

@emmanuel alguma ideia de quando isso será resolvido?