| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66213
|
Thu Feb 19 18:19:12 2009 |
 | Bill Pier | bpier@clove.org | Question | All | 2.7.3 | Re: scrollable text section only when viewing a log entry |
| Bill Pier wrote: |
|
| IStefan Ritt wrote: |
|
| Bill Pier wrote: |
|
| Stefan Ritt wrote: |
|
| Bill Pier wrote: |
|
Is there a way, option, feature to setup the text section only to be scrollable when viewing a log entry, such that the header (meta info) section stays fixed?
|
Unfortunately no.
|
Well, I tinkered a bit with a journal entry display page and found that without having to suggest the flavor-of-the-month web design mantra of "replace table layout with CSS only", just a few CSS tweaks can enable exactly what I am desiring.
For your consideration, here are the tweaks I made to get a fixed header and footer section with a scrollable journal entry section in the middle:
- moved the journal entry content and footer line (elog version info) out of the layout table structure, into their own div sections;
- in the style sheet, added attribute "position:fixed" to the "frame table" section;
- in the style sheet, added attribute sections for journal entry content and footer div sections:
- #content: overflow:auto;position:fixed;top:230px;bottom:30px;width:100%;
- #footer: text-align:center;bottom:0;position:fixed;width:100%;
Now as I'm not a web designer by trade and not intimately familiar with CSS nuances, I used the time honored method of documentation lookup with trial and error.
In any case, it worked and displays exactly the way I wanted; please do consider this for a future elog release.
|
Apparently you downloaded an ELOG page and modified it manually. Can you send me the modified page, it then would be easier for me to implement it (I can shorten "my" trial and error phase..)
|
Yes, you are correct, I did simply take a sample page from logs and tinker with the html and css file, with the changes enumerated previously. I have attached the tweaked sample html elog log page and css file, along with a few of the standard elog png files to complete the page with some semblance of the normal display.
Thu Feb 19 18:18:20 2009 Did this suggestion ever get considered for implementation?
|
|
|
66212
|
Wed Feb 18 20:14:04 2009 |
 | Stefan Ritt | stefan.ritt@psi.ch | Info | Windows | 2.7.5 | Re: How to share with others |
| Nuruzzaman wrote: |
|
Please tell me how to share my elog with people.
|
Connect your PC to the internet and tell everybody the URL. Make sure the Windows Firewall allows remote access. |
|
66211
|
Wed Feb 18 20:03:12 2009 |
| Nuruzzaman | nur@jlab.org | Info | Windows | 2.7.5 | How to share with others |
Please tell me how to share my elog with people. |
|
66210
|
Tue Feb 17 12:28:19 2009 |
| Steve Williamson | StephenWilliamson@Barnsley.gov.uk | Question | Linux | 2.7.5 | Re: Attachments |
| Stefan Ritt wrote: |
|
| Steve Williamson wrote: |
|
Also, on attachments, if I click on the attachment icon (paperclip) on the list page the URL encodes "/" as "%2f", e.g.
http://xxx.xxx.xxx.xxx:8080/Change_Log/..%2FChange_Log%2F090205_123135%2FCHANGE_CONTROL_NOTICE_050209.doc and I get the following error:
"Invalid URL: Change_Log/..%2FChange_Log%2F090205_123135%2FCHANGE_CONTROL_NOTICE_050209.doc" . If I then change all occurrences of "%2f" to "/" the link works.
|
You have an old version of elog, this bug has been fixed some time ago. Have a look for example at https://midas.psi.ch/elogs/Linux+Demo/.
If you click on a peperclip there, the attachment is shown correctly.
|
Thanks - just downloaded and compiled the latest version and all is well |
|
66209
|
Sat Feb 14 17:49:59 2009 |
| ermirza erekose | mirza98@fastmail.net | Question | Linux | 2.7.5-2130 | Re: Internal error, no valid header! |
| ermirza erekose wrote: |
|
| Stefan Ritt wrote: |
|
| ermirza erekose wrote: |
|
I got this error message when trying to upload 17K text file as attachment. Any idea why ? It's a fresh installed elog and not much configuration done yet.
|
No, no idea. I usually put several MB attachments into elogs without problems. Can you try with the demo logbook https://midas.psi.ch/elogs/Linux+Demo/. Maybe you have an old version of elog?
|
No problem attaching big files on F10 or CentOS 4.7. The one that is having issue was on JeOS-8.0.4 - Ubuntu ;-). All tested with ELOG version 2.7.5 build 2130.
|
Correction. The OSes are OK. But don't use Opera when uploading big files. |
|
66208
|
Fri Feb 13 16:57:02 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.7.5 | Re: frequent crashes on SL4 |
There was a general problem in submitting entries. If the TCP connection between the browser and elog
disconnects during the transmission and only part of the request gets transferred, it consistently
crashed elog. The probability for this is large if you have a slow connection and long attachments. The problem
has been fixed in SVN revision 2174, so please upgrade and try again. |
|
66207
|
Fri Feb 13 03:58:46 2009 |
| ermirza erekose | mirza98@fastmail.net | Question | Linux | 2.7.5-2130 | Re: Internal error, no valid header! |
| Stefan Ritt wrote: |
|
| ermirza erekose wrote: |
|
I got this error message when trying to upload 17K text file as attachment. Any idea why ? It's a fresh installed elog and not much configuration done yet.
|
No, no idea. I usually put several MB attachments into elogs without problems. Can you try with the demo logbook https://midas.psi.ch/elogs/Linux+Demo/. Maybe you have an old version of elog?
|
No problem attaching big files on F10 or CentOS 4.7. The one that is having issue was on JeOS-8.0.4 - Ubuntu ;-). All tested with ELOG version 2.7.5 build 2130.
|
|
66206
|
Thu Feb 12 17:13:05 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.7.5 | Re: frequent crashes on SL4 |
Hi Devin,
first of all, your stack traces are only of limited use for me. This typically happens
if you attach gdb to a running process, then you get something like
#0 0x080b2f8a in decode_post ()
#1 0x00000100 in ?? ()
#2 0x00000000 in ?? ()
(note the ??). If you run elogd directly from gdb, the stack trace contains much more information:
[meg@megon elog]# gdb elogd
...
(gdb) run
...
Server listening on port 8080 ...
Program received signal SIGINT, Interrupt.
0x0000003cb48c78d3 in __select_nocancel () from /lib64/libc.so.6
(gdb) where
#0 0x0000003cb48c78d3 in __select_nocancel () from /lib64/libc.so.6
#1 0x000000000046ea51 in server_loop () at src/elogd.c:27688
#2 0x0000000000471de8 in main (argc=1, argv=0x7fffe2b9bf18) at src/elogd.c:29018
(gdb)
including the line numbers, arguments etc. So please try to start elogd from inside gdb
and then reproduce your crash.
Your first problem seems to be related to some contents of your elogd.cfg, since in
one stack dump I saw a
strlen()
...
getcfg()
Here, the getcfg() function is called to retrieve some configuration from elogd.cfg.
Maybe you have a very long line, or the file is otherwise corrupt. Please check that
carfully and send me your elogd.cfg so that I can have a look myself. Usually it helps
to remove one line after the other and check when the problem disappears.
Your other problem which has the decode_post() in the stack dump seems to be related
to the case when you upload an entry (or attachment), and the TCP link breaks in
the middle. Probably the error handling in such a case is not correct. I will try
to reproduce this, although I don't have a satellite network.
Best regards,
Stefan |