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
|
|
Re: Entry size too large for email notification, posted by Andreas Luedeke on Tue May 19 16:34:20 2015
|
Hi Jacky,
if I read the source code correctly then the maximum size of a base64 encoded email is hard coded to be 10 MB in elogd.h (recompile
after changing it):
#define MAX_CONTENT_LENGTH 10*1024*1024
But
I think that an 2.2 MB image should easily fit into that.
Andreas
|
|
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 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 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 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: Fixed text, posted by Andreas Luedeke on Tue May 26 11:26:12 2015
|
Dear Neal,
I don't understand your example. There is no such thing as a "subject field". You can define an attribute called
"subject", like in this logbook.
But I would guess that you want to have five attributes "Time Off", "Reason",
etc. that cannot be altered after an entry has been created? That's easy.
Or do you want to protect entries with specific content not |
|
Re: Fixed text, posted by Andreas Luedeke on Wed May 27 08:41:05 2015
|
Hi Neal,
you can preload words into one attribute field, but one field is either editable or not, you cannot protect single words in
a field.
But the ELOG way to solve this would be to have multiple attributes: you would get one entry field for each attribute.
Just
look at this logbook: it has the attributes Icon, Author, Author Email, Category, OS, ELOG Version and Subject.
You can change the content |