Getting Session Manager to Work with Layout and Content Page Design

[GraybeardCoder]

Continuing the discussion from AC session variable not available in AC Set Session picker:

@George

tried a few samples and it always worked for me in a content page or in full page.
Is you session manager defined in the content page or in the layout page?
Also is it on the top or nested somewhere? hope not in a modal or so

@George when you 'try a few samples', do your tests include putting session management in a layout page and trying to access it from a content page? What are the configuration requirements when NOT putting session manager in a content page, but using a layout page instead?

Please see my bug report from yesterday. I get the "empty list" when trying to access session manager variables where session manager is in layout and I need access to them from content.

[Teodor]

I just tested this locally.
Created a layout page, added a Session Storage Manager on it and defined a session:

Created a content page based on this layout page. Added a button and added an onclick event to it. I can see the Session Storage Manager and i can access its variables from this page on button click:

this is the latest Wappler 7 beta 22, but things haven't really changed here recently.

@GraybeardCoder

What are the configuration requirements when NOT putting session manager in a content page, but using a layout page instead?

No special requirements for this. It works as it is shown on my screenshots.

[GraybeardCoder]

I appreciate the response @Teodor . Do you have 6.8 to test this on since 6.8 is the current stable version?

I'm perfectly willing to accept that my configuration or usage is at fault. I would just like to figure out what's causing it not to work for me so I can admit it and move forward.

[Teodor]

Same test in Wappler 6.8

A new layout page created in Wappler 6.8 with the Session Storage Manager added:

A new content page created in Wappler 6.8 with button and an onclick event:

Same result, i can set the session values without any issues.

[GraybeardCoder]

Ok, thank you. Is there some configuration at the top level of my project that may be interfering with this working for me? Where should I be looking to figure out why it's not working with my application?

[Teodor]

The info about the components used on your layout pages is stored in a file called config.js located in public > dmxAppConnect folder. Maybe your config file got corrupted for some unknown reason:

Note: just inspect the file, please don't delete it.

[GraybeardCoder]

In my config.js, it doesn't show "sessionMgrMain" in main.ejs. It's been there for at least 6 months. The config.js file is showing the session manager I added this morning to viewpictures, which is what I've fallen back to using for the moment.

dmx.config({
  "customization": {
    "custPortal": {
      "meta": null,
      "outputType": "text"
    }
  },
  "yourprivacy": {
    "query": [
      {
        "type": "text",
        "name": "policy"
      }
    ]
  },
  "main": {},
  "viewvideosnew": {},
  "viewpictures": {
    "sessionStorage": [
      {
        "type": "text",
        "name": "oauth_callback_page"
      },
      {
        "type": "text",
        "name": "fb_oauth_initiator"
      }
    ]
  }
});

Here's my main.ejs file:

[Teodor]

So when you add a session storage manager on your layout page, does it get added there on save? Does your layout page has an ID added in the App ID?

[GraybeardCoder]

No, config.js is not getting updated when I add a new session manager to my layout page:

dmx.config({
  "customization": {
    "custPortal": {
      "meta": null,
      "outputType": "text"
    }
  },
  "yourprivacy": {
    "query": [
      {
        "type": "text",
        "name": "policy"
      }
    ]
  },
  "main": {},
  "viewvideosnew": {},
  "viewpictures": {
    "sessionStorage": [
      {
        "type": "text",
        "name": "oauth_callback_page"
      },
      {
        "type": "text",
        "name": "fb_oauth_initiator"
      }
    ]
  }
});

[GraybeardCoder]

Yes, layout page has an app ID

[Teodor]

Maybe try restarting Wappler with debug on, then open the layout page, add a session manager, define a variable and save the page.
Attach the debug log here so we can see if there are any errors in it.

How to report bugs together with the Wappler debug log

Updated for Wappler Version 5.0 and higher We have a built-in bug reporting in Wappler that auto post a topic in this forum together with the debug log. Starting from version 1.1.0 the logging isn’t available per default, so you need to restart Wappler with logging. You can do that by clicking on the Wappler’s tray icon (Windows right click) and then choose “Restart with Logging” Then reproduce your problem and choose to submit a bug report from the Wappler menu File / Submit error report … o…

[GraybeardCoder]

report1742482468016.zip (534.5 KB)

[GraybeardCoder]

I hope this is something that doesn't fall through the cracks...