Re: rename menu commands , posted by Andreas Luedeke on Tue Apr 11 22:44:40 2017
|
Hm, maybe my question is silly, but why don't you just use the "Duplicate" command instead of renaming and misusing "Copy to"??
Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#general):
Menu commands = <list>
This option specifies the menu commands displayed on top of a single logbook page. For certain installations, it can be useful to disable some commands. Following commands are possible:
- New - Enter new logbook entry
- Edit - Edit current logbook entry
- Delete - Delete current logbook entry
- Reply - Submit a reply to current entry
- Duplicate - Duplicate the current entry with the possibility to change some values
- [...]
- Copy to - Copy entry to other logbook
- [...]
The commands are always in English, independent of the language = ... setting, and are automatically translated into the specified language.
If this option is not present, following default is used:
Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Config, Help
| Francois Cloutier wrote: |
|
Hi !
I do have an setup were I would like to rename the menu command but keeping their fonction. Namely, I would like to rename the "copy to" button to "Duplicate" since thats the option I would like to put in place ( Copy to = Same logbook only).
I tried to do so with css but it is not possible since the button doesn't have a specific id... Would you have another solution ?
Thanks for your help !
|
|
Re: rename menu commands , posted by Francois Cloutier on Wed Apr 12 13:52:34 2017
|
Somehow, I've missed to see that option :)
Thanks :)
| Andreas Luedeke wrote: |
|
Hm, maybe my question is silly, but why don't you just use the "Duplicate" command instead of renaming and misusing "Copy to"??
Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#general):
Menu commands = <list>
This option specifies the menu commands displayed on top of a single logbook page. For certain installations, it can be useful to disable some commands. Following commands are possible:
- New - Enter new logbook entry
- Edit - Edit current logbook entry
- Delete - Delete current logbook entry
- Reply - Submit a reply to current entry
- Duplicate - Duplicate the current entry with the possibility to change some values
- [...]
- Copy to - Copy entry to other logbook
- [...]
The commands are always in English, independent of the language = ... setting, and are automatically translated into the specified language.
If this option is not present, following default is used:
Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Config, Help
| Francois Cloutier wrote: |
|
Hi !
I do have an setup were I would like to rename the menu command but keeping their fonction. Namely, I would like to rename the "copy to" button to "Duplicate" since thats the option I would like to put in place ( Copy to = Same logbook only).
I tried to do so with css but it is not possible since the button doesn't have a specific id... Would you have another solution ?
Thanks for your help !
|
|
|
Re: rename menu commands , posted by David Pilgram on Wed Apr 12 14:00:58 2017
|
So did I [thankful there is no shame face icon].
| Francois Cloutier wrote: |
|
Somehow, I've missed to see that option :)
Thanks :)
| Andreas Luedeke wrote: |
|
Hm, maybe my question is silly, but why don't you just use the "Duplicate" command instead of renaming and misusing "Copy to"??
Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#general):
Menu commands = <list>
This option specifies the menu commands displayed on top of a single logbook page. For certain installations, it can be useful to disable some commands. Following commands are possible:
- New - Enter new logbook entry
- Edit - Edit current logbook entry
- Delete - Delete current logbook entry
- Reply - Submit a reply to current entry
- Duplicate - Duplicate the current entry with the possibility to change some values
- [...]
- Copy to - Copy entry to other logbook
- [...]
The commands are always in English, independent of the language = ... setting, and are automatically translated into the specified language.
If this option is not present, following default is used:
Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Config, Help
| Francois Cloutier wrote: |
|
Hi !
I do have an setup were I would like to rename the menu command but keeping their fonction. Namely, I would like to rename the "copy to" button to "Duplicate" since thats the option I would like to put in place ( Copy to = Same logbook only).
I tried to do so with css but it is not possible since the button doesn't have a specific id... Would you have another solution ?
Thanks for your help !
|
|
|
|
|
Re: Elog crashes with null Username, posted by Xuan Wu on Fri Apr 21 02:21:59 2017
|
We also meet this issue occasionally, so how can we get rid of this?
| Stefan Ritt wrote: |
|
Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.
| Alan Grant wrote: |
|
I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:
16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)
|
|
|
|
Re: Elog crashes with null Username, posted by Alan Grant on Fri Apr 21 05:27:35 2017
|
Are you using the current git revision Xuan?
| Xuan Wu wrote: |
|
We also meet this issue occasionally, so how can we get rid of this?
| Stefan Ritt wrote: |
|
Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.
| Alan Grant wrote: |
|
I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:
16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)
|
|
|
|
|
Re: Elog crashes with null Username, posted by Xuan Wu on Fri Apr 21 08:19:05 2017
|
No, We are using the released version 3.1.2
How to use the current git revision or is it a long time to wait for the next release?
| Alan Grant wrote: |
|
Are you using the current git revision Xuan?
| Xuan Wu wrote: |
|
We also meet this issue occasionally, so how can we get rid of this?
| Stefan Ritt wrote: |
|
Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.
| Alan Grant wrote: |
|
I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:
16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)
|
|
|
|
|
|
Re: Elog crashes with null Username, posted by Stefan Ritt on Fri Apr 21 10:57:07 2017
|
I made a new release for you 3.1.3
| Xuan Wu wrote: |
|
No, We are using the released version 3.1.2
How to use the current git revision or is it a long time to wait for the next release?
| Alan Grant wrote: |
|
Are you using the current git revision Xuan?
| Xuan Wu wrote: |
|
We also meet this issue occasionally, so how can we get rid of this?
| Stefan Ritt wrote: |
|
Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.
| Alan Grant wrote: |
|
I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:
16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)
|
|
|
|
|
|
|
Re: Elog crashes with null Username, posted by Xuan Wu on Fri Apr 21 12:18:57 2017
|
Awesome！It's appreciated. Many Thanks!
| Stefan Ritt wrote: |
|
I made a new release for you 3.1.3
| Xuan Wu wrote: |
|
No, We are using the released version 3.1.2
How to use the current git revision or is it a long time to wait for the next release?
| Alan Grant wrote: |
|
Are you using the current git revision Xuan?
| Xuan Wu wrote: |
|
We also meet this issue occasionally, so how can we get rid of this?
| Stefan Ritt wrote: |
|
Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.
| Alan Grant wrote: |
|
I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:
16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)
|
|
|
|
|
|
|
|