ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67151
|
Tue Nov 29 18:12:40 2011 |
| ron murphy | starfury65@gmail.com | Question | Linux | 2.7.7-1 | Cascading menus??? | 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!
|
67153
|
Tue Dec 13 22:18:04 2011 |
| Eoin Butler | eoin.butler@cern.ch | Question | Linux | 2.7.7-1 | Re: Cascading menus??? |
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
|
|
66630
|
Thu Nov 26 14:27:27 2009 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | 2.7.7- | "Reply to" Author in this forum | 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. |
66631
|
Thu Nov 26 17:42:02 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.7- | Re: "Reply to" Author in this forum | > 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. |
66632
|
Thu Nov 26 20:37:02 2009 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | 2.7.7- | Re: "Reply to" Author in this forum | > > 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! |
66571
|
Mon Nov 2 21:23:38 2009 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.7.7 2246 | 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 | 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 |
66572
|
Tue Nov 3 09:04:34 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.7 2246 | Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 |
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. |
66596
|
Wed Nov 11 19:45:19 2009 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.7.7 2246 | Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 |
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:
|
|