Jump to content

Demitry

Members
  • Content count

    311
  • Joined

  • Last visited

  • Days Won

    8

Status Replies posted by Demitry

  1. strange! i moved with my bootstrapped oscommerce to a new server (debian9, php7, mariadb) and mysql session timeout does not work again. even with the modifications from your addon. but only in admin. catalog user sessions timout as expected. any idea where to look?

    Regards,

    Stephan

    1. Demitry

      Demitry

      yeah, that's good to know, ...I have not set up the htpassword protection on the new BS Edge development site for the admin login yet. So, I did not test that piece of it with the modified contribution, though I thought it should not make a difference.

      I'm not sure as to why it did not work on the other server. 

      I'll try and test it on my set-up at some point. Thank you for the follow-up.

      Demitry

       

    2. (See 5 other replies to this status update)

  2. strange! i moved with my bootstrapped oscommerce to a new server (debian9, php7, mariadb) and mysql session timeout does not work again. even with the modifications from your addon. but only in admin. catalog user sessions timout as expected. any idea where to look?

    Regards,

    Stephan

    1. Demitry

      Demitry

      In theory, it should work fine. I mean the only thing that admin panel session time entry is doing is being stored in the database table to be applied to the conditional statement in /admin/includes/functions/sessions.php to evaluate the time passed since the last page load.

      And, it's the exact same script for the catalog side.

      Let me know if you find out. I'm semi-technical and not that great with sessions. I'd be curious to know. Thanks.

    2. (See 5 other replies to this status update)

  3. strange! i moved with my bootstrapped oscommerce to a new server (debian9, php7, mariadb) and mysql session timeout does not work again. even with the modifications from your addon. but only in admin. catalog user sessions timout as expected. any idea where to look?

    Regards,

    Stephan

    1. Demitry

      Demitry

      also, check to make sure that the entry in the admin panel for the admin session is numbers only. I added a condition to make sure that the entered data is numeric, and more than 30 seconds. It should be line 34 in /admin/includes/functions/sessions.php

      if (is_numeric(SESSION_EXPIRATION_ADMIN) && SESSION_EXPIRATION_ADMIN > 30) {

      That means that if you enter anything other than numbers, or a number less than 30 seconds, or leave that field blank, it will revert to server-side session settings.

       

    2. (See 5 other replies to this status update)

  4. strange! i moved with my bootstrapped oscommerce to a new server (debian9, php7, mariadb) and mysql session timeout does not work again. even with the modifications from your addon. but only in admin. catalog user sessions timout as expected. any idea where to look?

    Regards,

    Stephan

    1. Demitry

      Demitry

      hi Stephan,

      I am not familiar with the debian9 OS and mariaDB. However, after googling the mySQL to mariaDB migration, I found some session issues that others have experienced as well. Here is just one of such forum threads.

      https://mariadb.com/kb/en/library/migrating-from-mysql-mariadb-server-closing-client-connections-unexpectedly/

      Here the discussion is regarding the client sessions, however, I know that you mentioned it was the admin panel session that was the issue. There is mention in this thread of overriding the session settings using a wait_timeout directive. Unfortunately I am not familiar enough with this database to tell you how & where to set this setting or whether it will resolve the admin panel session issue you have.

      If you can find your way around code, I suggest to see if this or another fix will solve the problem, otherwise try to contact tech support at www.mariadb.com and see if they can help with this issue. It seems like others have the same problem, so I'm sure they have a solution for it.

      I found this recent osC forum too, though not much help on there.

      I apologize that I could not be of more help.

      Demitry

       

    2. (See 5 other replies to this status update)

×