elogd moves elog entries, posted by Konstantin Olchanski on Wed May 20 01:59:17 2015
|
elogd 3.1.0 moves all elog entries into year-named subdirectories. this feature makes it incompatible with older elogs and so should be clearly mentioned
in the documentation,
in the release announcement and in the release and migration notes. K.O. |
Re: elogd moves elog entries, posted by Andreas Luedeke on Wed May 20 11:59:59 2015
|
> elogd 3.1.0 moves all elog entries into year-named subdirectories. this feature makes it incompatible with older elogs and so should be clearly mentioned
in the documentation,
> in the release announcement and in the release and migration notes. K.O.
|
|
Re: elogd moves elog entries, posted by David Pilgram on Wed May 20 12:52:31 2015
|
> > elogd 3.1.0 moves all elog entries into year-named subdirectories. this feature makes it incompatible with older elogs and so should be clearly mentioned
in the documentation,
> > in the release announcement and in the release and migration notes. K.O.
|
|
Re: elogd moves elog entries, posted by Andreas Luedeke on Wed May 20 18:46:27 2015
|
> Stefan told me that the change was because some users were having thousands of yymmdda.log files
> in the logbook directories, and that sorting them into subdirectories by year at least did something to bring some
> order. Possibly to get around the lazy archivers, I suspect.
|
|
Re: elogd moves elog entries, posted by David Pilgram on Wed May 20 19:05:43 2015
|
> > Stefan told me that the change was because some users were having thousands of yymmdda.log files
> > in the logbook directories, and that sorting them into subdirectories by year at least did something to
bring some
|
|
Re: elogd moves elog entries, posted by Andreas Luedeke on Thu May 21 10:59:07 2015
|
I had no intention of causing any offence with my lazy archiving comment - hope I didn't, sorry if I did.
No
offence taken :-)
Personally, I would have found it useful to put the attachments into a separate directory - or at least to
allow
the possibility. Elog as it stands sometimes can, and sometimes cannot cope with that functionality - and even to try means messing |
|
Re: elogd moves elog entries, posted by Konstantin Olchanski on Wed May 20 20:03:06 2015
|
> Stefan told me that the change was because some users were having thousands of yymmdda.log files
> in the logbook directories
|
|
Re: elogd moves elog entries, posted by David Pilgram on Wed May 20 22:08:31 2015
|
> > Stefan told me that the change was because some users were having thousands of yymmdda.log files
> > in the logbook directories
>
|
Re: elogd moves elog entries, posted by Andreas Luedeke on Thu May 21 12:13:21 2015
|
> > elogd 3.1.0 moves all elog entries into year-named subdirectories. this feature makes it incompatible with older elogs and so should be clearly mentioned
in the documentation,
> > in the release announcement and in the release and migration notes. K.O.
|
|
Re: elogd moves elog entries, posted by Konstantin Olchanski on Sat May 23 02:53:31 2015
|
>
> "News for each version can be seen in the changelog (->http://midas.psi.ch/elog/download/ChangeLog)"
>
|
|
elogd complains about unknown cookies, posted by Konstantin Olchanski on Wed May 20 01:45:09 2015
|
elogd is spewing these messages about unknown cookies:
Received unknown cookie "is_returning"
|
|
Re: elogd complains about unknown cookies, posted by Stefan Ritt on Fri May 22 13:59:41 2015
|
> elogd is spewing these messages about unknown cookies:
>
> Received unknown cookie "is_returning"
|
|
Re: elogd complains about unknown cookies, posted by Konstantin Olchanski on Sat May 23 02:49:22 2015
|
> > elogd is spewing these messages about unknown cookies:
> >
> > Received unknown cookie "is_returning"
|
Entry size too large for email notification, posted by Jacky Li on Tue May 19 12:26:39 2015
|
Hi,
I am doing an inline image that is about 2.2 MB. When I do a submit, I got the following message:
Error sending Email via <i>"<email server>"</i>: Entry size too large for email notification. |
|
Re: Entry size too large for email notification, posted by Stefan Ritt on Fri May 22 13:43:14 2015
|
The size is defined by the variable MAX_CONTENT_LENGTH in elogd.c which is set to 10 MB. But email attachments are encoded in ASCII form, so they take
useually 3-4 times the space of the binary format. If you have problems with large emails, you can use the option "Email Format = 111" which
causes only the names of attachments to be included in email notifications. Users can then still click on the elog link inside the email notification and |
|
this elog errors sending email, posted by Konstantin Olchanski on Wed May 20 01:52:23 2015
|
| this elog gives errors sending mail through PSI email server. (did not capture the error messages, sorry). K.O. |
|
csv import timestamp, posted by Ferdinand Gassauer on Wed May 13 22:03:37 2015
|
I have to import a csv with a date field, which represents the creation date
this date should be used as "date" timestamp which is set automatically, otherwise all entries get the current datetime as timestamp
|
|
Re: csv import timestamp, posted by Andreas Luedeke on Thu May 14 02:19:53 2015
|
Hi Ferdinand,
and that is exactly what happens when you import a csv file with a date field:
the creation date ($entry
time) of the imported entries will be used from the "Date" column in the file.
I've just tried it and it works like a charm.
Did you have any problems doing it?
Cheers
Andreas
|
|
Re: csv import timestamp, posted by Ferdinand Gassauer on Thu May 14 07:01:23 2015
|
Thanks
what is the format of the Date field in the csv file ?
My Date is date and not datetime. |
|
Re: csv import timestamp, posted by Andreas Luedeke on Thu May 14 22:16:03 2015
|
Hi Ferdinand,
"import" is meant to be used for files that have been exported with "find". Therefore it is not very
flexible with the date format.
Todays date should look like that: "Thu 14 May 2015 22:12:00 +0200".
You have
to convert your file that the date matches this format (BTW: I found this out by using the find - export feature; it may depend on a local configuration.)
Cheers
Andreas
|
|
Elogd synchronisation with remote server, posted by Francois Cloutier on Thu May 14 02:35:15 2015
|
I came accross the admin guide and I was reading / searching for a way to sync logbooks across sites...
elogd mention "-m" and "-M" ... not elog but elogd... with that description :
synchronize logbook(s) with remote server
|
|
Re: Elogd synchronisation with remote server, posted by Andreas Luedeke on Thu May 14 05:13:34 2015
|
> I came accross the admin guide and I was reading / searching for a way to sync logbooks across sites...
> elogd mention "-m" and "-M" ... not elog but elogd... with that description :
> synchronize logbook(s) with remote server
|
"Leave Page" pop-up when "Submit" entry, posted by Andreas Luedeke on Tue May 12 03:25:45 2015 
|
I have a little problem with elogd 3.1.0. The problem persists up to the latest ELOG version, even in the
development branch (V3.1.0-8196b81):
|
|
Re: "Leave Page" pop-up when "Submit" entry, posted by Stefan Ritt on Tue May 12 11:27:52 2015
|
Thanks for the "boiling-down" of your config file. That helped me to reproduce the error quickly. It only occurs if you have a date/time attribute which
is hidden as a conditional attribute. This is a unusual combination, that's why I haven't seen that bug before. Actually some
JavaScript code checks the validity of the date attribute, but since it is conditionally not there, the JavaScript code crashes, which triggers the dialog |
Re: "Leave Page" pop-up when "Submit" entry, posted by Andreas Luedeke on Wed May 13 01:40:21 2015
|
> Thanks for the "boiling-down" of your config file. That helped me to reproduce the error quickly. It only occurs if you have a date/time attribute which
is hidden as a conditional attribute. This is a unusual combination, that's why I haven't seen that bug before. Actually some
> JavaScript code checks the validity of the date attribute, but since it is conditionally not there, the JavaScript code crashes, which triggers the dialog |
|
Re: "Leave Page" pop-up when "Submit" entry, posted by Stefan Ritt on Wed May 13 06:58:12 2015
|
> Apparently it was less work to fix than to isolate it ;-)
Well, I also spend like an hour on it. |
|
Remote entries with empty messages possible?, posted by Edmund Hertle on Fri May 8 17:45:24 2015
|
Hey,
I want to submit an entry to elog remotley using the "elog" command. For example:
elog -h elog-server-adress -l EO -a Fill=111 |
|
Re: Remote entries with empty messages possible?, posted by Stefan Ritt on Mon May 11 13:15:54 2015
|
The "command does not respond" means that the program starts reading in the main message text from the console. You can type several lines
of text, and finish it off by hitting Ctrl-D (Ctrl-Z under Windows).
I see your point of having empty texts. Indeed the "" on the command line does not work presently, so you have to add a space as a |
|
Re: Remote entries with empty messages possible?, posted by Andreas Luedeke on Mon May 11 22:51:44 2015
|
Hi Edmund,
Stefan already supplied a fix, but you could as well use a workaround: provide an empty file as text. The following works for Linux:
elog -h elog-server-adress -l EO -a Fill=111 -m /dev/null |