| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67841
|
Fri Mar 27 08:24:47 2015 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.0.0 | Re: Permission to view | No.
| Banata Wachid Ridwan wrote: |
|
so if that is the solution, all user that not allowed cannot login and cannot fill logbook
in my case, user still can login and fill logbook but cannot see other user's data on the same logbook, so user only see their own data.
but few members have a special permission to see all.
is that possible?
| Stefan Ritt wrote: |
|
You need
Password file = logbook.pwd
Login user = <name of allowed user(s)>
|
|
|
|
67843
|
Mon Mar 30 17:48:06 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | ELOG V2.9. | Re: Strange browser behaviour with chrome? | The (correct) display tells me that the colours are user-defined, probably by the configuration option
Style <attribute> <value> = <style>
which selects different styles for different rows. Now I do not know why your browser should change behaviour all over sudden, but I would double check the configuration. Like removing all style additions in the config file, then try again, then add one by one. There could also be a class defined with the "style" option which has not been added to the default style file themes directory of the elog installation.
Stefan |
|
67845
|
Tue Mar 31 11:44:27 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | ELOG V2.9. | Re: Strange browser behaviour with chrome? |
| Andreas Luedeke wrote: | | the content of a particular entry can change the rendering. If you have an HTML end tag like </table> or </font> in your entry, then the display after that entry may be spoiled. |
Actually not. If you have HTML statements in entries, they will be rendered using escape characters (like </table> -> </table>). This is necessary to avoid cross-side-script vulnerabilities (XSS). If this is not working in some case, let me know and I have to fix it. The only exception is if you explicitly allow this via Allow HTML = 1 |
|
67848
|
Wed Apr 1 11:41:31 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | ELOG V2.9. | Re: Strange browser behaviour with chrome? |
| Andreas Luedeke wrote: | If the content has been added with the "elog" command as HTML then it can contain mismatching HTML tags, can't it?
I don't see how this could be avoided by ELOG, unless you want to do a full HTML syntax check of all new and modified entries. |
It works also with entries submitted by the "elog" command. The reason is that for the OUTPUT, all "<" characters are transformed into >, which "inactivates" any HTML code, no matter where it came from. |
|
67854
|
Wed Apr 1 20:25:21 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | ELOG V2.9. | Re: Strange browser behaviour with chrome? </table> |
| Andreas Luedeke wrote: | Now I'm confused: if I create an entry with "elog -n 2 ...", then I put HTML code into elog and it is displayed as HTML. This HTML code does NOT convert a "<" into "<", otherwise you could not display any HTML.
But of course this code can be wrongly formatted, for example it can contain a </table> tag without a <table> tag before it. This will definitely spoil the display in ELOG, and that was what I was refering to.
I agree that html tags in plain text entries will not have this problem. |
Sure, in the main body text you can insert arbitrary HTML if this type of encoding is not prohibited. The < encoding I meant was for attribute values. Proof of principe above in the Subject field. |
|
67855
|
Thu Apr 2 15:44:33 2015 |
 | Stefan Ritt | stefan.ritt@psi.ch | Info | All | 3.1.0 | ELOG Version 3.1.0 announcement | This is an announcement for the ELOG version 3.1.0 being released just now. Among several bug fixes and an improved Drag & Drop interface for attachments, it contains a long awaited "autosave" feature.
Let's assume that you write an ELOG entry, and keep the window open for a longer time (like to write some shift notes over several hours). If your browser crashes or closes for some reason, you will loose your entered text. To avoid that, ELOG starting from version 3.1.0 has an autosave feature. Whenever you enter some text, it is saved in the background as a draft message to the server. If your browser is closed by accident, you always can go back to the logbook, click "New" and ELOG will tell you that there is a draft message and asks you if you want to edit it. When you edit and regularly submit this message, it becomes a "normal" entry and the draft flas is removed. In addition to the background saving, there is now also a "Save" button so you can manually save your text to the draft entry.
I have tested this to some extent, but I might not have seen all browser/OS combinations, so in case there is a problem, please report it here.
Happy Easter,
Stefan |
|
67861
|
Wed Apr 15 09:01:04 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | All | 3.1.0 | Re: ELOG Version 3.1.0 announcement | The changelog is here: http://midas.psi.ch/elog/download/ChangeLog
It is save to install the new version over the old one.
| Banata Wachid Ridwan wrote: |
|
congrats, any detail changelog? I assume in software packages?
is it save just install and overwrite the old version?
| Stefan Ritt wrote: |
|
This is an announcement for the ELOG version 3.1.0 being released just now. Among several bug fixes and an improved Drag & Drop interface for attachments, it contains a long awaited "autosave" feature.
Let's assume that you write an ELOG entry, and keep the window open for a longer time (like to write some shift notes over several hours). If your browser crashes or closes for some reason, you will loose your entered text. To avoid that, ELOG starting from version 3.1.0 has an autosave feature. Whenever you enter some text, it is saved in the background as a draft message to the server. If your browser is closed by accident, you always can go back to the logbook, click "New" and ELOG will tell you that there is a draft message and asks you if you want to edit it. When you edit and regularly submit this message, it becomes a "normal" entry and the draft flas is removed. In addition to the background saving, there is now also a "Save" button so you can manually save your text to the draft entry.
I have tested this to some extent, but I might not have seen all browser/OS combinations, so in case there is a problem, please report it here.
Happy Easter,
Stefan
|
|
|
|
67862
|
Wed Apr 22 13:40:19 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1 | Re: Max Logbooks for Email notify | Ok, I fixed this in the current GIT version. You might check if that works for you.
| Oliver Kleinau wrote: |
|
It was str variable in function process_http_request in elogd.c.
This should have the size of received buffer.
PROBLEM SOLVED!!!
| Oliver Kleinau wrote: |
|
It seems to be the GET buffer of the elog-Server. The GET statement is cut off after &sub_lb72=1&sub_ eg. 1000 chars.
| Oliver Kleinau wrote: |
|
Hi,
we've got 109 logbooks in Elog. Whenever I set a notify for all logbooks in configuration menu it is limited to 73 entrys. After saving the changes the rest of the entrys are cut off.
I've already searched in the sourcecode if I can find some limitation for that but without success.
When I change the password file by hand, it is working as long as I don't change anything in the configuration that rewrites the file.
Regards,
Oliver
|
|
|
|
|