Security Logout Error

A simple logout procedure that I've had working for years suddenly throws an error when I try to run the logout server connect.

I have a server connect like this:

<dmx-serverconnect id="logoutUser" url="/api/users/logout" noload="true" dmx-on:success="browserGlobal.reload()"></dmx-serverconnect>

I just have the security logout action in the server connect file.

You can see it's set to the correct security provider:

I am currently logged in and then I click the sign out link that runs the server connect and get the following error and I can't be logged out.

{
    "status": "500",
    "message": "Cannot read properties of null (reading '__dmxScope__')",
    "stack": "TypeError: Cannot read properties of null (reading '__dmxScope__')\n    at /opt/node_app/lib/core/parser.js:685:19\n    at /opt/node_app/lib/core/parser.js:697:21\n    at /opt/node_app/lib/core/parser.js:662:32\n    at || (/opt/node_app/lib/core/parser.js:66:39)\n    at /opt/node_app/lib/core/parser.js:424:42\n    at || (/opt/node_app/lib/core/parser.js:66:39)\n    at /opt/node_app/lib/core/parser.js:424:42\n    at || (/opt/node_app/lib/core/parser.js:66:39)\n    at /opt/node_app/lib/core/parser.js:424:42\n    at parser (/opt/node_app/lib/core/parser.js:359:19)"
}

I thought maybe it was a chrome issue so I tried safari but same error occurs.

I'm on Wappler 7.0.0 Beta 17. I just updated my docker desktop to the latest as well.

Any help from the team would be greatly appreciated.

-Twitch

Vaguely remeber seeing such errors in case of a curropt file upload. Not sure.
Try reuploading/rebuilding?

Thanks for the reply @sid. I'm in the local environment right now. I tried deleting the security logout and when I put it back it immediately showed the red exclamation and the red exclamation still remains even after I choose a security provider and save the file. And the same error occurs when trying to log out.

I may have to try deleting the security provider and then putting it back..... :unamused:

Ok finally figured out what was going on. I had some settings in the global file for access control using the current page, but there is no current page when running the logout server connect and that was causing the error. I added check for a current page and that stopped the error and I can now log out. Was driving me crazy....haha
So it's not a wappler issue, it's a not enough sleep and not enough coffee problem....lol

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.