Not sure if this is a bug or not; if it is not, kindly reclassify the category.

Following is a small example of what I will dub a 3-level, conditional logbook:

This example is hardly complete, but it is sufficient to demonstrate the issue I am running into.  This works until I select from the 2nd level (manufacturer); it won't display the dropdown for the model (I think my show attribute edit is supposed to display that).  Is there a restriction on how many levels of conditional I can have?  If there is, it would be disappointing because I am trying to do something similar to this example.

I hope there is something very simple I can do to correct this, or perhaps a completely different approach that accomplishes the same thing.  I'd like to stick with the multi-level selection process as I have done here.

I am running elog 3.1.5 on Devuan Chimaera (approx. Debian Bullseye, sans systemd) in a Virtualbox VM.

I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.

I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.

This is running under Win2K with SP4 as an automatic service on port 80.

I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.

If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.

Thanks,

David

hello all,

#1 i love ELOG : excellent app! i would like to ask/present a question here -- I have a couple of TYPE's defined as;

       Options Type = Day Shift, Swing Shift, Night Shift
What I'd love to be able to do, is depending on what TYPE was selected during the creation of a NEW ENTRY in the ELOG "shift log" I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected...

for example, if someone chose "Day Shift" that would be listed with a GREEN background, if someone chooses "Swing Shift" that gets a BLUE background, and so forth... I am wondering how one would go about implementing this?

second question... instead of listing the column named TYPE, can I just change it somewhere in the config to "SHIFT" so that in the list view, and even when in the NEW ENTRY form, I'd like it to show "Shift" instead of TYPE --- really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable?

Thanks for the app, I look forward to any reponses! I been editing the CSS, and once done think I'll add it to yr Config Examples, as I don't see many CSS themes there...

-peace-

Hello,

I try to have two Extendable options : Client and Equipment
so here is the line in my elogd.cfg
Extendable options = Client, Equipment

When I create a new entrie, I have the 2 scroll menus(Client and 
Equipment) and the 2 buttons(Client and Equipment) but i can't create 2 
news entries, i must create one for client, after I submit, I edit one 
more time and add a new equipement. Is there a solution for this?

Thanks a lot and sorry for mistakes or problem of comprehension i'am 
french :)

I found two potential memory leaks which I fixed in the git version, so you can try again.

Another possibility, which is actually preferred, is to limit the size of the subject filed to a reasonable number. You can do that with following option

Format subject = 0, attribname, attribvalue, 80, 200

This shows the subject line with a width of 80 characters, but does only allow 200 characters to be entered there.

Best,
Stefan

> I found two potential memory leaks which I fixed in the git version, so you can try again.

Just tested, and it works! Many thanks for very quick patch!

> 
> Another possibility, which is actually preferred, is to limit the size of the subject filed to a reasonable number. You can do that with following 
option
> 
> Format subject = 0, attribname, attribvalue, 80, 200

Yes, that is a good suggestion, I'll implemented it.

Many thanks again!

Best,
  Stefano

> 
> This shows the subject line with a width of 80 characters, but does only allow 200 characters to be entered there.
> 
> Best,
> Stefan

Maybe consider using the options -W -Wall when compiling elogd.
There are several warning messages.