Hi, thanks to everyone involved for giving us the elog.

A question:

Is it possible to submit entries to an elog on a remote machine by email?

Thanks, Thorsten

Hi, thanks for everyone involved for giving us the elog.

A question:

Is there an easy way (without intermediate save) to send screenshots (with irfan, snagit or hardcopy) as a new entry to an elog running on a remote machine?

Thanks, thorsten

I have Split Elog to Two Top Group [Check the Config Below].

Problem = 

After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.

[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1

Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing

[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01

[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01

Hi Andreas

I'm following the instruction from https://midas.psi.ch/elog/config.html#groups , please scroll to the Top Groups

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases

[global engineering]
Password file = engineers.pwd
Admin user = stefan

[global administration]
Password file = admin.pwd
Admin user = bill

Hi Andreas, 

Thanks for your help. I will try to do that and if I found how to fix this problems, I will post it at here again.

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases

[global engineering]
Password file = engineers.pwd
Admin user = stefan

[global administration]
Password file = admin.pwd
Admin user = bill

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies.  On the 10th reply the application crashed, this is repeatable 100% of the time.  Without the propagate option everything works fine.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

 Thank you for the reply, the not allowing branching was added during the troubleshooting phase of the crashing.  Initially I thought the branches caused the issue because crashing only occured on log notes that branched as I only saw the crash on notes that branched, this proved not to be the case.  Even with branches the system will crash once there are 10 replies in the note with propagate on.

As for use case, with  a few users I needed a way to represent a note as open so that the next person knew work still needed to be done.  Once work was completed all notes close, the reason for not using edit is so I have a clear record of what happened (although I may need to change to edit if 10 is the max).  I will experiment with the collapse to last to see how it looks.  Any other suggestions would be helpful.

 Thanks for the reply, I tried the very basic cfg and the second one you offered.  Running 2.9.2-2475 on a Windows 2008 R2 V.Server, I still crashed on attempt 10 never fail.  Windows detects the failure and gives this message:

Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707

Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707

Exception code: 0xc00000fd

Fault offset: 0x00065127

Faulting process id: 0x340

Faulting application start time: 0x01ceefa87fea0aea

Faulting application path: D:\ELOG\elogd.exe

Faulting module path: D:\ELOG\elogd.exe

Report Id: ceccc3da-5b9b-11e3-80f1-5ac95c924b0b

It only happens when propagate is on, I have to be missing some security setting in Windows maybe?  Don't know if that helped at all, but I'm out of ideas.