ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66226
|
Thu Feb 26 11:05:36 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5 | Re: No Valid Header? |
mike cianci wrote: |
Stefan,
I finally got it installed on a server at work (only took a year to work through all the red tape). I have seven logbooks up and running and only one is giving me trouble. It is an On-Line Help book where I wanted to store documents that could be referenced by our staff. It is the simplest of my logbooks (see config file below) but when I hit the "Submit" button it crashes the program. I can not see the error myself but the server guys are telling me that that we are getting an "Internal error, no valid header!" error. The only other thing that I can think to mention is that the entry that is crashing the program is a 60k Microsoft word table that I had cut and pasted into elog.
|
Ah, that rings a bell. We recently had problems with large tables. Can you try the current version if you get the same problem? |
66229
|
Fri Feb 27 17:25:30 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Mac OSX | 2.7.5 | Re: Attachment problems |
Dennis Seitz wrote: |
Apologies if these are known bugs, I'm very busy at the moment but I wanted to post this before I forget:
I'm using Safari on a Mac to make Elog entries.
1) The preview of some pdf attachments in edit mode displays huge areas of white space around each page. I can send examples if you'd like - please email me directly, for some reason I never get email notifications from this forum (and they aren't being tagged as spam, so I don't know where they go).
2) When that happens, the text entry area for ELcode format expands horizontally to match the huge pdf file width. Text without line feeds then doesn't wrap until the huge window width is filled, so I have to scroll horizontally all the time while editing to see what I've written.
3) So I turned off attachment previewing as a workaround (Preview attachments = 0 ). That worked fine by not expanding the entry area, but I noticed some odd behavior. The list of attachments below the text entry area is badly formatted. Here's a screen shot:

I tried to reproduce this with a new entry but the text was formatted properly for that entry.
P.S. While editing this entry, I see that the text area width is again being set by the width of the picture I've attached - try it yourself; if you try to resize your browser window smaller while editing, the text will only wrap until the width of the attachment is reached - the text no longer wraps at smaller widths than the attachment.
|
Your problem 1) is probably caused by ImageMagick. I use that package to convert PDFs to images. If this package estimates the paper size from the PDF incorrectly, you're screwed. You can go and actually locate the thumbnail pictures in the ELOG directory (should be named xxxxxx_yyyyyy_<name>-0.png). If you check these pictures, they are probably already huge.
Problem 3) indeed is a small bug in elogd, which I fixed in revision #2178. If you can download the SVN version and recompile elogd, you should be fine:

|
66233
|
Tue Mar 3 12:38:07 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.7.5-2130 | Re: Idea/Suggestion | > Hi Stefan,
>
> Must have missed it when the fixed/not fixed thread marking got implimented.
>
> Anyhow, my main point would still apply for where the thread is not yet fixed, but is in one of a number of possible
> states (waiting, panic, work-in-progress....). Clearly you can label the latest entry in a thread with the latest
> status, and icon, but when in collapsed mode, you only see the initial entry. If the latest entry were shown
> (optionally), then one can tell at a glance in the collapsed listings which entry may need direct attention.
If you always mark the whole thread with states (waiting, panic, work-in-progress,...) as described in my last posting,
then you will see this from the thread initial entry as well. If you use icons, then even more. The only disadvantage
is that you have to discipline yourself always modifying the whole thread and not only one entry in that thread. |
66235
|
Wed Mar 4 16:41:27 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.5 2142 | Re: Elogd crashes with: *** stack smashing detected *** |
Niklas wrote: |
Tried 2178 and I seem to hit some endless loop when I have big cookies. The loop seems to be in this for-loop (from gdb).
I perhaps you should have:
for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; )
if (i < (int) sizeof(cookie)-1)
cookie[i++] = *p++;
else
break;
cookie[i] = 0;
... Seems to be working for me =)
|
Yepp, you're right. I applied your change to the distribution code.
|
66239
|
Fri Mar 6 21:51:48 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.7.5 | Re: Email authentication with SSL/TLS |
Val Schmidt wrote: |
Hi,
I'm curious is it possible to send email notificaitons from elog through an smtp server that requires SSL/TLS authentication? I think it's not but I thought I'd ask.
-Val
|
This is currently not implemented and will probably not implemented in the next time, but it's on my (very long) to-do list. |
66243
|
Mon Mar 9 18:58:18 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5 | Re: Login issue |
Heinzmann wrote: |
Heinzmann wrote: |
Heinzmann wrote: |
Hi,
I have found the issue, when I mark at the login page:
Keep me logged in on this computer
for the next 41 days or until I log out
I'm not able to login. Only when it is not marked I'm able to login.
How can I diable/hide the part (Keep me logged in on this computer
for the next 41 days or until I log out) from my login page?I
Issue solved: Login expiration = 0
|
|
|
Great, you found it! The original problem is probably related to your cookie handling. If you don't check the "keep me logged it" box, elog generates a temporary cookie, which is used for the duration of your browser session, then the browser discards it. If you theck the box, a persistent cookie is created, which your browser stores in the cookie database and reuses it for the coming 41 days. I believe you have a problem there (persistent cookies not allowed, disk full, whatever...) which does not allow handling of persistent cookies. Try from anohter browser/computer and you will see that it works. |
66244
|
Mon Mar 9 19:00:26 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 2.7.5 | Re: Email recall function similar to what exists say in something like Outlook |
Niall Dooley wrote: |
Hi,
Is there a way perhaps of implementing an email recall feature into E-Log? In other words, to recall an email before the recipient (s) read the email originating from the e-log. Something perhaps along the lines of what exists in something like Outlook.
Thks in advance.
Regards,
Niall
|
No, this is not implemented. What I usually do is to check "Suppress Email notification", submit and revise my entry. Once I'm satisfied, I edit again and do not check "Suppress Email notification" so that the email is finally sent out. |
66252
|
Mon Mar 16 22:53:22 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.7.5-2130 | Re: Adding texts for each attachment |
Dongwook Jang wrote: |
Dear Stefan,
First of all, I appreciate that you made such a nice program. I've used elog for more than 5 years and it was wonderful experince to me and my research work was very productive with this.
I have a suggestion to you to improve this while I was using elog. If users can add texts or comments for each attachment, it will be great.
I am not sure if someone was already suggested this or it is already in your wish list.
Thank you.
Dongwook Jang
|
Dear Dongwook,
no, this is not implemented and also was never requested. The way most people work is that images are included directly in the text, and the the text goes along with that.
So for example if I want to show you the ELOG logo, I put it here:
If I want to add a comment for an attachment, I write it in the text and just refence the attachment with link. This way is more flexible that adding just a line of text to each attachment, since you can write several lines in the text, make a table etc. etc. |
|