Re: Problem with autosave functionality when combined with no 'edit' button, posted by Andreas Luedeke on Tue May 5 11:01:36 2015
|
Hi Thomas,
just my two cent: as a quick workaround (for now) you could restrict editing messages to a short time range, like 30 minutes. That would cover
most cases of draft messages.
Restrict edit time = 0.5
But I agree that |
Re: Problem with autosave functionality when combined with no 'edit' button, posted by Andreas Luedeke on Tue May 5 12:17:24 2015
|
| Oups, now I feel almost a little bit sorry for asking But thank you anyway!!! |
|
Re: Preloading Options or Moptions from a text file or CSV, posted by Andreas Luedeke on Mon May 11 22:42:44 2015
|
> > > Title says all :)
> > >
> > > Is it possible to preload Options or Moptions from a text file or CSV instead of being load from the elogd.conf ?
|
|
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 |
"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 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: Attribute not updated, posted by Andreas Luedeke on Thu May 14 02:02:45 2015
|
Hi Francois,
as far as I know there is a limit on the number of conditions you can use (See elog:67303).
I guess you did hit that limit.
|
|
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
|