| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1454
|
Thu Oct 13 13:27:02 2005 |
 | Bertram Metz | bmetz@sbs.com | Question | Linux | 2.6.0-beta | Re: Long lines in printout |
The lines are still cut, if printed on paper.
I played again with the 'message width' parameter, which actually the key parameter in my problem. I saw in the source, that the default value is now 112, but it was 76 in the elog version we'd used previously (V2.5.2). If I set 'message width' to 76 again, it works fine for new entries!
I wrote in the previous reply, that changing 'message width' didn't help. That seems to be the case for entries, which are re-submitted. For new entries it works.
Bertram |
|
1455
|
Thu Oct 13 13:51:55 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.0-beta | Re: Long lines in printout |
| Bertram Metz wrote: | | The lines are still cut, if printed on paper. |
Are you sure? After you change the CSS file, you have to reload the page. I just tried with the very long entry from this thread and got in the Firefox preview window the picture which I attached. The font size of the text body is shrunk such that all lines (except the one very long line) fit on the paper. |
| Attachment 1: printout.jpg
|
|
|
1458
|
Thu Oct 13 17:45:58 2005 |
| Bertram Metz | bmetz@sbs.com | Question | Linux | 2.6.0-beta | Re: Long lines in printout |
You're right. I don't know what I've tested this afternoon 
Without the fixed font the text might get very small, if the line is too long.
I think we'll set 'message width' = 76.
Thanks a lot Stefan! |
|
66315
|
Wed Apr 15 09:26:37 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | All | 2.7.6 | Re: Long cookie content is not handled properly. |
| Simon Patton wrote: | I discovered the infinite loop in 2.7.5 which can happen when a cookie's content is longer that the cookie array
designed to hold it. I also note that this issue has been addressed in 2.7.6, but the solution does not appear
to be correct and it can end up completely confusing the cookie extraction.
In 2.7.5 the code was:
for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; )
if (i < (int) sizeof(cookie)-1)
cookie[i++] = *p++;
While in 2.7.6 is became:
for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n';)
if (i < (int) sizeof(cookie) - 1)
cookie[i++] = *p++;
else
break;
This leaves 'p' pointing to the middle of the cookie's content and I can not see that this is corrected in the loop (sorry if I've missed that).
The solution I used to patch 2.7.5 was the following:
for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; ++p)
if (i < (int) sizeof(cookie)-1)
cookie[i++] = *p;
which simply truncates the contents of the cookie (which is assumed not to be an elogd cookie) but leaves 'p' in the right place to extract the next one. |
You're absolutely right about that. I incorporated your patch into revision #2192. |
|
66798
|
Wed Apr 28 11:09:47 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.77 | Re: Logout, authentication failure causes "redir" |
| Niklas wrote: |
|
When someone logout from my Elog, or the person does not have access to a logbook (due to "Login user =") the person gets a blank webpage with "redir" typed in the upper left corner.
I guess it should redir to some webpage? How can I get it to actually do that? Am I missing something in elogd.cfg?
|
Have you tried the URL = ... statement? |
|
66799
|
Wed Apr 28 16:34:17 2010 |
| Niklas | niklas@hoglund.pp.se | Question | Linux | 2.77 | Re: Logout, authentication failure causes "redir" |
| Stefan Ritt wrote: |
|
| Niklas wrote: |
|
When someone logout from my Elog, or the person does not have access to a logbook (due to "Login user =") the person gets a blank webpage with "redir" typed in the upper left corner.
I guess it should redir to some webpage? How can I get it to actually do that? Am I missing something in elogd.cfg?
|
Have you tried the URL = ... statement?
|
If a user that is not in "Login User =" tries to enter it would be nicer to have a "Access denied", instead of getting the first page again (user just keeps on trying and gets upset)... =) |
|
369
|
Wed Jun 4 15:30:12 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Loging user's activity |
> I was wondering if there is a way to have a more detailed log of users'
> activities?
> Current Logfile = <file> gives a good base for information about
> logins/access to 'protected' logbooks.
>
> What we would like to have is information about when a user reads an ELOG
> entry (to be able to determine the reaction/response time).
>
> For instance the LOG could look sg like this:
> %%user %%datetime %%logbook %%record read/edit/new/delete
Very nice idea, I put it on the wishlist. |
|
864
|
Wed Jan 5 16:04:53 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | | Re: Login/Password request appears twice |
> Have set up 3 top level groups, each with their own password file.
> Ever since users have to 'login' twice to get to the appropriate elog.
> You click on top level group, get to log book and click on the one you want
> and get login/password dialog box, click ok and and you get it again and
> then you finally get into the elog book.
>
> Anything I can check on this behavior?
Sorry my late reply, was very busy these days... (;-) Can you send me your
elogd.cfg so that I can see how you defined your groups?
- Stefan |