-
Welcome to the Chevereto User Community!
Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.
Please keep in mind:
- This community is user-driven. Always be polite and respectful to others.
- Support development by purchasing a Chevereto license, which also gives you priority support.
- Go further by joining the Community Subscription for even faster response times and to help sustain this space
User Sessions
- Thread starter mystik
- Start date
Hi @mystik
In v3.10.5 I changed the load priority of the core stuff and I gave top priority to app/settings.php. The idea is that this file can now be used to add any dirty hack you need to add to runtime. This is useful if your server administrator has some stuff disabled or the configuration is just messed up. I know, is horrible but it helps those that are being struggled there.
So, while I was doing that I noticed that a very common issue (session stuff) can be easily fixed with just one single line so I made a shortcut for those who need it. The session key is just a faster way to fix sessions for some.
If you want longer sessions, simply increase the session lifetime. Maybe you can't do it in your server settings, right? Bingo, now you add your dirty:
right into app/settings.php!
Rudycares.
In v3.10.5 I changed the load priority of the core stuff and I gave top priority to app/settings.php. The idea is that this file can now be used to add any dirty hack you need to add to runtime. This is useful if your server administrator has some stuff disabled or the configuration is just messed up. I know, is horrible but it helps those that are being struggled there.
So, while I was doing that I noticed that a very common issue (session stuff) can be easily fixed with just one single line so I made a shortcut for those who need it. The session key is just a faster way to fix sessions for some.
If you want longer sessions, simply increase the session lifetime. Maybe you can't do it in your server settings, right? Bingo, now you add your dirty:
PHP:
ini_set('session.gc_maxlifetime', <ONE MILLION SECONDS!>);right into app/settings.php!
Rudycares.