Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 20:08:04 2016
|
Aha, that's interesting too! I'll have to look more carefully through the documentation... :)
Stefan
Ritt wrote:
You guys know that there is the possibility to execute an arbitrary |
Escape character [ or ] doesn't work within [url], posted by Don on Fri Jul 15 19:46:26 2016
|
Here is the problem:
[url=http://example.com?arrays[]=v1&arrays[]=v2]click here[/url]
How can I escape [] inside url tag? |
Re: Escape character [ or ] doesn't work within [url], posted by Andreas Luedeke on Mon Jul 18 23:37:22 2016
|
The URL encoding of ']' as '%5D' appears to work:
[url=http://example.com?arrays[%5D=v1&arrays[%5D=v2]click here[/url]
Cheers, Andreas |
|
Re: Escape character [ or ] doesn't work within [url], posted by Don on Tue Jul 19 21:08:08 2016
|
Andreas
Luedeke wrote:
The URL encoding of ']' as '%5D' appears to work: |
|
string length limit in url tag, posted by Don on Wed Jul 20 16:03:24 2016
|
What is the string length limit in url tag and how to increase it?
For example,
[url=http://example.com?<text_string>]click here[/url] |
|
Re: string length limit in url tag, posted by Andreas Luedeke on Thu Jul 21 06:15:44 2016
|
Several strings in ELOG are limited to 256 chars. It is likely the limit for URLs, too.
The magic number "256" appears 285
times in the elogd.c file.
It is probaly easier if you compress long URLs with goo.gl
Cheers, Andreas
Don wrote:
|
elogd dies upon search, posted by Christian Ludwig on Fri Jun 3 08:16:31 2016
|
Hi all,
ELOG V3.0.0-21dc563
Our elogd dies alwways when searching for full text: |
solved: elogd dies upon search, posted by Christian Ludwig on Fri Jun 3 08:59:49 2016
|
I would like to share my findings about the solution of our problem:
One of my collegues used elog in a way it was not intended for, he put an endry with 8021 lines of text.
So I grabbed the corresponding 160517a.log file from logdir, renamed it to a text file and created a new entry with the large textfile as attachment. |