Is this an issues with the local session manager - variables persist after Session Storage Manager removal?

[StevenM]

Hi

I want to add a local session to the content page which I have done.

On click of an icon I want to set the session to a specific value.

But I do not understand why when choosing to set the session it comes up with one of my global session variable names and nothing else?

I have no local session storage on the layout page or on the content page.

I create the session storage and assigned the variable.

I then try and set the session value but why am I getting only one of my global variables listed?

This is one of 5 global variables I have in my app, why is appearing here?
What am I doing wrong here?

[ben]

Will this help?
https://docsdev.wappler.io/guides/passing-values-between-your-pages

[StevenM]

OK worked this out and appears that variables created in a layout page session manager persist after you delete the Session Storage Manager from the layout page.

But would still like to know if this is what is supposed to happen?

Step A. Layout Page

1. Create a Session Storage Manager in the Layout page.
2. Add a variable to the session manager: “layout_variable”
3. Save

Step B. Content Page

1. Go to the content page (which uses the layout page in Step A.) and create a Session Storage Manager and add a variable: “content_variable”
2. On a content page element (an icon for example) Dynamic Events click action select the to “Set” the content page session manager.
3. In the “Name” drop down “Set Session Storage Item” list you see the layout page Session Storage Manager variable.

Step C. Remove the Layout Session Storage Manager

1. Go back to the layout page and remove the layout page Session Storage Manager.
2. Go back to the content page and repeat Step B. above and you will see the Variable for the removed Layout Page Session Storage Manager is still available.

It appears that you have to first remove the variable from the layout page Session Storage Manager first and then delete the layout page Session Storage Manager before it removes the session variable.

Is there a reason for this?

Thanks!

[StevenM]

HI @ben

Are you able to take a look at my last comment - I understand how to use the session variables but not sure why a layout variable still persist after removal? Any ideas?

[ben]

@StevenM

It appears that you have to first remove the variable from the layout page Session Storage Manager first and then delete the layout page Session Storage Manager before it removes the session variable.

That's the way that I have been using session variables.

I am not sure, but I believe that client side session variables are controlled by the browser. If you want to see the result of your code, click on the Application tab and view the Session Storage. In this example, I have used Local storage.

[StevenM]

Thanks @ben

That is very handy!!

[GraybeardCoder]

@StevenM

It appears that you have to first remove the variable from the layout page Session Storage Manager first and then delete the layout page Session Storage Manager before it removes the session variable.

It's 2025 and I can still confirm this is a bug.
I have a session manager in my layout page which I can't access its variables from my content page (yes, the content page is using the layout page)
I added a session manager to my content page, created "test" as a session variable.
Deleted the session manager, and I can see the "test" variable available from my layout page's session manager.
Only after adding session manager back to my content page and deleting "test", then deleting the content page session manager, did the "test" variable get removed.