[New FREE plugin] Session & Local Storage (web storage API)

geraldons · 2020-09-26T19:04:01.784Z

The Same Occurring here with me. any solution to this problem?

vovahumnytskiy · 2020-09-27T07:28:40.352Z

I’ve used several WebStorages (1 webstorage for 1 value) and then when it was a time to use that value, then I used ‘:find & replace’ to delete the quotes.

jaguarconsultoriadig · 2020-10-05T00:42:32.675Z

Please do not understand the purpose and functionality of this plugin yet.
Could someone explain to me in a more simple and practical way?

thankful

Silvio Gregório

ken2 · 2021-07-30T15:16:48.812Z

I cannot, for the life of me, figure out how to retrieve the data stored in a session.

Is there any sort of tutorial instructions or video that I could take a look at?

Ken

miguel3 · 2021-08-02T11:48:47.852Z

I have the same problem as @ken2 . I have installed the plugin but I cannot not see the workflow actions under element actions in my app.

jacob8 · 2021-08-09T01:04:55.594Z

Hey, I’m using the Local Storage option for an API token also. I’m finding that when I close the browser and re-open it, the Local Storage wipes and doesn’t save the value. Doesn’t this defeat the purpose of Local Storage. I might as well be using Session storage. Wondering if you’re experiencing anything similar?

@Benji any thoughts on this?

Jacob

SebSchaeffer · 2021-08-22T12:39:48.925Z

I am getting this error when trying to clear web storage::

wailamara19 · 2021-12-09T13:45:35.736Z

i have the same problem as @mghatiya . i read all the blog but i figured out that no one has answered of this problem.
so please can some one told as why we didn’t get the actions of this plugin while we installed it
actions

plugs1920×809 47.6 KB

moabe.leite · 2022-01-30T03:22:04.424Z

Same issue here

keith · 2022-01-30T07:00:04.763Z

So, I take it folks would like a plugin for localStorage and sessionStorage that actually works? And that supports Things as well as primitive data types and Lists as well as scalars?

What’s it worth to you?

keith · 2022-02-07T01:46:07.527Z

Working on an actually useful localStorage plugin and read this plugin’s code just for yuks. It’s incredibly naïve and primitive.

It doesn’t know how to handle Things nor does it understand Lists (which we already know from comments above), but also only outputs the retrieved key value as text without JSON.parsing it. (The main interface has no type selector field so that’s all it could ever do. localStorage/sessionStorage can only hold strings (JSON.stringify’ed values), but of course we can restore them to their actual data types by parsing them properly.)

So, for the typical Bubbler, this plugin is less than useless.

aaronsheldon · 2022-02-07T05:12:53.823Z

Oh man, I just don’t see any graceful type-safe way of implementing this amount of polymorphism…even if client side actions could produce outputs. That’s not a complaint. I totally get how Bubble’s client side asynchronous implementation means client side actions cannot produce results.

In general the whole “interrogate an unknown thing to figure out what type to expect” seems to be some CS theoretical last bastion of human necessity. While everything else falls to the gods of AI, we all still seem to be writing a lot of code along the lines of “when X is run expect a result of type Y”

keith · 2022-02-07T05:20:13.841Z

I saw from another comment, @aaronsheldon, that you don’t think Bubble is strongly-typed. But it is.

In plugins, to use an output (and make its type dynamic)m we use the “App Type” editor selection type, like so:

image2664×222 14 KB

And now, in setting up an Exposed State (what I call an “output” because it’s easier to say/type/and understand), we can say:

image2678×236 24 KB

See?

aaronsheldon · 2022-02-07T05:21:14.379Z

I was being facetious.

keith · 2022-02-07T05:22:14.626Z

That is, the Bubble programmer must tell us what type of field we are to use.

So, even though we can have a plugin input that is “any thing”, we can never know how to publish that value, unless we ask the Bubble programmer what type it should be. It’s a minor limitation, but it can be annoying (for reasons I omit here at the moment).

aaronsheldon · 2022-02-07T05:23:33.434Z

Yup sorry for the confusion. That is exactly what I meant. Type navigation inevitably requires programmer input.

aaronsheldon · 2022-02-07T05:28:06.861Z

I have written some seriously messed up nested parameterized type methods in Julia. paramertized type paramertized by array type paramertized by number types paramertized by…" Generally resulting in a “I can’t believe that compiled and ran” moment.

aaronsheldon · 2022-02-07T05:42:05.805Z

Yeah I’ve mulled over implementing a plugin for local/session storage but the idea always makes my skin crawl. I think what really gets under my skin about using local/session storage in Bubble is that whatever use case a developer thinks they are solving with local/session storage it is probably better addressed with more native Bubble techniques. Such as custom states.

My take on the MDN documentation for local/session storage was that it was intended for building things like client side spreadsheets. So in the context of Bubble, a plugin developer would use it discretely behind the scenes to manage more complex semi-persistent state. A possible use case is a plugin that can “resume where you left off” on returning to the page after navigating around the app, i.e. unsaved (to the DB) data in a text editor (partial answers to quizzes and tests, maybe?). Or sinlgeton/monadic plugin elements where there can be multiple copies on the page but they all mirror each other via the local/session storage, rather than polluting the global/window object.

keith · 2022-02-07T06:47:37.550Z

Well, it’s most useful when you use it to store a complex object (think, an abandoned shopping cart). But it can be useful for just a single (scalar) value. Not a Bubble use case, but think of a page where the user submits some form and their email is the identifying key. And now, the page presents a second form and you don’t want the user to have to re-enter their email. So, you just save it to localStorage for when they return later. That’s a great use case for localStorage.

Similarly, localStorage could be used during a sign-in / onboarding workflow where you don’t want to bother saving (to the database) some values until the user completes the entire flow.

But making a (generally useful) Bubble plugin for any particular browser API is a pain in the butt as you have to consider all possible use cases (as much as you can) and accommodate them. This leads to rather large payloads even if some Bubble programmer is using the plugin in the most streamlined way.

It could also be useful as an alternative to passing values to some other page via querystring parameters. (What if the user simply never navigates to the next page? Their “saved” values are gone.)

It’s not very hard to do this, but the challenge is the UI for the Bubble programmer and providing useful feedback in the form of exposed states that are easy for the Bubble programmer to take action on. (My current draft of such a plugin is about 200 lines of [un-uglified/un-compled] JavaScript. Not bad.)

aaronsheldon · 2022-02-07T22:04:37.485Z

Yeah I can see it being useful for a multi-step reversible on-boarding/account creation wizard, where we only want to commit once all the validations have passed. Even then I would probably just bite the bullet and write an app specific custom plugin for exactly that purpose, likely using the non-persistent session storage, and with an “Account Creation” element containing states along the lines of “Step 1 Data”, “Step 2 Data”, etc… It would be a bit fluffed up in terms of a code base, but the control over the type coercion in and out of storage would be much tighter.