Re: Email format, posted by Arckonit on Tue Oct 17 09:35:01 2006
|
;)I've searched, i don't understand
but thanks !
"relis ton foutu manuel !"
excellent |
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Tue Oct 17 14:39:29 2006
|
| Stefan Ritt wrote: |
The problem lies in the ELCode parsing. When you post an entry in ELCode form, the elogd server has to parse every word to see if it's any of the ELcode tags. This is right now implemented in a kind of poor way, such that it takes very long for long entries. I will work to optimize that. In the meantime, it will help if you post such long entries just in "plain" form.
- Stefan |
Hi again,
I was wondering what is the cleanest way of changing old entries already submitted in ELCode into plain text. If I do not include ELCode in the allowed encodings does this apply to already submitted entries as well or will they still be treated as ELCode?
Thanks,
Dimitris |
|
Re: Problem with large entry size, posted by Stefan Ritt on Tue Oct 17 14:42:58 2006
|
| Dimitrios Tsirigkas wrote: | | I was wondering what is the cleanest way of changing old entries already submitted in ELCode into plain text. If I do not include ELCode in the allowed encodings does this apply to already submitted entries as well or will they still be treated as ELCode? |
The encoding is stored as an "invisible" attribute in each entry. You can change it in two ways:
1) Select each entry, click "edit", change the encoding with the radio buttons at the bottom and submit it again
2) Go and edit directly the xxxxxxa.log files in your logbook directory. You will see in those files something like
Encoding: ELCode
and you can change it with an editor to
Encoding: plain
Afterwards you have to restart the elogd daemon.
Did you try the new version, would be interesting to see if it's any better... |
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Tue Oct 17 14:47:53 2006
|
Thanks Stefan,
| Stefan Ritt wrote: | | Did you try the new version, would be interesting to see if it's any better... |
I didn't find the time to try it yet but I will do that later today. I will keep you posted - more soon.
Cheers,
Dimitris |
Re: can attrinute fields contain more that one line, posted by Grant Jeffcote on Thu Oct 19 07:00:57 2006
|
> > Is there any way to configure elog so that attribute fields can be edited
> > on more than line like the 'text' field?
> >
> > (This would be useful so that attributes could contain larger portions of
> > text including line breaks)
>
> No, but this request is already on the wishlist
> (http://midas.psi.ch/elog/wishlist.html) since some time. I added your vote.
Hi Stefan, could you add my vote for this feature too please?
Many thx |
How to pass attachment names to an Execute line?, posted by Alexandre Lindote on Thu Oct 19 11:45:18 2006
|
Hi,
I'm trying to pass the name of an attachment in a "Execute new " line, but I can't seem to get the correct syntax...
I've tried:
Execute new = echo "New document with reference $Internal Ref with the name $attachements " >> /home/zeplin3/lixo.log
Execute new = echo "New document with reference $Internal Ref with the name $attachements1 " >> /home/zeplin3/lixo.log
Execute new = echo "New document with reference $Internal Ref with the name $1 " >> /home/zeplin3/lixo.log
but nothing seem to work. If I remove the $attachments bit the output is correct...
Any suggestions?
Thanks
Alex |
|
Re: How to pass attachment names to an Execute line?, posted by Stefan Ritt on Thu Oct 19 19:45:35 2006
|
| Alexandre Lindote wrote: | Hi,
I'm trying to pass the name of an attachment in a "Execute new " line, but I can't seem to get the correct syntax...
I've tried:
Execute new = echo "New document with reference $Internal Ref with the name $attachements " >> /home/zeplin3/lixo.log
Execute new = echo "New document with reference $Internal Ref with the name $attachements1 " >> /home/zeplin3/lixo.log
Execute new = echo "New document with reference $Internal Ref with the name $1 " >> /home/zeplin3/lixo.log
but nothing seem to work. If I remove the $attachments bit the output is correct...
Any suggestions? |
Sorry there was a type in the documentation. You should write
$attachments
and not
$attachements
then it will work. |
|
Text column in the main list, posted by Alexandre Lindote on Fri Oct 20 13:26:10 2006
|
Hi,
is there a way of removing the "Text" column from the main listing of a logbook?
I have a logbook that works as a document database, and I don't even allow the entering of text... But the column insists on appearing! 
Thanks
Alex |