ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
900
|
Wed Feb 2 10:37:48 2005 |
| Laurent S. Nadolski | nadolski@synchrotron-soleil.fr | Bug report | Linux | Windows | V2.5.6-1 | Conditional attributes does not work in French |
Hi,
I am very much interested in using elog as a shift logbook for SOLEIL
accelerators.
I tested most of the options. Every thing works well except the conditional
attributs when French language is selected. In this case, I lost the
selected list option in the Field Equipement.
Here a simple exemple for testing.
NB: tests were done using the last and before last elog version.
I switched the language from English to French in Global options
Attributes = Accelerateur, Equipement
Options Accelerateur= Linac{1}, LT1{2}
{1}Options Equipement= cannon, section1
{2}ROptions Equipement= Alimentation, Diagnostics
I guess this is a simple bug since this problem does not exist for other
languages.
Best Regards,
Laurent Nadolski |
899
|
Tue Feb 1 14:44:00 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.5.5-2 | Re: Finding Last Changed Entries |
> Is there an inbuilt way to find the last entries changed in an elog?
>
> I could add a "Last Mod" attribute and then config "Subst on edit Last Mod =
> $date", but it occurred to me that this functionality might already be in
> this wonderful tool somewhere, but I just haven't found it yet.
>
> So, is it?
No it isn't. Not everybody wants it. So you have to do it in the way you
outlined it. Also have a look at http://midas.psi.ch/elog/faq.html#11
- Stefan |
898
|
Tue Feb 1 14:41:08 2005 |
| Bee | ralphb.elog@spampot.com | Question | All | 2.5.5-2 | Finding Last Changed Entries |
Is there an inbuilt way to find the last entries changed in an elog?
I could add a "Last Mod" attribute and then config "Subst on edit Last Mod =
$date", but it occurred to me that this functionality might already be in
this wonderful tool somewhere, but I just haven't found it yet.
So, is it?
Best regards, Ralph. |
897
|
Fri Jan 28 18:04:03 2005 |
| Tim Fowler | timfowler1@gmail.com | Request | Linux | Windows | 2.5.5-3 | Re: Automatic Export |
> > 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! |
896
|
Fri Jan 28 08:33:49 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | Windows | 2.5.5-3 | Re: Automatic Export |
> 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. |
895
|
Thu Jan 27 19:09:55 2005 |
| Tim Fowler | timfowler1@gmail.com | Request | Linux | Windows | 2.5.5-3 | Automatic Export |
Is there any way to automatically export the logbook(s)? |
894
|
Wed Jan 26 07:40:46 2005 |
| John Habermann | john.habermann@wilderness.org.au | Question | Linux | 2.5.5+r152 | Re: mirroring specific logbooks |
> > I was just wondering if it is possible to define what logbooks you want
> > mirrored in the [Global] part of the elogd.conf file.
>
> I added a new option
>
> Mirror exclude = 1
>
> which has to be put into the individual logbook section (not the [global] one).
> The modification will be contained in the next release.
Thank you very much Stefan. |
893
|
Tue Jan 25 21:48:52 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.5+r152 | Re: mirroring specific logbooks |
> I was just wondering if it is possible to define what logbooks you want
> mirrored in the [Global] part of the elogd.conf file.
I added a new option
Mirror exclude = 1
which has to be put into the individual logbook section (not the [global] one).
The modification will be contained in the next release. |