Re: Show attachments = 0, posted by Eric Quintero on Fri Oct 16 00:24:50 2015
|
Hm, looking through the source, there are many many places where PDF files are treated differently than strictly image filetypes (PNG, etc.). This makes
sense in the context of multi-page documents.
Still, I like using PDFs for vector plots... I suppose I should also confess to the following modification I've made to my ELOG for treating |
restrict edit time and autosave, posted by Kester Habermann on Fri Oct 30 18:20:22 2015
|
Hello,
When using restrict edit time together with autosave, there is the following problem: The counter for restrict edit time seems to start after
the autosave. If the time is up, it is no longer possible to submit the report. |
|
Re: restrict edit time and autosave, posted by Andreas Luedeke on Mon Nov 2 08:41:20 2015
|
Hi Kester,
yes, I did run into the same problem, that I could not even delete old drafts due to our restrict edit time.
We
allow anonymous submissions in our operation logbooks. After a while drafts of unsubmitted messages just pile up; and I need to remove them as administrator.
While
I can do that easily for anonymous drafts, I cannot do that for drafts of other users: I don't easily see those drafts.
It would be really |
|
Re: Find empty attributes, posted by Andreas Luedeke on Wed Feb 17 18:08:53 2016
|
It is possible for normal string attributes: the regular expression pattern "^$" can be used to search for an empty string.
E.g.
in this Forum "ELOG Version" is a required attribute, and should never be empty. But if you search for:
https://midas.psi.ch/elogs/Forum/?mode=threaded&reverse=0&reverse=1&npp=8&ELOG+Version=^%24
you'll
find a couple of entries from a time where it apparently wasn't a required attribute.
Cheers
Andreas
|
|
Re: Find empty attributes, posted by Stefan Ritt on Wed Feb 17 18:33:18 2016
|
Cool, I didn't know that trick myself, thanks for sharing.
Andreas
Luedeke wrote:
It is possible for normal string attributes: the regular expression |
Width of text field, posted by Edward Diehl on Tue Mar 22 18:28:03 2016
|
I use a elog which has a text field to show log entries: https://classis01.roma1.infn.it/elog/calib/ In the "Summary"
view there are only 3 lines of about 40 characters shown, so often the entry is cut off even though there is plenty of space in the text box for longer
lines. To see the full entry you must click on the ID number. Is there any way to configure the Text box to show longer lines? |
|
Re: Width of text field, posted by Andreas Luedeke on Wed Mar 23 11:40:52 2016
|
Did you try the options
Summary lines = x
Summary line length = x
as
documented in https://midas.psi.ch/elog/config.html#flags ? |
|
How to enforce line breaks in plain text entries?, posted by Andreas Luedeke on Wed Apr 27 14:07:52 2016
|
We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
entries made during the shift and files the printouts. If one entry in the shift was plain text without
appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the width
|