Re: Entries disappear after editing + UTF16 problem, posted by Stefan Ritt on Tue Feb 6 10:23:26 2018
|
The -bd... number must be from the .apk package, which I don't have control over. You have to check the elog git hash code. You see it at the bottom
of each elog web page. For this forum server, it's ELOG V3.1.2-7933898 with
7 digit number at the end. |
|
Re: Entries disappear after editing + UTF16 problem, posted by Stefan Ritt on Wed Feb 7 14:26:01 2018
|
Tell me your current seven digit number and I can check if your version is too old.
Peter
K wrote:
yes, that is exactly where I got this V3.1.2-bd75964 version! |
|
Re: User passwords not configurable with loacl passwordfile, posted by Stefan Ritt on Tue Feb 27 15:32:30 2018
|
Have you configures user-level access via
password file = anyfile.pwd
Can your elogd server write to that file?
If yes, can you please post your config file? |
|
Re: User passwords not configurable with loacl passwordfile, posted by Stefan Ritt on Mon Mar 5 14:29:26 2018
|
What happens when you don't use Kerberos authentication?
KaterKarlo99
wrote:
I'm afraid that there is something wrong because each user will be written |
|
Re: Problem with special character "č", posted by Stefan Ritt on Tue Mar 6 15:08:23 2018
|
Actually unicode characters are converted by your browser into HTML code (such as Č) where 268 decimal = 10C hex. elog just writes to file what
it gets from the browser. When an existing elog entry gets shown by the browser, the code is translated back to the character. Why do you care what is
written to the log file? If you use scripts or so to parse your log files, you have to adapt them to correctly decode HTML encoded characters. This is |
|
Re: Problem with special character "č", posted by Stefan Ritt on Tue Mar 6 15:54:23 2018
|
In the attribe filed, HTML code is not allowed for security reasons. If you want to bypass this (on your own risk), put
allow html = 1
into your config file. |
|
Re: how to insert images inline, posted by Stefan Ritt on Tue Mar 6 17:28:46 2018
|
Before you click OK on your point 4, click on "Send to Server".
Stefan
Piotr |
Re: Problem with special character "č", posted by Stefan Ritt on Fri Mar 16 12:46:09 2018 
|
I had time to look at the problem in detail. I found that a &#xxx; sequence is not correctly identified as HTML code, and thus displayed in plain
when used in an attribute. I fixed it in the current git revision and now it looks find in attribute (see attachment). Can you give it a try? Please note
that you need "Allow HTML = 1" in your config file. |