I'm pleased to announce the release of ELOG version 2.7.0 which contains the HTML editor FCKeditor. This allows the formatting of ELOG entries just as one is used from a word processor. I tried to make all functionality working as one is used from the ELCode system (like replies quote the original text in a yellow text box), but I'm not sure if I covered everything. So if you experience problems with the new editor, please report it and I will try to fix it. Anyhow it is always possible to switch back to the old ELCode encoding.

One warning for site administrators: Since it is possible to enter HTML code directly into a web page, one risks a XSS vulnerability. If someone knows how to protect the FCKeditor against submission of JavaScript, please let me know and I will add it. If this is an issue, you can turn off HTML encoding completely for public ELOG sites with allowed encoding = 3 in elogd.cfg.

Finally I would like to give credits to An Thai who proposed this editor.

While it is possible to print a logbook using the standard web browser print command in the Full or Summary view, a dedicated print function allowing the user to print out a hardcopy of a particular logbook would be very helpful.

Cheers

Adam

P.S. Thankyou for the response in elog:65671

Between the ELOG versions 2.7.0 and 2.7.1 the internal HTML editor FCKedit has been upgraded from version 2.4.3 to 2.5beta. The new version has a few more options and supports more browsers. People however reported some errors popping up like Unknown toolbar item "ELOGSubmit". This happens because some browsers cache the JavaScript from the old version of the editor in their cache. To fix this problem, simple clear the browser's cache. In Firefox, do a Tools -> Options -> Advanced -> Cache -> Clear now. Other browsers have similar ways to clear the cache.

The mxml source code should be moved into the elog-*/src directory. This requires changing the Makefile to:

MXMLDIR = src/mxml

Reason for change: if you want to build several versions of elog and you unpack the distributions in the same top-level directory, the most recently unpackaged version will overwrite the mxml directory contents, possibly introducing bugs.

#include /elog-archive/additional.config

 We have configured several logbooks to allow users to duplicate an entry in another logbook, which is very useful for entries which apply to more than one category.

However, once the entry is duplicated, subsequent revisions to the original entry are not copied to the duplicate entries.

I can see where implementing that would add a lot of code to ELOG.  Rather than do that, would it be possible to add a configuration option to duplicate only the attributes, and place a link to the original entry in the body of the duplicated entry instead of the full text?

Thanks,

Dennis

 It would be nice to have the option of including an attachment indicator column in summary view to show if an entry has any attachments.

Thanks.

Hello

Sometimes it can come in handy to start a temporary elog service on the Windows platform. ( Maybe for testing purposes )

You can use the SC.exe utility to do that. If it is not on you're system you may download it from : ftp://ftp.microsoft.com/reskit/win2000/sc.zip

For this you can use the following procedure ( from the dos prompt ) :

 sc.exe create AIX-elog binPath= "\"c:\ELOG2.7.3\elogd.exe\" -D -c c:\ELOG2.7.3\security.cfg" DisPlayname= "AIX Elog Security" start= auto

If all went well the system answers :

 [SC] CreateService SUCCESS

Please notice the strange way the double quotes are used and the space after the = in the above command.

Now open the windows services ( from the prompt ) : services.msc

In the window that opens you will see the just created service with the DisPlayname you gave in the above command.

You see it is not started. You could click start, but there is an other way.

Now you can start the service from the prompt using the DisPlayname :

  net start "AIX elog security"

Press F5 ( refresh ) in the services window and you will see that the service is started.

Or stop the service :

  net stop "AIX elog security"

To remove the service ( from the registry ) :

   sc.exe delete AIX-elog

The system gives back :

  [SC] DeleteService SUCCESS

The other option is to start elogd.exe from the prompt :

  elogd.exe -c 

This is all for now