Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Protect Selection page=1, posted by Ocane on Wed Jun 20 14:02:45 2012 
    icon2.gif   Re: Protect Selection page=1, posted by Tom Langford on Mon Feb 18 20:12:25 2013 
       icon2.gif   Re: Protect Selection page=1, posted by Stefan Ritt on Tue Feb 19 09:13:34 2013 
    icon2.gif   Re: Protect Selection page=1, posted by Stefan Ritt on Tue Feb 19 09:14:22 2013 
Message ID: 67438     Entry time: Mon Feb 18 20:12:25 2013     In reply to: 67289     Reply to this: 67439
Icon: Reply  Author: Tom Langford  Author Email: tlangfor@umd.edu 
Category: Question  OS: Linux  ELOG Version: 2.9.1-2435 
Subject: Re: Protect Selection page=1 

Ocane wrote:

 Hi,

I have several top groups and each has several logbooks.

If I use the global option Protect Selection page=1 and Show top groups = 1, after an user logs in to the top group selection URL, the elog steers away from the top group selection page, and automatically brings him to the logbook selection page of the first top group. Is the elog programmed to exhibit this behavior?

What I would prefer is that, after an user logs in, the elog stays on the top group selection page, sine each user has his preferred destination, not always the logbooks in the first top group. Is there any setting I can use in the config file to do this? 

(My users need to access different top groups and logbooks on regular basis).

Thank you and regards.

 I am currently having a similar problem. I am migrating a few separate elogs to one new computer. I have three top groups set up with their own password files. If I log into top group A (TGA), and then try to go to top group B (TGB), I am presented with a "Create new user" screen for my login name for TGA. When I complete that form, I am taken to the user settings for top group A, rather than TGB. I can log out of TGA and then log into TGB fine, but if I try to switch between them without logging out, it freaks out.

There seems to be a problem with the cookies that keep me logged into the different top groups not recognizing that they are different entities. I'm running eLog 2.9.1 rev 436. Is it possible that this has been addressed in 2.9.2?

Thanks,

-t

ELOG V3.1.5-fe60aaf