| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
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. |
|
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. |
|
66629
|
Thu Nov 26 13:12:23 2009 |
| Bertram Metz | Bertram.Metz@gefanuc.com | Question | Other | 2.7.7 | Re: elogd.cfg for this forum |
> Hi Stefan,
>
> I'm interested in the current configuration file for this discussion forum. Could you please post it to the
> 'config examples' logbook?
>
> Thanks,
> Bertram
Sure, here it is! |
|
66628
|
Tue Nov 24 10:38:26 2009 |
| Bertram Metz | Bertram.Metz@gefanuc.com | Question | Other | 2.7.7 | elogd.cfg for this forum |
Hi Stefan,
I'm interested in the current configuration file for this discussion forum. Could you please post it to the
'config examples' logbook?
Thanks,
Bertram |
|
66627
|
Mon Nov 23 13:17:53 2009 |
 | David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.7.7-2266 | Re: Attachments and images of attachments |
> > Hi Stefan,
> >
> > I attached a 12 page (22kB) pdf file - no images - to an entry, but elog only converted the first 8 pages to
> > images (.png). This is reproducable, i.e. a different small multipage pdf file produced the same number of images.
> >
> > The size of the pdf file does not seem to be a problem, a single page pdf file with a lot of images in it
> > attached as expected.
> >
> > Is this correct, or a defined limitation?
>
> This is a defined limitation. Sometimes people attach whole books in PDF form to an entry, and you don't want to end up
> with hundreds of images cluttering your browser. If you want to see the full document, just load it into your PDF viewer.
Thanks, Stefan (why is this answer down under my name!?)
I couldn't find reference to this in the documentation. In the case I referred to, I'll have to play with the pdf so that
the six pages I actually want displayed are. |
|
66626
|
Mon Nov 23 12:32:14 2009 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.7.7-2266 | Re: Attachments and images of attachments |
> Hi Stefan,
>
> I attached a 12 page (22kB) pdf file - no images - to an entry, but elog only converted the first 8 pages to
> images (.png). This is reproducable, i.e. a different small multipage pdf file produced the same number of images.
>
> The size of the pdf file does not seem to be a problem, a single page pdf file with a lot of images in it
> attached as expected.
>
> Is this correct, or a defined limitation?
This is a defined limitation. Sometimes people attach whole books in PDF form to an entry, and you don't want to end up
with hundreds of images cluttering your browser. If you want to see the full document, just load it into your PDF viewer. |
|
66625
|
Mon Nov 23 11:53:22 2009 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.7.7-2266 | Attachments and images of attachments |
Hi Stefan,
I attached a 12 page (22kB) pdf file - no images - to an entry, but elog only converted the first 8 pages to
images (.png). This is reproducable, i.e. a different small multipage pdf file produced the same number of images.
The size of the pdf file does not seem to be a problem, a single page pdf file with a lot of images in it
attached as expected.
Is this correct, or a defined limitation? |
|
66624
|
Fri Nov 20 19:32:22 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 |
| 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.
|