Re: drag and drop attachments not working with web server authentication, posted by Stefan Ritt on Tue Jan 12 21:07:59 2016
|
Have a look here: elog:68014
Devin
Bougie wrote:
Hello, The "Drop attachments here..." section does not work when |
|
Re: drag and drop attachments not working with web server authentication, posted by Devin Bougie on Tue Jan 12 21:13:54 2016
|
Thanks, Stefan. I read that before asking my question, but didn't see a resolution in that thread. I am already at 3.1.1, and I am testing
on a clean installation. Are you saying that the solution is in the development branch after the release of 3.1.1?
|
|
Re: drag and drop attachments not working with web server authentication, posted by Stefan Ritt on Tue Jan 12 21:19:25 2016
|
No. What the thread says is first try this forum, see if you can drag and drop here. If not, you have a problem on your browser. If yes, you have somewhere
some old JavaScript file around. Might be in the cache of your browser.
Devin |
|
Re: drag and drop attachments not working with web server authentication, posted by Devin Bougie on Tue Jan 12 21:31:42 2016
|
Yeah, I had tried that and it did work in your demo forum. It just didn't work in mine with authentication = webserver, even with a clean
browser profile. |
|
Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 08:37:42 2016
|
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. |
|
Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 10:27:21 2016
|
Yeah, I found the RSS feed feature, but I could not get ETags/Last-Modified header fields which meant that I'd have to read and parse the entire
feed every time. Maybe I made a mistake and they do work, but if not, I think it would make sense to implement as it should save work for both the server
and the client. |
|
Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 10:29:54 2016
|
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 |
|
Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 17:04:34 2016
|
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 |