According to section "Syntax of elogd.cfg" of the "Administrator's Guide" Options <attribute> = <list> and  ROptions <attribute> = <list> should be the same. But there is a litle difference, because choosing an entry of the Options-pull-down menu causes a reload of the entry mask while choosing a ROption-radio-button the entry mask is not reloaded. This causes a problem using conditional attributes. The condition is only paid attention to in case of Options but not in case of ROptions. In my case I would like to use ROption, as it is faster to set a radio button than to choose an item in a pull-down menu, but I can't as I have also to use conditional attributes. Is there any solution?

Hello @all,

for a logbook I have also to set up a guest access. As I want to have a login page first opening the logbook,  I created a second logbook entry in the elog.cfg that points to the same subdir as the original logbook. The idea of this guest access is, that users who have no login rights can read selected items with selected attributes. Therefor I restricted the guest account with all available "Guest"-commands in the elog.cfg.

But this is not sufficient. Let's suppose I have an attribute called 'Accessibility' with options 'public' and 'private'. What I am searching for is a filter command for the list display, i.e. if an entry has the accessibility flag 'public', a guest sees this entry in the list and can access it. But if the entry has the accessibility flag private, the entry should not be displayed for guests but for users, that are logged in.

I read the administrator guide carefully, but I didn't found a command that provides for that. Does such a filtering command for the list exist? If not, is it possible to implement one?

Best regards,

Wolfgang Bayer

Greetings all.  A few ELOG users have posted issues with ELOG 3.0 and newer not working with a variety of MS Windows operating systems,.
I have also encountered a similar problem in my environment.

For the following operating systems:        
1) Windows XP SP3 (32-bit)           
2) Windows Server 2003 SP 2 (32-bit)
when either elog.exe or elogd.exe are run from command line or file manager, the operating system reports the program is not a Win32 application.

I have other test computers that succesfully ran ELOG 3.0, 3.1 and 3.1.1
1) Windows Vista Enterprise (32-bit)
2) Windows 7 Professional (64-bit) 

Has ELOG 3.x and newer changed in regards to support for MS Windows but is not documented on the
official ELOG documentation?

Any help would be most appreciated.

NOTE: The current production ELOG I use on Windows Server 2003 is 2.92-2475 but I would like to use the
features available on the 3,.x versions.  Unfortunately, I am not able to change my production operating system.
 

Thank you for recompiling ELOG.  Unfortunately, there is no change in all the test machines
I ran the newly compiled ELOG 3.1.1-1 on.  I will use the 2.x version until our systems move
to a new operating system or I can find someone in my IT department who knows how to compile programs
from the source code. 

If anyone else has suggestions or could compile the source for us to try, please speak up.  There are
many installations of obsolete operating systems in production :
 

I would like to export several entries out of a logbook I have with a specific subject. 

I need to send these entries to someone who does not have elog nor can they install it.

Is there a way to do this?

Thanks,

Bill

 Thanks for the information, looks like the csv options don't export the actual entry.  I'll have to play with the other formats they look like html.

I noticed a long url got hard-wrapped when I entered a long one, I patched 
the source code. I don't know if this was done intentionally, otherwise you 
might want to change this also.

diff elogd.c elogd.c.org 
4468c4468
<     rsprintf("<textarea rows=20 cols=%d wrap=soft name=Text>", width);
---
>     rsprintf("<textarea rows=20 cols=%d wrap=hard name=Text>", width);

BTW, why is the editor window 20 rows by 76 columns ?
(20 is fixed in the source code, but 76 is the width-variable that is set 
hard to:

  /* set textarea width */
  width = 76;

Now I don't like both parameters. 20 is too long for my display (1024x768) 
and 76 is too short. Something dynamically would be cool, but a parameter 
somewhere in a config file would also be acceptable. (just a thought, makes 
it easier to upgrade)

When I make a new entry I get an email with 

   subject: New ELOG entry

But when I or someone else changes an entry I also get an email with a 

   subject: New ELOG entry

I would prefer to see "Changed" , "Edited", or "Updated". This is beyond my 
programming capabilities so I enter this request.