Re: How to change configuration already set properly, posted by Andreas Luedeke on Wed Mar 18 09:34:46 2015
|
ELOG does not provide you with a simple mechanism to rename attributes in existing entries.
If you rename an attribute in the configuration,
then you need to adapt all existing entries by replacing the name in all *a.log files on the server.
Or you could set-up a second logbook
with the renamed attributes, export all entries from the first logbook (use "Find") and import these entries in the second logbook.
|
|
Re: How to change configuration already set properly, posted by Andreas Luedeke on Fri Mar 20 09:23:57 2015
|
ELOG is storing all entries as text files. Open text files and use search and replace in text editor. Or instead: export with Find and import in another
ELOG with renamed attributes.
Banata |
|
Re: Permission to view, posted by Andreas Luedeke on Fri Mar 20 09:25:11 2015
|
Yes, it is possible. And explained in ELOG documentation.
Banata
Wachid Ridwan wrote:
Hello, |
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Tue Mar 31 11:36:25 2015
|
[quote="Stefan Ritt"]The (correct) display tells me that the colours are user-defined, probably by the configuration option
Style <attribute> <value> = <style>
|
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 10:54:27 2015
|
[quote="Stefan Ritt"][quote="Andreas Luedeke"]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.[/quote]
|
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 18:31:28 2015
|
[quote="Stefan Ritt"][quote="Andreas Luedeke"]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.[/quote]
|
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 18:39:14 2015
|
Proof of principle ;-) |
elogd lost entry database without restart during file system trouble, posted by Andreas Luedeke on Thu Apr 30 09:54:17 2015
|
I'm running ELOG since several years with rather heavy usage.
Last week I've upgrades from 3.0.0 to 3.1.0 and this week I had twice the same problem:
elogd lost the index for old entries and showed empty logbooks, without having restarted.
|