Re: Paper clip showing attachment not always present, posted by Stefan Ritt on Fri Nov 13 15:07:57 2009
|
> It would appear to be a bug that the attachment icon does not appear in the threaded display (for any entry
> other than the initial one).
Yes, that's indeed a bug. I fixed it in SVN revision 2266. |
|
Re: Paper clip showing attachment not always present, posted by David Pilgram on Fri Nov 13 15:10:34 2009
|
Thanks Stefan!
(But I'll wait and see if you do anything about Steve's point...so I'll download "after work"!).
> > It would appear to be a bug that the attachment icon does not appear in the threaded display (for any entry
> > other than the initial one).
>
> Yes, that's indeed a bug. I fixed it in SVN revision 2266. |
|
Re: "Collapse to last = 1" problem when reply twice to the same entry, posted by Stefan Ritt on Mon Nov 16 13:46:38 2009
|
> Hello.
>
> Please look at the entry 66525 of this forum (just 5 thread before this one):
>
> -> chain.crt, posted by Gerhard Schneider on Thu Sep 3 21:55:52 2009 (66525)
> |-> Re: chain.crt, posted by Stefan Ritt on Fri Sep 4 08:33:16 2009 (66526)
> |-> Re: chain.crt, posted by Gerhard Schneider on Wed Oct 7 07:56:52 2009 (66556)
>
> When you collapse the thread, it is collapsed to the 66526 instead of the 66556 (more recent)
>
> + Re: chain.crt, posted by Stefan Ritt on Fri Sep 4 08:33:16 2009
>
> I guess it is because both 66526 and 66556 replies to the first entry.
> I have the same problem with Elog v2.7.7-2246 and Windows.
>
> In general, it seems to work well only if you always reply to the last entry of a thread.
>
> Thank you.
>
>
> b.t.w. : is there any tip to always force reply to the last entry of a thread?
I fixed that in revision 2269. So now elog scans a complete branch and searches for the last entry in the branch.
You can check again the branch above on the forum, should work now. |
|
Re: Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by Heinzmann on Tue Nov 17 19:31:46 2009
|
| David Spindler wrote: |
|
| 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:
|
Hi,
I´m using 2.7.7 rev 2246 and tested it with my logbooks without any problems. But today I had no chance to reach them anymore. Strange.
Regards,
Michael
|
|
Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Fri Nov 20 19:32:22 2009
|
| David Spindler wrote: |
|
| 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:
|
Sorry for the delay.
1: The offending log file.
|
"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. |
|
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. |
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! |