Auto save feature not working on 3.1.0, posted by David Wallis on Fri Jun 5 23:10:27 2015
|
Auto-saving does not seem to be working. In the config file, I have the following:
Save drafts = 1
Autosave = 10 |
option transfer, posted by Neal Grafton on Fri Jun 5 11:52:43 2015
|
| Can the chosen text in a dropdown menu be automatically transfered (copied) to this Text box? |
Re: option transfer, posted by Stefan Ritt on Fri Jun 5 12:01:01 2015
|
No.
Neal
Grafton wrote:
Can the chosen text in a dropdown menu be automatically transfered |
|
Re: option transfer, posted by Neal Grafton on Fri Jun 5 13:06:22 2015
|
OK Thanks
I was trying to save the operator repeatedly typing in standard messages.
|
|
Re: option transfer, posted by Stefan Ritt on Fri Jun 5 13:19:43 2015
|
There are browser extensions for that like "Autofill Forms" for Firefox. You can even link text templates to a single key.
Neal
Grafton wrote:
OK Thanks |
|
Re: option transfer, posted by Andreas Luedeke on Fri Jun 5 19:35:34 2015
|
Why would you transfer the message to the text box?
You can have a "Message" attribute, which is an option
list.
If the first option "Custom" is chosen, then you get an additional field "Custom Message".
We have
an attribute "Entry type", there we could add the type "Message", if the attribute should not exist for other types of entries.
As |
ELOG Version field in elogs/Forum, posted by Andreas Luedeke on Fri May 29 09:38:40 2015
|
Hi Stefan,
could we change the format of the "ELOG Version" field in this logbook, that one can enter the full git revision
number?
|
|
Re: ELOG Version field in elogs/Forum, posted by Stefan Ritt on Fri Jun 5 10:18:38 2015
|
> Hi Stefan,
> could we change the format of the "ELOG Version" field in this logbook, that one can enter the full git revision
> number?
|
|
Duplicate: LDAP docs, posted by Stephen G on Thu Jun 4 00:10:32 2015
|
This is a duplicate, made by mistake.
Could someone point me to the LDAP configuration docs, I searched to no avail. I'm sure there is some big red ldap config button it, |
|
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. |