ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66583
|
Sun Nov 8 23:29:35 2009 |
| soren poulsen | soren.poulsen@cern.ch | Question | Linux | 2.7.7 | Re: Automatically generated incrementing tags (#) |
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
|
This can be solved with something like "Subst <attr> = $shell(cmd...) where cmd calculates a new value of attr, as a function of #, when attr does not already have a value. This thread is closed.
Soren
|
66585
|
Mon Nov 9 11:50:05 2009 |
| Eddy Berends | eddy.berends@stratosglobal.com | Bug report | Linux | 2.7.7 | Reply on item not allowed moving item to other logbook |
After I moved an item from one logbook to another one I cannot reply on this item anymore.
When the submit button is clicked it returns: Submit not allowed
This eLog server running Linux is sync'd with an server running Windows XP.
On the windows server the funcionality is working perfect(so no Submit is not allowed on a reply) |
66591
|
Tue Nov 10 14:24:26 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.7 | Re: Reply on item not allowed moving item to other logbook |
Eddy Berends wrote: |
After I moved an item from one logbook to another one I cannot reply on this item anymore.
When the submit button is clicked it returns: Submit not allowed
This eLog server running Linux is sync'd with an server running Windows XP.
On the windows server the funcionality is working perfect(so no Submit is not allowed on a reply)
|
Check your configuration file for the destination logbook, probably you have only restricted rights there ("Guest menu", "Login user" ???) |
66592
|
Tue Nov 10 14:42:11 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.7 | Re: Automatically generated incrementing tags (#) |
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. |
66594
|
Tue Nov 10 15:00:15 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.5 | Re: Dynamic attribute values |
Steve Williamson wrote: |
Hi
I'm doing something wrong but can't work out what!
I've created a new logbook with some date attributes that need to keep in step, e.g. one date ("receipt date") is set to the date the new record is created and another ("response required") to 7 days later. The logbook doesn't use threaded messages, just a single page for each log entry with Submin/Preview/Back. The dates are set with:
Preset Receipt Date = $date
Preset Response Required = $shell(gawk 'BEGIN{ print $Receipt Date + 86400 * 7}')
"receipt date" and "response required" are set correctly when the log is written but if I change "receipt date" then "response required" is not altered - presumably because Preset only works on "New". Tho I haven't found a way to make this dynamic with Subst.
When the log is updated later a third date may be entered ("proposal submitted") and this should calculate a fourth date ("proposal expires"). Again, I thought I could do this with some sort of "Subst" but can't work out how. If I use Subst then the value of "proposal expires" isn't changed at all and if I use Subst On Edit then the value isn't changed until I go in to edit the log when the correct "proposal expires" date gets calculated and displayed, e.g.:
Subst On Edit Proposal Expires = $shell(gawk 'BEGIN{ if ($Proposal Sumbitted > 0) {print $Proposal Submitted + 86400 * 30}}')
Am I trying to do the impossible, and is there a document that will help me to understand when different updates (Preset, Subst, Subst On..., Change etc) happen and comparing their use?
|
Just try with the current version, where I reworked the "Subst" commands. See elog:66592. "Subst" work now only on "New", and "Subst on Edit" only works when editing an entry. |
66595
|
Tue Nov 10 21:36:21 2009 |
| soren poulsen | soren.poulsen@cern.ch | Question | Linux | 2.7.7 | Re: Automatically generated incrementing tags (#) |
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. |
66597
|
Wed Nov 11 19:53:57 2009 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | 2.7.7-2252 | Paper clip showing attachment not always present |
Hi Stefan,
I must have seen this before, but only just "noticed" it.
If you attach a picture or pdf to the first entry in a tread, there is then a paperclip after the thread display
line. This shows up in threaded view or collapsed threaded view.
If you then attach a picture or pdf to a subsequent entry, the paperclip icon does not show up in threaded
display, (it is still there on the initial entry) but if the attachment is to the latest entry it shows up in
treaded collapsed display (collapse on last=1, of course). If collapse on last=0, then initial entry shows on
threaded, collapsed, and that has the icon as expected.
When the icon does show, you can click on it and get the correct attachment to show/launch reader or whatever.
It would appear to be a bug that the attachment icon does not appear in the threaded display (for any entry
other than the initial one).
(sorry about the first posting, hit the wrong key sequence in error)
Regards,
David Pilgram. |
66598
|
Fri Nov 13 10:57:03 2009 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | 2.7.7-2252 | Re: Paper clip showing attachment not always present |
I may have made this sound as if the issue occurs if the first entry in a thread has an attachment; in fact it
happens whether or not there is an attachment to the first entry.
Hope this makes matters a bit clearer.
> Hi Stefan,
>
> I must have seen this before, but only just "noticed" it.
>
> If you attach a picture or pdf to the first entry in a tread, there is then a paperclip after the thread display
> line. This shows up in threaded view or collapsed threaded view.
>
> If you then attach a picture or pdf to a subsequent entry, the paperclip icon does not show up in threaded
> display, (it is still there on the initial entry) but if the attachment is to the latest entry it shows up in
> treaded collapsed display (collapse on last=1, of course). If collapse on last=0, then initial entry shows on
> threaded, collapsed, and that has the icon as expected.
>
> When the icon does show, you can click on it and get the correct attachment to show/launch reader or whatever.
>
> It would appear to be a bug that the attachment icon does not appear in the threaded display (for any entry
> other than the initial one).
>
> (sorry about the first posting, hit the wrong key sequence in error)
>
> Regards,
>
> David Pilgram. |