| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2010
|
Thu Oct 19 12:42:42 2006 |
 | deletoille | xavier.deletoille@synchrotron-soleil.fr | Bug report | Linux | Windows | 2.6.2-1723 | Re: Date format in Threaded display |
IT WORKS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
THANKS A LOT |
|
2009
|
Thu Oct 19 12:32:11 2006 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | Windows | 2.6.2-1723 | Re: Date format in Threaded display |
| deletoille wrote: | I’ve tried on the last available release (revision 1732) and I have the same problem.
You said in you previous message that: “I fixed yours now in revision 1734, so give it a try.”
Could you tell me when this one will be available? |
Since you checked "Linux" in the "OS" of this entry, I was under the assumption that you were able to compile elog from the Subversion repository (http://savannah.psi.ch/websvn/filedetails.php?repname=elog&path=%2Ftrunk%2Fsrc%2Felogd.c).
If you need the Windows executable, I made http://midas/elog/download/windows/elog262-6.exe for you. |
|
2008
|
Thu Oct 19 12:26:16 2006 |
 | deletoille | xavier.deletoille@synchrotron-soleil.fr | Bug report | Linux | Windows | 2.6.2-1723 | Re: Date format in Threaded display |
| Stefan Ritt wrote: | That fix for Steve Jones was slightly different, it had to do with substitutions in threaded display. I fixed yours now in revision 1734, so give it a try.
Salut,
Stefan |
Hello,
I’ve tried on the last available release (revision 1732) and I have the same problem.
You said in you previous message that: “I fixed yours now in revision 1734, so give it a try.”
Could you tell me when this one will be available?
Thanks in advance |
|
2007
|
Thu Oct 19 11:45:18 2006 |
 | Alexandre Lindote | alex@lipc.fis.uc.pt | Question | Linux | 2.6.2-1699 | How to pass attachment names to an Execute line? |
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 |
|
2006
|
Thu Oct 19 07:00:57 2006 |
 | Grant Jeffcote | grant@jeffcote.org | Question | Windows | 2.5.2 | Re: can attrinute fields contain more that one line |
> > 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 |
|
2005
|
Tue Oct 17 14:47:53 2006 |
| Dimitrios Tsirigkas | dimitrios.tsirigkas@cern.ch | Question | | | Re: Problem with large entry size |
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 |
|
2004
|
Tue Oct 17 14:42:58 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Problem with large entry size |
| 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... |
|
2003
|
Tue Oct 17 14:39:29 2006 |
| Dimitrios Tsirigkas | dimitrios.tsirigkas@cern.ch | Question | | | Re: Problem with large entry size |
| 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 |