🌎 Global States/Variables plugin by Zeroqode

[Ilinca]

This plugin is like a godsend when it comes to creating states. It is simple and light. It allows you to create list-type states and not only, and send a value from one reusable to another, or any other bubble element. The list-type states can be easily edited without thinking through Bubble logic, just indicate the state name and index value, that’s it. You are not limited in the number of states. Create, edit and use custom states in the elements or workflows to diversify and simplify the development experience.

Live demo: https://zeroqode-demo-28.bubbleapps.io/global_states_variables

DEMO & DOCUMENTATION

Global States/Variables | Plugin for Bubble by Zeroqode

SUPERCHARGE YOUR APP WITH ZEROQODE PLUGINS

No-Code App Plugins for Bubble | Zeroqode

Ilinca-Andreea Ceban
Executive Assistant @ Zeroqode

165+ Bubble Templates
35+ Bubble Courses
300+ Bubble Plugins
Convert Bubble app to iOS & Android
No-code Development Services

[user13]

Hello there,

It looks like a good way to do more with less effort and a smarter solution.
Is there more detailed information and documentation about how the plugin works?
Specifically, about how and where the global states are stored to be sent between elements.
We are concerned about what kind of information is recommended or not to be used in the global states, e.g., external database API settings or something like that.
And the demo doesn’t make it clear if, when changing the global state of one element, the other elements will have the same value. Is that so?

Thanks in advance!

[Gulce]

Hi there! @user13
Sorry for the late reply due to the weekend.

Unfortunately, we don’t have documentation for this plugin.

@user13

Specifically, about how and where the global states are stored to be sent between elements.
We are concerned about what kind of information is recommended or not to be used in the global states, e.g., external database API settings or something like that.

The data is stored locally in the browser, but it’s hidden and not accessible from the console.

@user13

when changing the global state of one element, the other elements will have the same value. Is that so?

Yes, if the value changes in the state, it’s updated in all elements where this state is used.

Please let me know if you have any further questions or concerns. I will be happy to assist.

Best regards,
Gulce

[parthapatel0723]

Hi! I just got this plugin. I have 0 idea how to set this up. I checked the demo but there is just so much going on, and I am honestly getting super frustrated. Hopefully, there is support available to help setup.

I am looking to save a State called “visible?” on a Mobile Menu. Whenever the mobile menu resuable element is on a page, I want to create the state on page load and by default set it to “no”. Now, when another reusable element on the same page, a button, is clicked, I want to change the variable to “yes”. It looks super confusing with field1, through like field10 and no ability to name each of the fields, how do I connect to the “visible” element?

Here is my test page where I have something setup in the backend though it does not work.

Eliminate email fatigue.

Would really appreciate help! Thanks.

[dorel]

Hello @parthapatel0723,

I apologize for any inconvenience you’ve experienced. I’ll do my best to assist you with your query.

@parthapatel0723

I am looking to save a State called “visible?” on a Mobile Menu. Whenever the mobile menu resuable element is on a page, I want to create the state on page load and by default set it to “no”. Now, when another reusable element on the same page, a button, is clicked, I want to change the variable to “yes”.

Here’s how you can achieve this:

1. Create your Mobile Menu reusable element if you haven’t already.

2. Inside the Mobile Menu reusable element, add a button or any element you prefer.

3. Create a custom state on the reusable element, let’s call it “VisibleCustom” and set its initial value to “no.”

4. Configure the button inside the reusable element to trigger an action that changes the custom state “VisibleCustom” to “yes” when pressed.

5. On the page where you want to use the Mobile Menu reusable element, add the reusable element but hide it initially. Add a button that will show the reusable element

6. Add the plugin’s element on the page and create a workflow that is triggered when the reusable element becomes visible. In this workflow, add an action using the “Create State” action from our plugin to create a state called “Visible?” with the value “no.”

7. Create another workflow that changes the “visible?” state from “no” to “yes” when the custom state “VisibleState” inside the reusable element is set to “yes.” You can use the “Edit State” action from our plugin for this purpose.

Screenshots.

This is how the functionality looks like :

Regarding your reference to “field1”, “field2”, “field3”, etc., these typically refer to the individual states or fields within the plugin’s element. For example, “field1” refers to the first state you’ve created in the “Create State” action.

I tried to access the provided link, but it seems to be unavailable to me. Could you please double-check that I have access to it

I hope this information helps you achieve your desired functionality. If you have any more questions or need further assistance, please feel free to reach out to us via the forum or directly at support@zeroqode.com.

Wishing you a great day ahead

[parthapatel0723]

Hey,

Thanks for your prompt reply. I ended up finding a solution outside of the plugin, but I plan to use it in the future as I definitely see the use. Notice how in your screenshots for Create and Edit state, you have a field called “Visible?” that then = something. On my end, I only have “field1” “field2” and so on. How do I name it “Visible?” for example, so I can stay organized.

[dorel]

Hi @parthapatel0723,

I’m delighted to hear that you’ve found a working solution that meets your needs!

Regarding the naming of the states, in the “create state” action, you can simply enter the desired name for the state in the provided field, as shown in the attached screenshot:

As for the fields having predefined names, it does seem unusual. Please ensure that you are using the latest version of the plugin and check if this behavior persists. If you encounter any further issues or have additional questions, please feel free to reach out.

Looking forward to your response!