Check the session save path: session_save_path() http://php.net/manual/en/function.session-save-path.php
It is possible to define different session.save_path configurations for specific directories in php.ini See http://php.net/manual/en/ini.sections.php Also it might be overridden in either a user.ini file: http://php.net/manual/en/configuration.file.per-user.php Or .htaccess php_value (sorry if this double posted, Google has been giving me grief lately) David Neilsen | 07 834 3366 | PANmedia ® On Thu, Sep 8, 2011 at 10:38 AM, Robert Urquhart <[email protected]>wrote: > I have a php curler which has stumped me. > > Data being stored in $_SESSION by a script in a sub-directory is not > available to scripts in the webroot directory. It can be passed > between and across any subdirectories of the webroot just fine (so my > short-term solution is to move some functionality to a subdirectory > but this is not ideal). > > - the webroot scripts are correctly using the same session id. > > - webroot scripts don't appear to be preserving session data beyond > their own page load either - it doesn't appear on a refresh or on > other pages whether also in webroot or in subdirectories > > - most of the content on webroot pages is output by the exact same > code as on subdirectory pages - the page files themselves only contain > some flags and then an include (session_start() is down in the > include). > > I'm guessing it's some sort of scoping issue, but I've checked for > www / not-www switches and suchlike. > > Anyone run into anything like this before? We recently changed servers > - I've yet to test on other sites to see if the problem occurs there > as well (could be a lot of work involved if it does :( ). > > Robert Urquhart > > -- > NZ PHP Users Group: http://groups.google.com/group/nzphpug > To post, send email to [email protected] > To unsubscribe, send email to > [email protected] > -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
