ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69847
|
Sun Dec 8 22:00:32 2024 |
| Liam Gaffney | liam.gaffney@liverpool.ac.uk | Request | Linux | commit 6ee1005 | Reuqest to extract X-Forwarded-Name and X-Forwarded-Email when using webserver |
When using the Webserver authentication in combination with "File" and "Self register = 3", it is possible to keep track of registrations and control access still. This is very useful, and upon clicking on the logbook for the first time, the user is asked to register by typing their username, full name and email address.
First issue here is that they can still edit the box with their username, which might cause confusion if somebody decides to choose a different username and is then surprised about why they cannot automatically login again. Is it possible to lock this field from being edited?
The second issue is more minor, but the user has to manually type their name and email address, even though the webserver may already be able to provide this information in the headers. Specifically, it would be useful to read the name from the X-Forwarded-Name header and email address from the X-Forwarded-Email header.
My config file snippet is below:
Authentication = Webserver, File
allow password change = 0
Password file = webserver.passwords
Self register = 3
|
148
|
Fri Nov 1 13:33:01 2002 |
| Willem Koster | W.Koster@rc.rug.nl | Request | | | wrapping of text in edit field |
I noticed a long url got hard-wrapped when I entered a long one, I patched
the source code. I don't know if this was done intentionally, otherwise you
might want to change this also.
diff elogd.c elogd.c.org
4468c4468
< rsprintf("<textarea rows=20 cols=%d wrap=soft name=Text>", width);
---
> rsprintf("<textarea rows=20 cols=%d wrap=hard name=Text>", width);
BTW, why is the editor window 20 rows by 76 columns ?
(20 is fixed in the source code, but 76 is the width-variable that is set
hard to:
/* set textarea width */
width = 76;
Now I don't like both parameters. 20 is too long for my display (1024x768)
and 76 is too short. Something dynamically would be cool, but a parameter
somewhere in a config file would also be acceptable. (just a thought, makes
it easier to upgrade) |
149
|
Fri Nov 1 13:39:41 2002 |
| Willem Koster | W.Koster@rc.rug.nl | Request | | | New ELOG entry |
When I make a new entry I get an email with
subject: New ELOG entry
But when I or someone else changes an entry I also get an email with a
subject: New ELOG entry
I would prefer to see "Changed" , "Edited", or "Updated". This is beyond my
programming capabilities so I enter this request. |
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 |
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 |
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 |
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. |
246
|
Thu Mar 13 17:30:16 2003 |
| nick | nick@nick.com | Bug report | | | Problems with 2.3.2 |
Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to
port bindings, basically im running elog bound to port 81 and when i
install the new RPM it refuses to bind to this port, i tried port 8080 and
that worked fine
Any ideas ? |