| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68233
|
Wed Jan 13 19:22:35 2016 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | ELOG V3.1.0-241 | Re: Monitoring a logbook for changes | You look here: http://midas.psi.ch/elog/config.html and scroll down to "Execute New". I wonder how you ever could run elog without looking at that page.
| Tamas Gal wrote: |
|
I'm probably too tired or I don't know, but of course I looked at the user's guide and the admin's guide but did not found anything about this ;-) Is there another documention which I missed somehow?
| Stefan Ritt wrote: |
|
In the documentation of course :-)
| Tamas Gal wrote: |
|
Where is this feature documented?
| Stefan Ritt wrote: |
|
You guys know that there is the possibility to execute an arbitrary script on each submission of a new messge? Just use "Execute new = <script>". In the script you have access to all parameters of the message. That's maybe simple than to watch the file set.
|
|
|
|
|
|
68234
|
Wed Jan 13 19:26:35 2016 |
| Tamas Gal | tgal@km3net.de | Question | Linux | ELOG V3.1.0-241 | Re: Monitoring a logbook for changes | OK thanks I'll check that out. I did not configure ELOG by myself, I only use it and wrote the Slack plugin ;-)
| Stefan Ritt wrote: |
|
You look here: http://midas.psi.ch/elog/config.html and scroll down to "Execute New". I wonder how you ever could run elog without looking at that page.
| Tamas Gal wrote: |
|
I'm probably too tired or I don't know, but of course I looked at the user's guide and the admin's guide but did not found anything about this ;-) Is there another documention which I missed somehow?
| Stefan Ritt wrote: |
|
In the documentation of course :-)
| Tamas Gal wrote: |
|
Where is this feature documented?
| Stefan Ritt wrote: |
|
You guys know that there is the possibility to execute an arbitrary script on each submission of a new messge? Just use "Execute new = <script>". In the script you have access to all parameters of the message. That's maybe simple than to watch the file set.
|
|
|
|
|
|
|
68235
|
Wed Jan 13 20:08:04 2016 |
| Johan Forsberg | johan.forsberg@maxlab.lu.se | Question | Linux | ELOG V3.1.0-241 | Re: Monitoring a logbook for changes | Aha, that's interesting too! I'll have to look more carefully through the documentation... :)
| Stefan Ritt wrote: |
|
You guys know that there is the possibility to execute an arbitrary script on each submission of a new messge? Just use "Execute new = <script>". In the script you have access to all parameters of the message. That's maybe simple than to watch the file set.
| Tamas Gal wrote: |
|
I just noticed that there are multiple messages per file, so I have to adapt the parser. I'll update this thread when I'm done!
| Johan Forsberg wrote: |
|
Yeah, I suppose something like that would be both faster and more efficient than polling ELOG itself. Fortunately the ELOG disk format looks easily parsed.
Thanks for the pointer!
| Tamas Gal wrote: |
|
I recommend monitoring directly on the server. Here is an example of a very simply Python script (https://github.com/tamasgal/elog-slack) which monitors the files very efficiently and immediately pushes notifications to Slack (slack.com). Just look at the code, it's pretty straight forward and very easy to adapt it to other (web) services.
Btw. here is an ELOG entry of it https://midas.psi.ch/elogs/Forum/68224
| Johan Forsberg wrote: |
|
Hi again!
I've another need that you probably already thought of :)
I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).
Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.
Cheers,
Johan
|
|
|
|
|
|
|
68239
|
Tue Jan 19 22:03:36 2016 |
 | Devin Bougie | devin.bougie@cornell.edu | Bug report | Linux | 3.1.1 | drag and drop attachments only working for admins if "restrict edit = 1" | I'm finally able to reproduce this, and my initial description was incorrect. If we have "restrict edit = 1", only an "Admin user" can use the "Dop attachments here..." or the "Image" button in the CKEditor. The old "Choose File," "Upload" buttons, however, works just fine for anyone.
If we have "restrict edit = 0", anyone can upload an attachment using all three interfaces.
This is very reproducible by toggling restrict edit in the global section or for an individual logbook.
Devin |
|
68240
|
Wed Jan 20 20:38:17 2016 |
| Devin Bougie | devin.bougie@cornell.edu | Bug report | Linux | 3.1.1 | entry does not appear in list while it is being edited | When an entry is being edited, it does not appear in the list once it's been autosaved or the editor manually clicks on "Save." This has been reproduced in the "Linux Demo" forum on this site, as well as on a clean installation of the 3.1.1 binary on EL6.
It would be great if there was a configuraiton option to control this, but I haven't found it yet. To reproduce:
- edit an existing entry
- click on "Save"
- view the list for that logbook, and the entry will be hidden until you click "Submit"
Obviously this becomes a problem when a user edits an entry, but navigates away from the browser window before submitting the changes.
Any suggestions would be greatly appreciated.
Many thanks,
Devin |
|
68241
|
Thu Jan 21 11:39:18 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | 3.1.1 | Re: entry does not appear in list while it is being edited | Hi Devin,
this is the intended bevaviour, there is nothing wrong with that.
Only a submitted entry should be visible to the world.
If you would have played a little bit longer, you would have found out yourself how you'll get access again to this so-called "draft" entry after closing the browser window:
as soon as you attempt to create - as the same user - an new entry, you'll be asked if you want to continue editing your old draft entry instead.
I've attached a screenshot of this "pending draft" menu, as it has been shown for this entry before I've submitted it.
Kind Regards, Andreas
PS: You gave a very clear "failure" description: what you did, what you expected to happen and what you've observed what happened instead. Well done: that deserves a swift answer! 
| Devin Bougie wrote: |
|
When an entry is being edited, it does not appear in the list once it's been autosaved or the editor manually clicks on "Save." This has been reproduced in the "Linux Demo" forum on this site, as well as on a clean installation of the 3.1.1 binary on EL6.
It would be great if there was a configuraiton option to control this, but I haven't found it yet. To reproduce:
- edit an existing entry
- click on "Save"
- view the list for that logbook, and the entry will be hidden until you click "Submit"
Obviously this becomes a problem when a user edits an entry, but navigates away from the browser window before submitting the changes.
Any suggestions would be greatly appreciated.
Many thanks,
Devin
|
|
| Attachment 1: elog-pending-draft.png
|
|
|
68242
|
Thu Jan 21 16:00:30 2016 |
| Devin Bougie | devin.bougie@cornell.edu | Bug report | Linux | 3.1.1 | Re: entry does not appear in list while it is being edited | Thanks, Andreas. I was aware of the "pending draft" menu, and I am aware that you can manually browse to an entry even if it doesn't appear in the list. However, for our operations group it is a requirement that any saved entry appears in the list, even if it's in the process of being edited. We won't be able to upgrade until this is possible.
Previous releases didn't have this problem, so hopefully it won't be too difficult to address with a new configuration option. Please let me know if there's something I should do to submit an official feature request / bug report.
Thanks again,
Devin
| Andreas Luedeke wrote: |
|
Hi Devin,
this is the intended bevaviour, there is nothing wrong with that.
Only a submitted entry should be visible to the world.
If you would have played a little bit longer, you would have found out yourself how you'll get access again to this so-called "draft" entry after closing the browser window:
as soon as you attempt to create - as the same user - an new entry, you'll be asked if you want to continue editing your old draft entry instead.
I've attached a screenshot of this "pending draft" menu, as it has been shown for this entry before I've submitted it.
Kind Regards, Andreas
PS: You gave a very clear "failure" description: what you did, what you expected to happen and what you've observed what happened instead. Well done: that deserves a swift answer!
| Devin Bougie wrote: |
|
When an entry is being edited, it does not appear in the list once it's been autosaved or the editor manually clicks on "Save." This has been reproduced in the "Linux Demo" forum on this site, as well as on a clean installation of the 3.1.1 binary on EL6.
It would be great if there was a configuraiton option to control this, but I haven't found it yet. To reproduce:
- edit an existing entry
- click on "Save"
- view the list for that logbook, and the entry will be hidden until you click "Submit"
Obviously this becomes a problem when a user edits an entry, but navigates away from the browser window before submitting the changes.
Any suggestions would be greatly appreciated.
Many thanks,
Devin
|
|
|
|
68243
|
Fri Jan 22 10:12:33 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.1.1 | Re: entry does not appear in list while it is being edited | I have a question here. You say "previsous releases didn't have this problems". Well, they did not have the auto-save feature. You can turn this off if you like with "autosave = 0". This also removes the "Save" button so elog behaves exactly as before.
I decided NOT to show draft entries in the list, because these are entries currently under editing, and maybe the editor does not want others to see a half finished entry. Actually I had this feature initially and people complained about seing half finished messages in the list. Previously, when there was no "Save" button, new entries where not visible on the list because nothing was submitted at all, and I guess that was ok with you. So would reverting to the old functionality via "autosave = 0" make you happy? Of course you then loose the autosave functionality. So if people enter a long entry, and surf away from the page or the browser crashes, the entry is lost.
| Devin Bougie wrote: |
|
Thanks, Andreas. I was aware of the "pending draft" menu, and I am aware that you can manually browse to an entry even if it doesn't appear in the list. However, for our operations group it is a requirement that any saved entry appears in the list, even if it's in the process of being edited. We won't be able to upgrade until this is possible.
Previous releases didn't have this problem, so hopefully it won't be too difficult to address with a new configuration option. Please let me know if there's something I should do to submit an official feature request / bug report.
Thanks again,
Devin
| Andreas Luedeke wrote: |
|
Hi Devin,
this is the intended bevaviour, there is nothing wrong with that.
Only a submitted entry should be visible to the world.
If you would have played a little bit longer, you would have found out yourself how you'll get access again to this so-called "draft" entry after closing the browser window:
as soon as you attempt to create - as the same user - an new entry, you'll be asked if you want to continue editing your old draft entry instead.
I've attached a screenshot of this "pending draft" menu, as it has been shown for this entry before I've submitted it.
Kind Regards, Andreas
PS: You gave a very clear "failure" description: what you did, what you expected to happen and what you've observed what happened instead. Well done: that deserves a swift answer!
| Devin Bougie wrote: |
|
When an entry is being edited, it does not appear in the list once it's been autosaved or the editor manually clicks on "Save." This has been reproduced in the "Linux Demo" forum on this site, as well as on a clean installation of the 3.1.1 binary on EL6.
It would be great if there was a configuraiton option to control this, but I haven't found it yet. To reproduce:
- edit an existing entry
- click on "Save"
- view the list for that logbook, and the entry will be hidden until you click "Submit"
Obviously this becomes a problem when a user edits an entry, but navigates away from the browser window before submitting the changes.
Any suggestions would be greatly appreciated.
Many thanks,
Devin
|
|
|
|
|