ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69249
|
Sun Oct 25 06:26:49 2020 |
| Daniel Kohl | dkol@yaani.com | Question | Linux | Windows | Mac OSX | All | Other | 3.1.4 | MEG style elog configuration |
Hello,
I'm new to elog software and I could not find a solution to my configuration issue. I would like to setup a configuration file similar to MEG experiment's elog.
https://elog.psi.ch/elogs/meg/
I'm interested in creating similar to the structure: "General", "Collaboratoin", "Sub-groups (with sub-sub groups "Software", "Hardware" etc). I cannot tell if this was created by using Top Group feature.
Can someone explain how this design structure can be achieved?
Thanks,
Daniel |
67474
|
Thu Apr 4 17:47:12 2013 |
| Daniel Campora | dcampora@cern.ch | Bug report | Linux | 2.9.2 | Checking logging before posting |
Hi there,
Here's a bit of a special scenario. There's no server-side check the user is logged in upon posting, but it rather seems the server relies on the post data sent from the form.
An example of this can be triggered on a write restricted elog, by hitting on New and logging out in another tab. Then posting, from the first tab, will post as if the user was logged on. Hitting back and posting again also works.
Cheers |
67538
|
Tue Jun 25 19:31:56 2013 |
| Daniel Campora | dcampora@cern.ch | Question | Linux | 2.9.2 | Image attachments null in e-mails. Error log? |
Hi there :)
I'm having a problem with the e-mail notification on my installation of elog. I'm testing the attachment upload with images, and it seems to work seamlessly. However upon posting, the e-mail notification sends a null attachment, instead of the image I would expect.
Is there an error log I can check for this? I started the elog process without the daemon option, but I can't see any error coming up.
Cheers,
|
67657
|
Mon Jan 20 19:15:24 2014 |
| Daniel Campora | dcampora@cern.ch | Request | All | 2.9.2 | [Not] Submit on pressing enter key |
Hello community,
I have a feature request for the form of the ELOG.
For some users, especially coming from a MAC background, it is very inconvenient to press enter (ie. on the subject field) and post a message (or get prompted to do so). Instead, enter in these fields should work as a tab.
Cheers, keep up the good work,
Daniel |
1478
|
Mon Oct 24 14:19:18 2005 |
| Daniel Broers | d.broers@amc.nl | Question | Other | 2.6.0 b4 | Login screen reappears after correct login |
We are running elog perfectly on a solaris machine for some time now.
Except on some client pc's the login screen keeps reappearing after a succesfull login.
We upgraded to version 2.6.0 beta 4 but the problem persists.
Any suggestions? |
1480
|
Mon Oct 24 14:50:58 2005 |
| Daniel Broers | d.broers@amc.nl | Question | Other | 2.6.0 b4 | Re: Login screen reappears after correct login |
Stefan Ritt wrote: |
Daniel Broers wrote: | We are running elog perfectly on a solaris machine for some time now.
Except on some client pc's the login screen keeps reappearing after a succesfull login.
We upgraded to version 2.6.0 beta 4 but the problem persists.
Any suggestions? |
Do you have cookies disabled on these client pc's maybe? |
No, cookies are enabled. |
1482
|
Mon Oct 24 16:20:37 2005 |
| Daniel Broers | d.broers@amc.nl | Question | Other | 2.6.0 b4 | Re: Login screen reappears after correct login |
Stefan Ritt wrote: |
Can you
- Delete all cookies on the client machine and try again
- If the problem persists: Tell you how you access your elogd. Do you use Apache as proxy? Which URL statement do you have in your elogd.cfg? What are the URLs shown in the address bar of your browser?
- Can you start elogd with the "-v" flag, and send me the output shown during an unsuccessful login
|
|
1484
|
Mon Oct 24 17:14:59 2005 |
| Daniel Broers | d.broers@amc.nl | Question | Other | 2.6.0 b4 | Re: Login screen reappears after correct login |
Stefan Ritt wrote: |
Daniel Broers wrote: | Output in attachment |
Your output shows:
Set-Cookie: unm=daniel; path=/Maldi; expires=Monday, 24-Oct-05 14:57:55 GMT;
Now I don't know when you made this entry, but it looks to me like either
- your time is set incorrectly on the server side
- your "login expiration" setting in elogd is set incorrectly
Can you check these two things? |
Now it works!
- The time is (apparently) set incorect on the server side. But why would one client have problems while others don't?
- I changed the login expitation from 1 to 5 hours and now we can log in!
Thanks a lot for your quick support! |