From: phil <ph...@lo...> - 2015-06-26 20:45:44
|
Hi Alistair If there are just a few lines to your solution which requires no manual editing, then perhaps you would send me the duffs so I could study. As Tim points out it is quite easy to use the config.php sessionssavepath to explicitly set where the server should save the session to. Some documentation as you say might be all we really need Alastair <kn...@gm...> wrote: >Hi Tim, > >I've just looked into this a little deeper and it appears you're referring to $SessionSavePath. After a while of fiddling around with this variable and manually creating folders for each isolated install, I was able to get this to work. Unfortunately this process isn't well documented and requires manual configuration on the server for this to work (not horrible, I'd prefer to keep manual config to a minimum). > >Perhaps, this could be simplified by setting the "Path" value in the session cookies instead. This removes the need to create folders and specify locations in the config file, and it can be easily automated too. > >On a side note, the session.inc script should probably be setting the session cookie name with session_name() as PHPSESSID is very generic and doesn't help with debugging at all. > >My Regards, >Alastair Knowles. > >On 25/06/15 03:15, Tim Schofield wrote: > >Hi Alastair the session save path can be set in config.php. The line is commented out by default. > >Thanks >Tim > >On 24 Jun 2015 12:40, "Alastair Knowles" <kn...@gm...> wrote: > >Hi, >It seems currently if you've got 2 different WebERP installs on the same >web server with 2 different paths (e.g. http://server/webERP1/ and >http://server/webERP2/), they share the same session cookies and thus >logging into both sessions at once could end up overriding the wrong >database. After doing some reading, it seems its possible to set the >session path in the cookies, thus forcing each install to have its own >cookies. I've made the required changes to the session.inc file and have >been running 2 concurrent installs with no problems for the last couple >of months. > >Just as a background as to how I've been using this functionality, this >allows me to have both a live system and a totally isolated development >system running concurrently from which I can try modifications without >the risk of damaging the live system and without having to temporarily >log out of the live system. > >I've made the necessary modifications (a grand total of 4 added lines) >and have re-based it to the latest svn (as of half an hour ago). Would >it be possible for this feature to be added upstream to the sourceforge >svn? (Pending review of course) If so, I'll send through the diff asap. > >My Regards, >Alastair Knowles. > >------------------------------------------------------------------------------ >Monitor 25 network devices or servers for free with OpManager! >OpManager is web-based network management software that monitors >network devices and physical & virtual servers, alerts via email & sms >for fault. Monitor 25 devices for free with no restriction. Download now >http://ad.doubleclick.net/ddm/clk/292181274;119417398;o >_______________________________________________ >Web-erp-developers mailing list >Web...@li... >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > >-- >Sent from my Android device with K-9 Mail. Please excuse my brevity. >------------------------------------------------------------------------------ >Monitor 25 network devices or servers for free with OpManager! >OpManager is web-based network management software that monitors >network devices and physical & virtual servers, alerts via email & sms >for fault. Monitor 25 devices for free with no restriction. Download now >http://ad.doubleclick.net/ddm/clk/292181274;119417398;o >_______________________________________________ >Web-erp-developers mailing list >Web...@li... >https://lists.sourceforge.net/lists/listinfo/web-erp-developers |