Hi,
OXID starts a session only when a special class or function is called
or a parameter exists in the request.
Classes that cause OXID to start a session:
- register (in views/register.php)
- account (in views/account.php)
Functions that cause OXID to start a session:
- tobasket
- login_noredir
You are not necessarily bound to those conditions.
You can force a session start on each request by setting
$this->blForceSessionStart in the config.inc.php to true.
But I am also looking forward for a reasonable answer to your question :)
Mit freundlichen Grüßen
Sven Ferber
__
Hi,
have a look at the function _getRequireSessionWithParams() in class oxsession.
You can expand the array in config.inc.php and add classes, functions or
parameters, so you are not bound to these conditions.
Cause of performance reason it's a good idea to start session only when
necessary. F
Doesn't the example given by Elisabeth encourage session use for
performance? If all users without a session share the same cache file, that
would cause a bottle neck for write access? Since hard drive space is not
usually an issue, seems to me that having more files per user would benefit
perfor
No, the cache files in OXID EE are generated once and in standard configuration
have a lifetime of 12 hours. The users only "read" this file once it is
generated, it's a static file (or object, depending on cache backend).
Performance peak is only when generation is necessary. Users with session
Hi,
@oxid-dev-team: I would like to hear your opinion about this:
When you limit the voucher-series a user-group, for example to
national-customers and the user isnt logged in when he tries to use the
voucher, he gets an error because he isnt in that group.
For the case he is logged in a
