Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 717 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded | Hide attachments  Show all entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 716, 717, 718 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  68098   Thu Aug 20 14:23:43 2015 Reply Edmund Hertleedmund.hertle@kit.eduInfoAll3.1.1Re: Version 3.1.1 of elog has been released

There seems to be a small problem with the new "Date/Time format <attribute>" implementation. It works great for the detailed view of a single entry:

But fails to work on the list view (same entry, the Date column is formated as it should):

Relevant config part:

Time format Time Start = %H:%M:%S
Time format Time End = %H:%M:%S

Stefan Ritt wrote:

Version 3.1.1, released August 4th, 2015

  • Updated CKEditor to version 4.5.1

  • Implemented "Date/Time format <attribute> = ..."

  • Implemented "Use Email Subject Edit = ..."

  • Replaced "Back" by "Delete" button

  • Fixed many issues with Draft Messages

  • CSS file is now in *addition* to the default file elog.css

  • Added LDAP documentation

  • Added "Logout to URL = ..." option

  • Added description of Apacher server authentication

 

  68099   Thu Aug 20 15:52:26 2015 Reply Stefan Rittstefan.ritt@psi.chInfoAll3.1.1Re: Version 3.1.1 of elog has been released

Thanks for reportung that bug. I fixed it in revision f828049.

Edmund Hertle wrote:

There seems to be a small problem with the new "Date/Time format <attribute>" implementation. It works great for the detailed view of a single entry:

But fails to work on the list view (same entry, the Date column is formated as it should):

Relevant config part:

Time format Time Start = %H:%M:%S
Time format Time End = %H:%M:%S

 

  68105   Mon Aug 31 17:14:08 2015 Reply Eric Quinteroericq@caltech.eduQuestionAll3.0.0-70b274bRe: Show attachments = 0

The automatic hiding behavior is what I'm after, and I've discovered that it is only a problem for PDF attachments. I have reproduced this on the demo logbook on git revision f828049. 

I've taken a look at the source you mentioned, but as far as I can tell, it is just looking for the opening of the img tag in the HTML source, and I'm not sure why that is different for a PDF.

  68113   Mon Sep 7 12:44:42 2015 Entry Edmund Hertleedmund.blomley@kit.eduBug reportAll3.1.1Creating ELog Links not working properly in HTML Editor

Hey,

the syntax for creating links to other elog entries has a small issue in the HTML editor. The link will not be created properly if there are whitespaces in the name of the logbook. Using ELCode (or in a simple attribute field) the whitespaces can be replaced by "+", but this does not work in the HTML editor. The work-around would be to use ELCode mark-up instead of HTML.

Example 1 (this should work): elog:Contributions/47

Example 2 (this will not work): elog:Config+Examples/11

Example 3 (will also not work): elog:Config%20Examples/11

  Draft   Tue Sep 22 14:56:37 2015  Edmund Hertleedmund.hertle@kit.eduRequestAll3.1.1Suggestion for tooltips and/or comments

Hey,

if you define a Tooltip at the moment it is only displayed on the attribute. I would like it very much if it would also be displayed on the values (on the right column in the detailed view and on the whole column in the list view), since we are using the tooltips to define the units of the attribute and it would be nice to pop up when you hover a value.

As for the comment it would be nice to have a flag to also show the comment on the detailed view while looking at an entry. At the moment it is only showed when creating a new entry. Again we use this field to define the units.

This is an example of how we use these options:

attributes = Fill Number, Beam Current, Beam Energy, Beam Lifetime, RF Voltage S2, RF Voltage S4, RF Frequency, Synchrotron Frequency

Comment Beam Current = in mA
Comment Beam Energy = in GeV
Comment Beam Lifetime = in hh:mm
Comment RF Voltage S2 = in kV
Comment RF Voltage S4 = in kV
Comment RF Frequency = in MHz
Comment Synchrotron Frequency = in kHz

Tooltip Beam Current = in mA
Tooltip Beam Energy = in GeV
Tooltip Beam Lifetime = in hh:mm
Tooltip RF Voltage S2 = in kV
Tooltip RF Voltage S4 = in kV
Tooltip RF Frequency = in MHz
Tooltip Synchrotron Frequency = in kHz

Cheers

eddy

  68121   Tue Sep 22 15:04:55 2015 Idea Edmund Hertleedmund.hertle@kit.eduRequestAll3.1.1Suggestion for tooltips and/or comments

Hey,

if you define a Tooltip at the moment it is only displayed on the attribute. I would like it very much if it would also be displayed on the values (on the right column in the detailed view and on the whole column in the list view), since we are using the tooltips to define the units of the attribute and it would be nice to pop up when you hover a value.

As for the comment it would be nice to have a flag to also show the comment on the detailed view while looking at an entry. At the moment it is only showed when creating a new entry. Again we use this field to define the units.

This is an example of how we use these options:

attributes = Fill Number, Beam Current, Beam Energy, Beam Lifetime, RF Voltage S2, RF Voltage S4, RF Frequency, Synchrotron Frequency

Comment Beam Current = in mA
Comment Beam Energy = in GeV
Comment Beam Lifetime = in hh:mm
Comment RF Voltage S2 = in kV
Comment RF Voltage S4 = in kV
Comment RF Frequency = in MHz
Comment Synchrotron Frequency = in kHz

Tooltip Beam Current = in mA
Tooltip Beam Energy = in GeV
Tooltip Beam Lifetime = in hh:mm
Tooltip RF Voltage S2 = in kV
Tooltip RF Voltage S4 = in kV
Tooltip RF Frequency = in MHz
Tooltip Synchrotron Frequency = in kHz

Cheers

eddy

  68129   Mon Sep 28 06:29:57 2015 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportAll3.1.1Re: Creating ELog Links not working properly in HTML Editor

I can confirm this bug.

But I don't think this has to work as you've described it, when using the HTML editor: if you use HTML, you can use the link feature of the editor.
But that link feature does currently not work at all with internal elog references, not even a simple elog:1">elog:1 (as you can see here). I suppose there is some more work to do for Stefan on that ;-)
 
Cheers, Andreas
Edmund Hertle wrote:

Hey,

the syntax for creating links to other elog entries has a small issue in the HTML editor. The link will not be created properly if there are whitespaces in the name of the logbook. Using ELCode (or in a simple attribute field) the whitespaces can be replaced by "+", but this does not work in the HTML editor. The work-around would be to use ELCode mark-up instead of HTML.

Example 1 (this should work): elog:Contributions/47

Example 2 (this will not work): elog:Config+Examples/11

Example 3 (will also not work): elog:Config%20Examples/11

 

  68130   Mon Sep 28 06:45:03 2015 Reply Andreas Luedekeandreas.luedeke@psi.chRequestAll2.9.0(elogd)Re: elog client overwriting attached files when editing existing log

The "elog" command has no "append" feature. You can either create a new entry, or you can overwrite an old entry. Therefore this is not a bug but the intended bahaviour.

I admit that the documentation is misleading, since overwriting an existing entry is called "editing":

[-e <id>]                Edit existing message

I interprete your posts that you would like to have two new features for the "elog" command:

  • to append text to the body of an existing entry
  • to add additional attachments to an existing entry

Without a specific application in mind I would like to add a request (for consistency):

  • to modify a specific attribute of an existing entry.

Cheers, Andreas

Edmund Hertle wrote:

Hey,

I think this is a "problem" of the elog client, since it simply replaces the data. In most cases this is what you want, but since I wanted to have the option to append to the acutal message I built a function to first read-back the entry and add to the message instead of replacing it.

I just played around a bit and found that the attachments will be even disconnected, if you do not specify the -f parameter but just edit a different part of this entry.

A work-around for this is tricky. I tried to write to the "Attachment" attribute directly (-a "Attachment=Filename'), since then you coud read back the data first and manually add the filenames again. But this does not work.

Since the attachments are not actually removed, the only option I see is to modify the logbook file entry on the server by manually re-adding the filenames to the "Attachment: " line.

Joseph McKenna wrote:

Using the elog client to upload atachments, I can successfully send attachments to an existing elog, however the existing attachments are lost.

I have tested using the elog client version 3.1.1 and elog client version 2.9.2 sending to elogd 2.9.0

elog -h localhost -p 8080 -l test -f  file1.png -f file2.png -e 249 -v -x

This works great, the text contained in the elog post is retained, however all attachments are lost and replaced with those sent by this command.

Can anyone provide some tips? I am not sure if its a problem with the client or server.

Thank you in advance!

Joseph


            

 

 

Goto page Previous  1, 2, 3 ... 716, 717, 718 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6