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

We're using elog as our CMDB, but now management wants us to employ "web services" and I fear going to another tool (elog is fitting the admins like a glove, so we'd rather keep it)

Is it possible to configure elog to be able to run as a web-service ?  (basically getting xml-output according to a specific (SOAP) schema instead of html output)

http://en.wikipedia.org/wiki/Web_services

A 'Web service' (also Web Service) is defined by the W3C as "a software system designed to support interoperable Machine to Machine interaction over a network." Web services are frequently just Web APIs that can be accessed over a network, such as the Internet, and executed on a remote system hosting the requested services.

The W3C Web service definition encompasses many different systems, but in common usage the term refers to clients and servers that communicate using XML messages that follow the SOAP standard. Common in both the field and the terminology is the assumption that there is also a machine readable description of the operations supported by the server written in the Web Services Description Language (WSDL). The latter is not a requirement of a SOAP endpoint, but it is a prerequisite for automated client-side code generation in many Java and .NET SOAP frameworks (frameworks such as Spring and Apache CXF being notable exceptions). Some industry organizations, such as the WS-I, mandate both SOAP and WSDL in their definition of a Web service.