|
|
|
Demo
Discussion
|
|
Forum
Config Examples
Contributions
Vulnerabilities
|
| Discussion forum about ELOG, Page 240 of 801 |
Not logged in |
 |
|
|
|
|
| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67857
|
Fri Apr 10 08:37:19 2015 |
 | Oliver Kleinau | oliver.kleinau@it.niedersachsen.de | Question | Linux | 3.1 | Re: Max Logbooks for Email notify | 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
|
|
|
67856
|
Wed Apr 8 11:40:27 2015 |
 | Oliver Kleinau | oliver.kleinau@it.niedersachsen.de | Question | Linux | 3.1 | Max Logbooks for Email notify | 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
|
|
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 |
|
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. |
|
67853
|
Wed Apr 1 18:39:14 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | ELOG V2.9. | Re: Strange browser behaviour with chrome? | |
Proof of principle ;-) |
|
67852
|
Wed Apr 1 18:31:28 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | ELOG V2.9. | Re: Strange browser behaviour with chrome? |
| Stefan Ritt wrote: |
| 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. |
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. |
|
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. |
|
67847
|
Wed Apr 1 11:01:14 2015 |
| Tim Schelfhout | tim.schelfhout@fixbrussel.be | Question | Windows | ELOG V2.9. | Re: Strange browser behaviour with chrome? |
Thank you all of you for your notes ...
Anyway I have no time at the present to debug this ... at the level of configuration file.
I discovered however that the Incognito Mode of Chrome does NOT seem to have this problem??
Chrome version is 41.0.2272.101
Don't know why ??? ... tried disabling all of the added extensions in chrome but to no avail.
Don't know what else can be different in both modes.
| Andreas Luedeke wrote: |
| Stefan Ritt wrote: | 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 |
Just my two cent:
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.
You could try to select the very same entries in both browsers, to see if it does depend on the specific entry content.
If the problem persists, then I would suggest that you post the following:
- a minimal configuration for a logbook that reproduces the problem; and
- the actual entries, exported in XML or RAW format; and
- screenshots on how it displays with IE (add version number) and with Chrome (add version number).
Cheers
Andreas |
|