Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 717 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  68146   Fri Oct 16 00:24:50 2015 Reply Eric Quinteroericq@caltech.eduQuestionAll3.0.0-70b274bRe: Show attachments = 0

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 PDFs like images in drag-and-drop uploading. 

--- a/scripts/ckeditor/plugins/dndfiles/plugin.js
+++ b/scripts/ckeditor/plugins/dndfiles/plugin.js
@@ -142,7 +142,7 @@ CKEDITOR.plugins.add( 'dndfiles', {
                                                                return;

                                                        if(src.indexOf(".png") >= 0 || src.indexOf(".jpg") >= 0 || src.indexOf(".jpeg") >= 0
-                           || src.indexOf(".gif") >= 0 || src.indexOf(".svg") >= 0) { // This is an image
+                           || src.indexOf(".gif") >= 0 || src.indexOf(".svg") >= 0 || src.indexOf(".pdf") >= 0) { // This is an image
                                                                html += '<a href = ' + src + '><img src = "' + thumb + '">' + '</a>';
                                                        } else {        // this is not an image
                                                                // Server appends 14 characters in front of the name so we should remove them

  68173   Fri Oct 30 18:20:22 2015 Entry Kester Habermannkester.habermann@gmail.comBug reportAll3.1.1restrict edit time and autosave

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.
It is also not possble to edit old drafts if restrict edit has elapsed since the creation of the save.
Autosave is definitively a nice new feature. However, I think it would be better if the counter for restrict edit time only started after the "submit" of the report and allowed edits to drafts no matter how old they are. As it is one needs to either set a really high value for restrict edit time or turn off autosave.
The issue seems to be related to: https://midas.psi.ch/elogs/Forum/68103

Regards

Kester

 

 

 

  68176   Mon Nov 2 08:41:20 2015 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportAll3.1.1Re: restrict edit time and autosave
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 nice, if drafts would be handled different then other entries regarding "Restrict edit time" as you've suggested.
Cheers, Andreas
Kester Habermann wrote:

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.
It is also not possble to edit old drafts if restrict edit has elapsed since the creation of the save.
Autosave is definitively a nice new feature. However, I think it would be better if the counter for restrict edit time only started after the "submit" of the report and allowed edits to drafts no matter how old they are. As it is one needs to either set a really high value for restrict edit time or turn off autosave.
The issue seems to be related to: https://midas.psi.ch/elogs/Forum/68103

Regards

Kester

 

 

 

 

  68262   Wed Feb 17 18:08:53 2016 Reply Andreas Luedekeandreas.luedeke@psi.chInfoAllELOG V3.1.1-3f3Re: Find empty attributes
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:
you'll find a couple of entries from a time where it apparently wasn't a required attribute.
Cheers
Andreas
Arno Teunisse wrote:

Want to use the find function from ELOG to search for empty fields ( Attributes that are not defined ) 
How to do that ? 
Could not find it in the Forum.
 

Greetings Arno Teunisse
 

 

 

  68263   Wed Feb 17 18:33:18 2016 Reply Stefan Rittstefan.ritt@psi.chInfoAllELOG V3.1.1-3f3Re: Find empty attributes

Cool, I didn't know that trick myself, thanks for sharing.

Andreas Luedeke wrote:
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:
you'll find a couple of entries from a time where it apparently wasn't a required attribute.
Cheers
Andreas
Arno Teunisse wrote:

Want to use the find function from ELOG to search for empty fields ( Attributes that are not defined ) 
How to do that ? 
Could not find it in the Forum.
 

Greetings Arno Teunisse
 

 

 

 

  68291   Tue Mar 22 18:28:03 2016 Question Edward Diehldiehl@umich.eduQuestionAllELOG V2.9.2-245Width of text field

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?   Thank you.

 

  68292   Wed Mar 23 11:40:52 2016 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionAllELOG V2.9.2-245Re: Width of text field

Did you try the options

  • Summary lines = x
  • Summary line length = x

as documented in https://midas.psi.ch/elog/config.html#flags ?

It works nicely with plain text entries; it has some difficulties with HTML, since it has to remove the formatting and that disturbs the line count.

Cheers Andreas

Edward Diehl wrote:

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?   Thank you.

 

 

  68304   Wed Apr 27 14:07:52 2016 Question Andreas Luedekeandreas.luedeke@psi.chRequestAllV3.1.1How to enforce line breaks in plain text entries?
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
of this line and either the printout is cut off at the right side, or the whole content is scaled down to very
tiny scale, which makes it unreadable.

Is there a way to enforce line breaks in plain text entries?
ELOG V3.1.5-3fb85fa6