Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 417 of 808  Not logged in ELOG logo
icon5.gif   Cascading menus???, posted by ron murphy on Tue Nov 29 18:12:40 2011 

This may be already answered somewhere around here, but I could not find it. 

Question: Is it possible to have a pull down will a sub menu.  Something like,

 

Entry 1

Entry 2 --> Entry 2a

                   Entry 2b

                   Entry 2c

Entry 3

Entry 4

 

Thanks!

 

    icon2.gif   Re: Cascading menus???, posted by Eoin Butler on Tue Dec 13 22:18:04 2011 

ron murphy wrote:

This may be already answered somewhere around here, but I could not find it. 

Question: Is it possible to have a pull down will a sub menu.  Something like,

 

Entry 1

Entry 2 --> Entry 2a

                   Entry 2b

                   Entry 2c

Entry 3

Entry 4

 The way I do this is

Attributes = Author, Subject, Run, Type, Hardware, Software, 

Options Type = Announcement{1}, Shift_Summary{2}, Physics_Discussion{3}, Analysis{4}, Hardware{5}, Software{6}
Options Hardware = Computers, Cryostat/Vacuum, DAQ, Environment Sensors, Magnets
Options Software = Analysis/Simulations, Control/Measurement, Detector, Linux, MIDAS, Sequencer, Windows
Show Attributes = Author, Type, Subject
{5} Show Attributes = Author, Type, Subject, Hardware
{6} Show Attributes = Author, Type, Subject, Software


 

icon5.gif   "Reply to" Author in this forum, posted by David Pilgram on Thu Nov 26 14:27:27 2009 
Hi Stefan,

This has happened twice on this forum now, starting from Mon 23rd November.

Someone submits an entry (Me, 66625, Bertram Metz 66628)
I assume you post a reply (66626, 66629), but it shows up as if I or Bertram are the author of the reply, not
yourself.  My reply to you (66627) was really authored by me, and I expressed puzzlement then at this point.

Is this a bug, or some wierd affect of us forgetting to log out?

Regards,

David.
    icon2.gif   Re: "Reply to" Author in this forum, posted by Stefan Ritt on Thu Nov 26 17:42:02 2009 
> Hi Stefan,
> 
> This has happened twice on this forum now, starting from Mon 23rd November.
> 
> Someone submits an entry (Me, 66625, Bertram Metz 66628)
> I assume you post a reply (66626, 66629), but it shows up as if I or Bertram are the author of the reply, not
> yourself.  My reply to you (66627) was really authored by me, and I expressed puzzlement then at this point.
> 
> Is this a bug, or some wierd affect of us forgetting to log out?
> 
> Regards,
> 
> David.

Thanks for pointing out this issue. This bug was introduced recently, when I tried to avoid the

Re: Re: Re: ...

in the subject line. I changed this now completely so that we can have

Preset on reply Author = $full_name
Preset on first reply Subject = Re: $Subject

which fixes both things. The modification is in revision 2271.
    icon14.gif   Re: "Reply to" Author in this forum, posted by David Pilgram on Thu Nov 26 20:37:02 2009 
> > Hi Stefan,
> > 
> > This has happened twice on this forum now, starting from Mon 23rd November.
> > 
> > Someone submits an entry (Me, 66625, Bertram Metz 66628)
> > I assume you post a reply (66626, 66629), but it shows up as if I or Bertram are the author of the reply, not
> > yourself.  My reply to you (66627) was really authored by me, and I expressed puzzlement then at this point.
> > 
> > Is this a bug, or some wierd affect of us forgetting to log out?
> > 
> > Regards,
> > 
> > David.
> 
> Thanks for pointing out this issue. This bug was introduced recently, when I tried to avoid the
> 
> Re: Re: Re: ...
> 
> in the subject line. I changed this now completely so that we can have
> 
> Preset on reply Author = $full_name
> Preset on first reply Subject = Re: $Subject
> 
> which fixes both things. The modification is in revision 2271.

Thanks Stefan!
icon5.gif   2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Mon Nov 2 21:23:38 2009 

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

    icon2.gif   Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by Stefan Ritt on Tue Nov 3 09:04:34 2009 

David Spindler wrote:

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.

I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash. 

    icon2.gif   Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Wed Nov 11 19:45:19 2009 

Stefan Ritt wrote:

David Spindler wrote:

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.

I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash. 

 In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:


ELOG V3.1.5-3fb85fa6