ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68131
|
Mon Sep 28 11:58:11 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.9.0(elogd) | Re: elog client overwriting attached files when editing existing log | You are right. "Edit" should be more like "Replace". I changed that in the documentation.
I acknowledge the request to replace or append only a specific attribute or attachment, and put it on my to-do list.
Stefan
Andreas Luedeke wrote: |
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
|
|
|
|
68132
|
Mon Sep 28 12:05:04 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 3.1.1 | Re: Creating ELog Links not working properly in HTML Editor | Right, spaces won't work. But others work. Andreas, if you just put elog:1 without any link etc. just as plain text, it will be converted automatically into a link.
A workaround is to explicitly specify a link to an elog entry. Press the link button from the editor toolbar, enter a name and copy the full URL from the browser address bar, like here: https://midas.psi.ch/elogs/Forum/68129. If you switch to "Source" (Top left editor toolbar, you can changed the link name manually, like here.
Andreas Luedeke wrote: |
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
|
|
|
68133
|
Tue Sep 29 08:50:30 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | All | 3.1.1 | Re: Creating ELog Links not working properly in HTML Editor | Hi Stefan,
yes, I know that a plain text " elog:1" works in the HTML editor, too.
But if you put " elog:1" in the URL field of the link dialog, then ELOG screws up: you get the text
and the link points to link type "URL", protocol "<other>", URL "1".
Or more precisely, the HTML source looks like the following:
<a href="1">elog.1</a>"><a href="1">elog.1</a>
(I've replaced ":" by "." here in the source, to avoid another iteration of links by ELOG).
That is not what I would have expected:
either it should have been remained unchanged, or it should point to the right URL of the entry elog:1 (the latter case preferred :-).
Cheers, Andreas
Stefan Ritt wrote: |
Right, spaces won't work. But others work. Andreas, if you just put elog:1 without any link etc. just as plain text, it will be converted automatically into a link.
A workaround is to explicitly specify a link to an elog entry. Press the link button from the editor toolbar, enter a name and copy the full URL from the browser address bar, like here: https://midas.psi.ch/elogs/Forum/68129. If you switch to "Source" (Top left editor toolbar, you can changed the link name manually, like here.
Andreas Luedeke wrote: |
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
|
|
|
|
68136
|
Wed Sep 30 10:23:30 2015 |
| Edmund Hertle | edmund.hertle@kit.edu | Request | All | 2.9.0(elogd) | Re: elog client overwriting attached files when editing existing log | Hey,
the edit/replace feature is already capable of just replacing individual attributes. I already make heavy use of this feature:
1. One entry is created with some measurement parameters
2. A different script is running processing the measurement data making a plot and a fit
3. Two fit parameters and the attachment are added to the original elog entry (all other attributes and values still exist afterwards)
But the problem here is, that although it does work for normal attrbutes, the attachments will always be replaced (=> removed) if you use this command. Since I only add the attachment on the edit it does work for me.
Btw the documentation on the homepage is also misleading about the -w command, since in the actual version it does nothing with any password but just reads back the whole elog entry (which I use to manually append the main message)
Andreas Luedeke wrote: |
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
|
|
|
|
68146
|
Fri Oct 16 00:24:50 2015 |
| Eric Quintero | ericq@caltech.edu | Question | All | 3.0.0-70b274b | Re: 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 |
| Kester Habermann | kester.habermann@gmail.com | Bug report | All | 3.1.1 | restrict 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 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | All | 3.1.1 | Re: 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 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | All | ELOG V3.1.1-3f3 | Re: 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
|
|
|