I’m searching, trying numerous ways… and I’m still not able to figure this one out. This is so simple… someone has to be able to give me something. lol
I’m making a maintenance page, when it’s turned on, my Navbar has a page load function that “should” activate when the setting is on, but it’s not working. Even when I switched the Only When like you had stated.
I think you need to place the condition into the workflow itself, not its first action.
So define a workflow “Do when condition is true” and put the “only when” condition in here. This will define when the workflow will get fired. And you put the got to page maintenance action into this without condition.
As for Telah, I have my settings on a different page that are connected to a list for the settings.
The toggler changes the options accordingly, so I must be doing something wrong with my logic haha.
Furthermore, the workflow is triggered from my websites main NavBar Resuable element. On Page Load… even tried When settings_systems's:first item's enabled is "yes" with constraint of "db_name = maint"
Just to get this clear:
You want to trigger the navigation action when two things happen: (1) a switch on your page is in a specific state, and (2) a certain data condition is given. Correct?
And your workflow is in the reusable element?
And the switch on your page outside the reusable element?
I have a separate page. It’s the admin settings page.
It’s linked to the list of settings. Has a toggler inside the list. The toggler sets the “data table” of system_setting (whichever one is listed) to enabled = true/false. The data reflects on the table.
I have a reusable element on the main pages, that has the workflow trigger you have seen above that I want to trigger When the setting Enabled is “yes”via Data.
Yes that should be not too complex indeed. I found the “Do when condition is true” workflow sometimes unreliable if relating to stuff that is not happening on the page. You can try the “Do every 5 seconds” thing instead. If that does not work either then the problem is somewhere else.
Yes. So you have user A who is flipping the switch and that should result in user B who is on another page (with the reusable element) to be sent to somewhere else, right?
In this case the browser on user B side needs to identify when to send the user to the other page, in other words needs to check against the server has the data changed or not on a regular basis.
Now you either do that manually (e.g. with a do every 5 seconds workflow using your search) or rely on Bubble maintaining the data relationship based on your search and checking automatically.
The latter did not work well for me if the data is not displayed on the page for user B.
I feel like it wouldn’t make sense to expose some things. Like should me even exposing that matter? The workflow happens in the backend, at least I thought.