Re: Automatically generated incrementing tags (#), posted by soren poulsen on Tue Nov 10 21:36:21 2009
|
| Stefan Ritt wrote: |
|
| soren poulsen wrote: |
|
| soren poulsen wrote: |
|
| soren poulsen wrote: |
|
Hi,
I am using the # character to generate automatically incrementing numbers for new messages.
My issue is that # is evaluated when you hit "New" but E-log is only aware of the new value being used when you hit "Submit".
So, two E-logs can have the same value substituted for # if two E-logs are being edited in parallel.
Maybe someone has a solution to this ?
Soren Poulsen
|
The solution is to use "Subst" instead of "Preset".
|
This is not really resolved, since "Subst" creates a new number on both "New" and "Reply". I would like "Subst" to create a new number only on "New" and preserve this number through replies throughout the thread. I would like to be able to say "Subst thread = #" to make a new number for the thread and combine it with "Subst on reply thread = $thread" to preserve the number on replies, but this does not work. Maybe someone has already done this ?
Soren
|
I just reworked the "Subst" command to make it more consistently. Now "Subst on Edit" and "Subst on Reply" are executed after the entry submission, and they are mutually exclusive. So all you need right now is
Subst Tag = #
and it will not increment when editing or replying to an existing entry. The fix is in SVN revision 2264.
|
Thanks a lot for doing this change. |
|
Re: Automatic creation of new entry in another logbook, posted by Stefan Ritt on Fri Nov 18 21:03:03 2005
|
| Carlos Mateo wrote: | | I am trying to create an entry in logbook2 when I submit a new entry in logbook1. The automatically created entry in logbook2 will have a reference to the entry that created it. |
Please tell me for what purpose you need two identical logbooks. Maybe what you want can be achieved in a simpler way.
| Carlos Mateo wrote: | | 1.- Using the "Execute new" I call elog to create the second entry. As the server is single-process, it locks: elog is waiting for elogd to be ready and elogd is waiting for elog to finish to accept new requests. As my server is on a Windows machine I canīt execute elog on background. |
Have you tried to start your elog with the start command under Widnows, like start elog .... This is the equivalent of starting a process in the background under linux.
| Carlos Mateo wrote: | | 2.- I tried to run 2 servers on different ports using the same elogd.cfd file, calling the second server from elog. This "almost" works: the logbook files are updated, but the original server must be restarted to "see" the changes. |
This is because you use the same data directory for both servers. If one server writes a new entry to a file, the other server does not realize this. Only when you restart it, it rescans the whole data directory and gets aware of the new entry. Try using separate data directories for the two servers.
| Carlos Mateo wrote: | | 3.- Using the "Menu text" option, I create a link to create the new entry. The problem is that attributes are not parsed: a link like this <a href="/logbook2/?cmd=New&pAttr=Value $ID">Test</a> wonīt substitute $ID |
Parsing attributes is not implemented and therefore will not work. |
Re: Automatic creation of new entry in another logbook, posted by Carlos Mateo on Mon Nov 21 10:41:46 2005
|
| Stefan Ritt wrote: |
| Carlos Mateo wrote: | | I am trying to create an entry in logbook2 when I submit a new entry in logbook1. The automatically created entry in logbook2 will have a reference to the entry that created it. |
Please tell me for what purpose you need two identical logbooks. Maybe what you want can be achieved in a simpler way.
They are not identical. They just share some information
| Carlos Mateo wrote: | | 1.- Using the "Execute new" I call elog to create the second entry. As the server is single-process, it locks: elog is waiting for elogd to be ready and elogd is waiting for elog to finish to accept new requests. As my server is on a Windows machine I canīt execute elog on background. |
Have you tried to start your elog with the start command under Widnows, like start elog .... This is the equivalent of starting a process in the background under linux.
Thank you. It works with start!
| Carlos Mateo wrote: | | 2.- I tried to run 2 servers on different ports using the same elogd.cfd file, calling the second server from elog. This "almost" works: the logbook files are updated, but the original server must be restarted to "see" the changes. |
This is because you use the same data directory for both servers. If one server writes a new entry to a file, the other server does not realize this. Only when you restart it, it rescans the whole data directory and gets aware of the new entry. Try using separate data directories for the two servers.
| Carlos Mateo wrote: | | 3.- Using the "Menu text" option, I create a link to create the new entry. The problem is that attributes are not parsed: a link like this <a href="/logbook2/?cmd=New&pAttr=Value $ID">Test</a> wonīt substitute $ID |
Parsing attributes is not implemented and therefore will not work. |
Thank you for your help |
|
Re: Automatic Export, posted by Stefan Ritt on Fri Jan 28 08:33:49 2005
|
> Is there any way to automatically export the logbook(s)?
Kind of. You can use "wget" under Linux (use cygwin under Windows to get wget
under Windows). Then issue a
wget "http://midas.psi.ch/elogs/forum/?cmd=Search&mode=xml"
and you will get an XML export. Same works with CSV export. If you put that
command in cron, you have this on an automatic basis. |
|
Re: Automatic Export, posted by Tim Fowler on Fri Jan 28 18:04:03 2005
|
> > Is there any way to automatically export the logbook(s)?
>
> Kind of. You can use "wget" under Linux (use cygwin under Windows to get wget
> under Windows). Then issue a
>
> wget "http://midas.psi.ch/elogs/forum/?cmd=Search&mode=xml"
>
> and you will get an XML export. Same works with CSV export. If you put that
> command in cron, you have this on an automatic basis.
Thanks Stefan! That was exactly what I was looking for! |
|
Re: Automatic Copy to , posted by Stefan Ritt on Wed Jan 18 12:33:00 2006
|
| Chris Warner wrote: | | Is it possible to configure elog to copy a new entry from 1 logbook to another? |
No, you have to copy entries manually with the "Copy to" menu command. For that, you have to put something like
Menu commands = List, New, Edit, Copy to, Delete, Reply, Duplicate, Find, Config, Help
into your configuration file. |
|
Re: Automatic Copy to , posted by Grant Jeffcote on Sun Aug 31 14:43:19 2008
|
Stefan,
Is there any way I might be able to initiate the 'copy to' function by selecting a 'tick box' (boolean) or conditional attribute choice in an entry page when submitting that page? We have a requirement where we run a main 'Operations' log and have another log with some entries needing to be in both (for additional actions etc). I understand the Operator can always manually use the 'Copy To' function after submitting the original entry but was wondering if there was some way a shell script (execute function?) or similar may be activated by a boolean or even a 'conditional' choice?
Thx |
|
Re: Automatic Copy to , posted by Stefan Ritt on Mon Sep 1 13:54:53 2008
|
| Grant Jeffcote wrote: | Stefan,
Is there any way I might be able to initiate the 'copy to' function by selecting a 'tick box' (boolean) or conditional attribute choice in an entry page when submitting that page? We have a requirement where we run a main 'Operations' log and have another log with some entries needing to be in both (for additional actions etc). I understand the Operator can always manually use the 'Copy To' function after submitting the original entry but was wondering if there was some way a shell script (execute function?) or similar may be activated by a boolean or even a 'conditional' choice?
Thx |
I put your request on the whishlist. |