ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
213
|
Tue Feb 11 08:57:39 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: elog notification process causes the email to be truncated when going to Blackberry |
> I just noticed that the notifications I receive from your ELOG system,
> doesn't show anyone in the "TO:" section but myself. Or is ELOG
configured
> to only send myself a message?
This is on purpose. I have many people registered for the Forum. So when a
notification is sent, it is not a good idea if everybody sees everybody
else's mail addresses. Therefor I have
Omit Email to = 1
in the config file. This way the "To:" field is omitted to "hide" the mail
recipients from each other. Your mail client realizes that and fills in your
own address automatically, that's why you only see yourself. Maybe you try
that option, might help with your previous problem as well.
- Stefan |
212
|
Mon Feb 10 23:36:31 2003 |
| eric wooten | wootene@verizon.net | Bug report | | | Find |
When you do a find in elog, records per page (some crazy large number - for
your forum logbook, display 57 entries seem to cause the problem, then
select last year (1 years worth of logs),(don't select printable)
the results appear way off the screen (the message body looks fine, but the
title, etc extend way off the screen).
Printable doesn't have this problem. |
211
|
Mon Feb 10 23:19:50 2003 |
| eric wooten | wootene@verizon.net | Question | | | Re: elog notification process causes the email to be truncated when going to Blackberry |
I just noticed that the notifications I receive from your ELOG system,
doesn't show anyone in the "TO:" section but myself. Or is ELOG configured
to only send myself a message?
> Another Question: Could ELOG be configured to send notifications as a
Blind
> Copy? Just wondering if that would take care of the problem?
>
> > Hi Stefan,
> >
> > Many users have there email forward to Blackberry devices. Although I
> > wasn't aware, it appears the Blackberry has a limit (or maybe one was
set)
> > of how big the message can be (still checking for that though).
> >
> > Previously, a modification was made that addressed the issue of slow ELOG
> > response when saving the elog entry. I think the change was for ELOG to
> > generate one email and send to all the users designated to receive the
> > notification. This caused everyone to show up as "TO" addresses.
> >
> > This change makes the Email header increase in size (length). I guess
the
> > Blackberry counts the Header portion as part of the email size limit.
> >
> > Any ideas?
> >
> > Thanks,
> > Eric |
210
|
Mon Feb 10 23:11:25 2003 |
| eric wooten | wootene@verizon.net | Question | | | Re: elog notification process causes the email to be truncated when going to Blackberry |
Another Question: Could ELOG be configured to send notifications as a Blind
Copy? Just wondering if that would take care of the problem?
> Hi Stefan,
>
> Many users have there email forward to Blackberry devices. Although I
> wasn't aware, it appears the Blackberry has a limit (or maybe one was set)
> of how big the message can be (still checking for that though).
>
> Previously, a modification was made that addressed the issue of slow ELOG
> response when saving the elog entry. I think the change was for ELOG to
> generate one email and send to all the users designated to receive the
> notification. This caused everyone to show up as "TO" addresses.
>
> This change makes the Email header increase in size (length). I guess the
> Blackberry counts the Header portion as part of the email size limit.
>
> Any ideas?
>
> Thanks,
> Eric |
209
|
Mon Feb 10 23:05:36 2003 |
| eric wooten | wootene@verizon.net | Question | | | elog notification process causes the email to be truncated when going to Blackberry |
Hi Stefan,
Many users have there email forward to Blackberry devices. Although I
wasn't aware, it appears the Blackberry has a limit (or maybe one was set)
of how big the message can be (still checking for that though).
Previously, a modification was made that addressed the issue of slow ELOG
response when saving the elog entry. I think the change was for ELOG to
generate one email and send to all the users designated to receive the
notification. This caused everyone to show up as "TO" addresses.
This change makes the Email header increase in size (length). I guess the
Blackberry counts the Header portion as part of the email size limit.
Any ideas?
Thanks,
Eric |
208
|
Fri Feb 7 22:26:13 2003 |
| Nick | Nick@nick.com | Question | | | Re: Lost features since upgrade to 2.3.0 |
> I revised the way links are placed into the summary table, so I could have
> lost some functionality (I did not try all config combinations since there
> are too many now). So I can fix your problem in two ways now: Either always
> have the first item in a list be a link, or have each item be the (same)
> link. What do you think is a better solution?
I think the first option is the better one, having the first columns data in
the list be linkable for example i am using this to store customer
configuration and the list needs to be in alphabetical order so it has to be
the first column but needs to be linkable :)
Would be nice if you can specify which columns data has links as a flag or
setting of some sorts, as opposed to either the first or all, but given a
choice I would want the first column to be the linkable one
My config looks like this
Display search = Customer Name, Account ID, Author, Date, #
I think the better option is first item (being the first column entries) all
have links to the logbook entries (which is how it was in the previous
version)
>
> > Problem 2 - no matter what i try in the config file i cannot get elogd to
> > use stylesheets ive tried specifying and even editing and removing the
> > default.css style sheet i downloaded but it just seems to ignore its
there.
I resolved this problem, many thanks for your help |
207
|
Fri Feb 7 19:52:41 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Lost features since upgrade to 2.3.0 |
> Problem 1 - Since upgrading to version 2.3.0 I seem to have lost the some
> functionality explained below. When i first log into my logbook (i only
> have a single one) it defaults to the summary view and the first field is
> one called Customer Name as opposed to # as i wanted the list sorted by
> this field, the link for that logbook entry is no longer available on the
> first field (being Customer Name) but only on the # field), however if you
> use Summary threaded view the whole line is a link.
I revised the way links are placed into the summary table, so I could have
lost some functionality (I did not try all config combinations since there
are too many now). So I can fix your problem in two ways now: Either always
have the first item in a list be a link, or have each item be the (same)
link. What do you think is a better solution?
> Problem 2 - no matter what i try in the config file i cannot get elogd to
> use stylesheets ive tried specifying and even editing and removing the
> default.css style sheet i downloaded but it just seems to ignore its there.
First question: Does your elog pages have color? If so, the default.css is
loaded correctly. Otherwise your page would contain text but all would be
white.
So I presume you see color, that means your default.css is loaded correctly.
It can now be that your browser caches that stylesheet. I use MS Internet
Explorer and Mozilla and a "reload" on the browsers refreshes the
stylesheet, but you really have to press the "reload" button (or clear the
browser cache). Have you tried that?
- Stefan |
206
|
Fri Feb 7 18:38:56 2003 |
| Nick | nikc@cnic.com | Question | | | Lost features since upgrade to 2.3.0 |
Ive got 2 issues which I cant see to resolve I was wondering if anyone can
help.
Problem 1 - Since upgrading to version 2.3.0 I seem to have lost the some
functionality explained below. When i first log into my logbook (i only
have a single one) it defaults to the summary view and the first field is
one called Customer Name as opposed to # as i wanted the list sorted by
this field, the link for that logbook entry is no longer available on the
first field (being Customer Name) but only on the # field), however if you
use Summary threaded view the whole line is a link.
Is there a flag or setting to the make the first field a link?
Problem 2 - no matter what i try in the config file i cannot get elogd to
use stylesheets ive tried specifying and even editing and removing the
default.css style sheet i downloaded but it just seems to ignore its there.
Any help or advice ?????? |