If a Required Attribute starts with a number – No CKEditor, posted by David Dunne on Fri Nov 27 06:53:54 2015
|
Hello,
Is the below an issue or am I doing something incorrectly?
Creating an attribute starting with a number and then including that attribute in
the Required Attribute list prevents access to the CKEditior.
This appears to be the case at least with FreeBSD (10.2 Rel) using Elog V3.1.0 and Windows
7 with Elog V3.1.1-3f311c5.
The problem can be recreated using the Elog supplied sample config and adding the necessary attribute, sample config showing |
Monitoring a logbook for changes, posted by Johan Forsberg on Tue Jan 12 15:06:42 2016
|
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 |
Re: Monitoring a logbook for changes, posted by Stefan Ritt on Tue Jan 12 16:10:34 2016
|
Use automatic email notifications or RSS feeds. Read the manual for that.
Stefan
Johan |
|
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 |
|
Re: Monitoring a logbook for changes, posted by Stefan Ritt on Wed Jan 13 17:21:56 2016
|
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 |