Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 514 of 808  Not logged in ELOG logo
IDdown Date Icon Author Author Email Category OS ELOG Version Subject
  65697   Fri Jan 18 13:57:31 2008 Question Javier A. Ortizjavier.ortiz.78@gmail.comQuestionWindows Audit Trail?

First thanks for the great software! My only question would be how to implement audit trail feature. I know you can control who edits and that's great but in regulated environments like mine there's a requirement that the original record, the one edited, is not deleted or overwritten. If not possible right now the only thing I could think of is a mechanism, maybe possible thru configuration, that when the record is edited it is copied to an audit trail logbook (i.e. if logbook name is 'test' it's audit logbook will be named 'test-audit' which is read only) and have a link to the audit trail of the record (show only changes of the current record).

 

I'm more than aware that it's possible thru configuration but I'm short on that dept. Any help/idea?

 

Thanks in advance!

  65696   Fri Jan 11 14:33:58 2008 Reply Kristján Jónssonkj@raunvis.hi.isQuestionLinux2.7.0-1954Re: Configuration of HTML editor

 

Stefan Ritt wrote:

 

Kristján Jónsson wrote:

Do I have to do any extra configuration in elog to enable the FCKeditor.

What I get with V2.7.0-1954 is that the main message entry field looks and behaves identically whether I set the encoding to HTML or plain (except the width and height of the field changes).

ELCode works as expected.  Message files saved with the encoding set to HTML have a line "Encoding: HTML", but no HTML markup.  Those saved with encoding set to plain have the line "Encoding: plain", but are otherwise identical.

I have the scripts directory as set up by "make install" containing the elcode.js file and the fckeditor subdirectory.  All are world readable.

Any hints about what could be the problem?

 

Version 1954 is a bit old. Please update to the current SVN version and try again. There must be a file elog/scripts/fckeditor/fckeditor.js which was missing at some time.

 

Excellent, works as expected now, thanks.

Didn't realise how far behind the SVN version elog-latest.tar.gz is.

 

 

 

  65695   Fri Jan 11 08:08:51 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.0-1954Re: Configuration of HTML editor

Kristján Jónsson wrote:

Do I have to do any extra configuration in elog to enable the FCKeditor.

What I get with V2.7.0-1954 is that the main message entry field looks and behaves identically whether I set the encoding to HTML or plain (except the width and height of the field changes).

ELCode works as expected.  Message files saved with the encoding set to HTML have a line "Encoding: HTML", but no HTML markup.  Those saved with encoding set to plain have the line "Encoding: plain", but are otherwise identical.

I have the scripts directory as set up by "make install" containing the elcode.js file and the fckeditor subdirectory.  All are world readable.

Any hints about what could be the problem?

Version 1954 is a bit old. Please update to the current SVN version and try again. There must be a file elog/scripts/fckeditor/fckeditor.js which was missing at some time.

 

  65694   Thu Jan 10 18:30:26 2008 Question Kristján Jónssonkj@raunvis.hi.isQuestionLinux2.7.0-1954Configuration of HTML editor

Do I have to do any extra configuration in elog to enable the FCKeditor.

What I get with V2.7.0-1954 is that the main message entry field looks and behaves identically whether I set the encoding to HTML or plain (except the width and height of the field changes).

ELCode works as expected.  Message files saved with the encoding set to HTML have a line "Encoding: HTML", but no HTML markup.  Those saved with encoding set to plain have the line "Encoding: plain", but are otherwise identical.

I have the scripts directory as set up by "make install" containing the elcode.js file and the fckeditor subdirectory.  All are world readable.

Any hints about what could be the problem?

Thanks

Kristján

 

  65693   Thu Jan 10 16:31:22 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.0-1985Re: Unknown toolbar item 'ShowBlocks'

Uwe wrote:

Stefan Ritt wrote:

Uwe wrote:

Hello,

I just made an update from version V2.7.0-1964 to V2.7.0-1985 and I am receiving now the error message Unknown toolbar item 'ShowBlocks' whenever creating or editing an entry.  When clicking onto Ok, everything seems to work fine. Can you help please? Error message occurs in Internet Explorer and also in Firefox.

The intermediate elog version 2.7.0-3 had a bug which truncated some entries (just like the one where I reply to). This has been fixed in release 2.7.0-4. So please everybody who uses 2.7.0-3 do an update.

  65692   Thu Jan 10 15:32:40 2008 Agree Uweuweho@web.deQuestionWindows2.7.0-1985Re: Unknown toolbar item 'ShowBlocks'

Stefan Ritt wrote:

Uwe wrote:

Hello,

I just made an update from version V2.7.0-1964 to V2.7.0-1985 and I am receiving now the error message Unknown toolbar item 'ShowBlocks' whenever creating or editing an entry.  When clicking onto Ok, everything seems to work fine. Can you help please? Error message occurs in Internet Explorer and also in Firefox.

  65691   Thu Jan 10 15:30:35 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.0-1954Re: "Default encoding" default is not as documented

Quote:
"Default encoding" appears to have the default value of 2 (HTML) instead of 0 (ELCode) as documented in http://midas.psi.ch/elog/config.html

ELOG V2.7.0-1954 : elog.c line 8952

Kristján


I changed the documentation Wink

The reason for this is to give beginners the FCKeditor by default instead of the ELCode encoding.
  65690   Thu Jan 10 15:24:53 2008 Entry Kristján Jónssonkj@raunvis.hi.isBug reportLinux2.7.0-1954"Default encoding" default is not as documented
Hi,

"Default encoding" appears to have the default value of 2 (HTML) instead of 0 (ELCode) as documented in http://midas.psi.ch/elog/config.html

ELOG V2.7.0-1954 : elog.c line 8952

Kristján
ELOG V3.1.5-3fb85fa6