ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 97 of 807

Not logged in

Find | Login | Help

Full | Summary | Threaded | Collapse | Expand

6453 Entries

Goto page Previous 1, 2, 3 ... 96, 97, 98 ... 805, 806, 807 Next

Re: Multi Logook Login RESOLVED, posted by Hal Proctor on Tue Apr 21 20:32:10 2009

Stefan Ritt wrote:

Hal Proctor wrote:

Grant Jeffcote wrote:

Hal Proctor wrote:

We have two logbooks, each with a different list of users.

The logbooks are open to all network users for read only.

A user with Write permisions logs into his designated logbook.

He then decides to view the other logbook, the one he does not have write permissions to by clicking on the tab to the other logbook.

He is immediately logged out of the logbook he has write permissions to.

He did not close his browser session, only clicked on the other logbook tab.

Is there Any way to keep that person logged into the logbook he has rights to without having the "keep me logged in Checkbox"?

Just like this site has Forum, Config Examples, etc.

Once you select another tab they are logged out of their logbook they just logged in to.

Have a look at this thread Hal, worked well for me: Link

thanks Grant, but I dont see the solution. your last entry still states users being logged out when switching logbooks.

Are you suggesting that every user within our orginization needs to be on the deny list of logbook1 if they have rights to logook2?

Can you try the following:

Put your "password file = xxx" option from the [global] section in elogd.cfg into each individual logook, remove it from [global]
Remove all cookies from your browser
Try again to log in to the individual logbooks

The login is handled through cookies. Once you log in, you get two cookies unm (for user name) and upwd (for user password). Each cookie contains a "path" which controls to which URL the browser sends that cookie. If you "password file = xxx" statement is under [global], then "path=/", meaning the cookie is sent for all logbooks. This confuses you if you have different rights for different logooks. If "password file = xxx" is however in each individual loogbooks configuration, then you get "path=/<lobook>". You can check that by inspecting your browser's cookies. In that case the login name and password cookies are only sent to the URL for that specific logbook. I have not tested that extensively (different browsers, with/without Apache proxy), but if it works reliably, I will put this into the documentation.

This worked for us just fine! thanks!

Mirror Server Funktion , posted by Andreas Wilke on Tue Apr 21 22:13:26 2009

Ich möchte meine "lokale" ELOG Installation mit einem Server in der Firma synchronisieren.

Dazu habe ich in der entfernten Firewall ein Portmapping auf den ELOG Server in der Firma eingerichtet.

Wenn ich von meiner "lokalen" Maschine im Browser http://meinedomain.dyndns.xx:PORT aufrufe, kann ich auf den ELOG Server zugreifen.

Ich habe in meiner "lokalen" Installation in der Section [global] den Mirror-Server = http://meinedomain.dyndns.xx:PORT angeben.

Beim Synchornisieren bekomme ich jedoch den Hinweis "Fehler beim Zugriff auf entfertes Logbuch".......

Re: Is there a way to import old log messages, posted by Stefan Ritt on Fri Apr 24 09:03:05 2009

Joseph Le wrote:

I update my elog from version 2.7.5 to 2.7.6 and mistakenly replace configuration file. so i have to reconfigure everything from ground up. when my elog back online, old log messages are not show up. is there a way to import old log messages from old log book to new one.

thanks

You don't have to import old log book messages, they should be shown automatically (as long as you don't overwrite your configuration file mistakenly). If you had a different logbook name (not "demo") your files will still be there under c:\Program Files\ELOG\logbooks\<logbook name>. Just add the proper name in elogd.cfg, restart elogd and you will see your old messages.

Database Like - ELOG Format, posted by mike cianci on Wed Apr 29 12:28:13 2009

Stefan,

I am using the Database Like - ELOG format and on the list page, the the last two columns (on the right side) are, "Text" and "Attachments (the paperclip)".

Both of which I have deleted from the input page.

Is there anyway to remove them from the List page?

Thanks, Mike

Re: Database Like - ELOG Format, posted by Stefan Ritt on Thu Apr 30 08:48:01 2009

mike cianci wrote:

Stefan,

I am using the Database Like - ELOG format and on the list page, the the last two columns (on the right side) are, "Text" and "Attachments (the paperclip)".

Both of which I have deleted from the input page.

Is there anyway to remove them from the List page?

Thanks, Mike

You need:

Show text = 0

Enable Attachments = 0

to supress the text entry box and the attachment field.

Display search = ID, Type, Location, Status

to show only the attributs of interest in the list display (your attributes could be different)

Summary lines = 0

to supress the text in the list display. At the moment, this still shows the paperclip colum, but I want to fix this in the next version.

Problem Naming Logbooks, posted by mike cianci on Fri May 1 08:05:42 2009

I have a logbook named "Centaur" (instrument name) for a problem log on an instrument and a logbook named "CentaurNewLot" for

a logbook (Database Like - ELOG format) where we would log reagent lot number changes for that instrument.

The problem is that when I name the logbooks, like I have, it screws up the formatting (List page) of the second log book.

If I rename the second logbook something totally unrelated to the first logbook my originally intended formatting returns.

Re: Problem Naming Logbooks, posted by Stefan Ritt on Wed May 6 15:35:44 2009

mike cianci wrote:

I have a logbook named "Centaur" (instrument name) for a problem log on an instrument and a logbook named "CentaurNewLot" for

a logbook (Database Like - ELOG format) where we would log reagent lot number changes for that instrument.

The problem is that when I name the logbooks, like I have, it screws up the formatting (List page) of the second log book.

If I rename the second logbook something totally unrelated to the first logbook my originally intended formatting returns.

I tried to reproduce your problem but without success. In my case the "CentaurNewLot" looks fine:

so what is different in your case? Can you try with the simple example logbook from the distribution and the add one option after the other to see which one causes the trouble?

Re: Mirror Server Funktion , posted by Stefan Ritt on Wed May 6 15:38:10 2009

Andreas Wilke wrote: