ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69232
|
Thu Oct 8 12:40:52 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | V3.1.4-a04faf9f | Re: Is it possible to visually group attributes with border |
Nope, this is not possible. Sorry.
Stefan
Daniel Sajdyk wrote: |
Hello,
I'm working on new logbook and in one category I'll have many attributes (many more than in attached screenshot).
So here is my question. Is it possible to visually group such attributes with some border, or something like that?
In screenshot you can see what I want to achieve.
Best Regards
Daniel
|
|
69236
|
Tue Oct 20 08:24:20 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | latest | Re: Field values dependent on other selections |
Look in the manual under "conditional attributes"
Stefan
Anthony Krishock wrote: |
All,
I would like to know if there is a way in elog to populate a field based on the value of another field. What I want to do is have a field with a few selections (a menu) and another text field that populates based on what I select from the menu.
Is this possible?
|
|
69240
|
Tue Oct 20 18:02:42 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | ELOG V3.1.4-ba8 | Re: From command line: "command Submit not allowed" |
"submit not allowed" you typically get if there is a "guest menu" for read-only access and you are not logged in. I never tried the elog program with PAM authentication, but you said that your turned authentication off. What I would do is to strip down your elogd.cfg to a very simple form until the elog utility works, then figure out which configuration makes the trouble.
Stefan
David Wallis wrote: |
Update: I tried switching the logbook to no authentication reqiured, and still get the "command Submit not allowed" response.
David Wallis wrote: |
I'm running Elog version V3.1.4-ba84827 on Red Hat Linux 7.9. As part of migrating from an older in-house logbook to Elog, I need to upload all the old logbook entries. However, when I attempt to do that with the "elog" command line tool, I'm getting the error "command Submit not allowed.
I read through a similar report from 2015 (entry #68149), but none of the potential causes seem to be at play here. The logbook is using PAM authentication, and I can log in to the web interface using the same credentials I'm using from the command line. The other case mentioned a dis-allowed encoding format, but my logbook is configured to allow all formats.
This is the command line I'm using:
/usr/local/elog/bin/elog -v -h logbook.aps.anl.gov -p 8081 -l On_Call -x -n 2 -a Date='10/19/2020 01:02' Author="David Wallis" Title='Test Upload' Status='Open' System='On-Call' -u 'wallis' '*****' "This is a test message"
|
|
|
69242
|
Tue Oct 20 18:40:05 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | ELOG V3.1.4-ba8 | Re: From command line: "command Submit not allowed" |
Giving up. Send me your config file and I will debug it.
Stefan
David Wallis wrote: |
Hmmm... I added "New" to the Guest menu list, and the button showed up for a guest user. But when I submitted the new ticket, I got the message Error: Command "Submit" is not allowed for user ""
Stefan Ritt wrote: |
"submit not allowed" you typically get if there is a "guest menu" for read-only access and you are not logged in. I never tried the elog program with PAM authentication, but you said that your turned authentication off. What I would do is to strip down your elogd.cfg to a very simple form until the elog utility works, then figure out which configuration makes the trouble.
Stefan
David Wallis wrote: |
Update: I tried switching the logbook to no authentication reqiured, and still get the "command Submit not allowed" response.
David Wallis wrote: |
I'm running Elog version V3.1.4-ba84827 on Red Hat Linux 7.9. As part of migrating from an older in-house logbook to Elog, I need to upload all the old logbook entries. However, when I attempt to do that with the "elog" command line tool, I'm getting the error "command Submit not allowed.
I read through a similar report from 2015 (entry #68149), but none of the potential causes seem to be at play here. The logbook is using PAM authentication, and I can log in to the web interface using the same credentials I'm using from the command line. The other case mentioned a dis-allowed encoding format, but my logbook is configured to allow all formats.
This is the command line I'm using:
/usr/local/elog/bin/elog -v -h logbook.aps.anl.gov -p 8081 -l On_Call -x -n 2 -a Date='10/19/2020 01:02' Author="David Wallis" Title='Test Upload' Status='Open' System='On-Call' -u 'wallis' '*****' "This is a test message"
|
|
|
|
|
69250
|
Mon Oct 26 11:42:53 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | Mac OSX | All | Other | 3.1.4 | Re: MEG style elog configuration |
It was done using the "groups" feature:
https://elog.psi.ch/elog/config.html#groups
Stefan
Daniel Kohl wrote: |
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
|
|
69252
|
Tue Oct 27 16:15:26 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | V3.1.4-ba84827 | Re: Create entry from command line - override Date? |
You have to manually manipulate the logbook files YYMMDDa.log where you find the date at the top like:
MID@$: 1
Date: Wed, 02 Sep 2020 15:38:09 +0300 <==== change here !!!!
Author: Stefan
Type: General
Category:
Subject: CURL test
Attachment:
Encoding: plain
========================================
Text body
|
69254
|
Tue Oct 27 16:49:53 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | V3.1.4-ba84827 | Re: Create entry from command line - override Date? |
"Date" must be on the first line on each entry and it must be named "Date".
Stefan
David Wallis wrote: |
Hi Stefan, thanks! Does the Date field need to be the first field in each entry? I can see adding a "termpory" field called "Orig Date", upload the old entries, then edit the file(s), delete the Date field, and rename Orig Date to Date. Will that work?
Stefan Ritt wrote: |
You have to manually manipulate the logbook files YYMMDDa.log where you find the date at the top like:
MID@$: 1
Date: Wed, 02 Sep 2020 15:38:09 +0300 <==== change here !!!!
Author: Stefan
Type: General
Category:
Subject: CURL test
Attachment:
Encoding: plain
========================================
Text body
|
|
|
69267
|
Wed Dec 2 11:51:24 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.7-2246 | Re: Change / List Change doen't work anymore? |
Yepp, the documentation was wrong. I fixed it.
Stefan |