Wappler Version : 5.8.2 (stable channel)
Operating System : w10
Server Model: php
Database Type: mysql
Hosting Type: localhost (php 7.0.2) / custom hosting (8.1.21)
I can’t attach any version of the modules, but in case they can’t recreate the issue, I can provide a ftp user to the team so they can inspect why the cookie option is not rendering correctly and do some test
The cookie options in the security provider are for the remember me cookie. For the session cookie you have to check the server configuration, for php in the php.ini file PHP: Runtime Configuration - Manual.
It depends on the server being used. With PHP you have to setup the session handling in the php.ini, ASP.NET has the web.config file for configuring. For NodeJS you can edit the config.json.
For NodeJS we could probably make it editable using the UI, but for PHP we can’t since the ini file is located on your server and not within the wappler project.
Edits in the config.js will be lost when that file gets an update, better to create a special user config file, it will be read by the server and extends the config.
The security provider uses 2 cookies. It uses the session cookie for keeping track of the logged in user and the remember me cookie is used when the user session is expired and logs the user in again. The cookie options in the security provider properties are for the remember me cookie.
I’m trying to replicate it again now but can’t replicate it. Seems to be fixed: now when I login on either the subdomain or main domain, I’m logged in on both of them! Just how it used to be.
Very frustrating though that I have no idea why it broke and why it’s fixed…
The only thing that I did now was removing a duplicate server provider (that wappler created when I tried to resave the security provider earlier this week).
I removed one with development target enabled, yet git showed it removed something in .wappler/targets/live production/modules/
So I reverted the removal in git, and deployed again.
@patrick
Do you have any idea what could be going wrong? I still believe it’s something in the wappler config perhaps not going well. The reason I believe that is because git didn’t show anything happening to the securityprovider or other files…
But I managed to break it and fix it without knowing how.