ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1870
|
Wed Jul 5 00:18:29 2006 |
| Arno Teunisse | arno.teunisse@hetnet.nl | Bug report | Windows | 2.6.1-6 | Re: Corrupt page link |
Ulrich Trüssel wrote: | If a loggbook contains more than one page of entries, above and under the list are links for changing the page by number (or privous / last and all) conatining links looking like "http://localhost:8080/logbook/page2?mode=mode". This is the correct link and will work until Version 2.6.1-5!
In Version 2.6.1-6 the link is corrupted and look always like "http://localhost:8080/logbook/pag" |
In this version, the above is true. It also has corrupted entries when clicking : Full | Summary | Threaded.
On MSExplorer and Firefox only a part of the link is shown in the left-down corner of the browser :
http://localhost:8080/?mo
No matter what button you click.
It should be : http://localhost:8080/?mode=full
http://localhost:8080/?mode=Summary
http://localhost:8080/?mode=Attachments
I'v tested is with the default elogd.cfg file which comes with the installation.
Something is going wrong here.
When importing a csv text file the above is introduced also.
Just installed the previous version :
====================================
[C:\Program Files\ELOG]elogd -c elogd.cfg
elogd 2.6.1 built May 24 2006, 08:59:09 revision 1688
Indexing logbooks ... done
Server listening on port 8080 ...
And the problem is gone. !!!!
problem is in version :
==========================
[C:\Program Files\ELOG1]elogd -c elogd.cfg
elogd 2.6.1 built Jun 13 2006, 08:43:21 revision 1691
Indexing logbooks ... done
Server listening on port 8080 ...
I love elog , for it's simplicity,
but will not upgrade to the lastest release untill this is solved. |
1871
|
Wed Jul 5 12:51:25 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.6.1-6 | Re: Corrupt page link |
Arno Teunisse wrote: | Just installed the previous version :
====================================
[C:\Program Files\ELOG]elogd -c elogd.cfg
elogd 2.6.1 built May 24 2006, 08:59:09 revision 1688
Indexing logbooks ... done
Server listening on port 8080 ...
And the problem is gone. !!!!
problem is in version :
==========================
[C:\Program Files\ELOG1]elogd -c elogd.cfg
elogd 2.6.1 built Jun 13 2006, 08:43:21 revision 1691
Indexing logbooks ... done
Server listening on port 8080 ...
|
Thanks for your detailed information. The hint with the two different revisions heally helped. I fixed that in revision 1695, and made an intermediate release 2.6.1-7. This will fix the problem. Can you please check that this is working? |
1921
|
Sun Sep 3 23:16:31 2006 |
| Arno Teunisse | arno.teunisse@hetnet.nl | Bug report | Windows | 2.6.1-6 | Re: Corrupt page link |
Stefan Ritt wrote: |
Arno Teunisse wrote: | Just installed the previous version :
====================================
[C:\Program Files\ELOG]elogd -c elogd.cfg
elogd 2.6.1 built May 24 2006, 08:59:09 revision 1688
Indexing logbooks ... done
Server listening on port 8080 ...
And the problem is gone. !!!!
problem is in version :
==========================
[C:\Program Files\ELOG1]elogd -c elogd.cfg
elogd 2.6.1 built Jun 13 2006, 08:43:21 revision 1691
Indexing logbooks ... done
Server listening on port 8080 ...
|
Thanks for your detailed information. The hint with the two different revisions heally helped. I fixed that in revision 1695, and made an intermediate release 2.6.1-7. This will fix the problem. Can you please check that this is working? |
Sorry for my ( very ) late answer , But yes the problem is GONE after installing the new release? Thanks. |
1752
|
Mon Mar 6 14:04:12 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.6.1-1660 | Re: Crafted URL causes elog to coredump |
Steve Jones wrote: | While playing with TOP GROUP I managed to get elog 2.6.1 1660 on Solaris 9 to coredump. Since I didn't really understand TOP GROUP I tried a URL where I had http://elog.server.com/topgroupname/logbookname. Putting that logbookname at the end caused elog to dump.
Can this be reproduced by others? |
No. This forum has the "elog" as the top group, "Forum" as the logbook, so if I write
http://midas.psi.ch/elogs/elog/Forum
it does not crash. |
1753
|
Mon Mar 6 17:35:52 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1660 | Re: Crafted URL causes elog to coredump |
Stefan Ritt wrote: |
Steve Jones wrote: | While playing with TOP GROUP I managed to get elog 2.6.1 1660 on Solaris 9 to coredump. Since I didn't really understand TOP GROUP I tried a URL where I had http://elog.server.com/topgroupname/logbookname. Putting that logbookname at the end caused elog to dump.
Can this be reproduced by others? |
No. This forum has the "elog" as the top group, "Forum" as the logbook, so if I write
http://midas.psi.ch/elogs/elog/Forum
it does not crash. |
|
1755
|
Mon Mar 6 17:45:18 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.6.1-1660 | Re: Crafted URL causes elog to coredump |
No, the above link just works fine, just click it. |
1756
|
Mon Mar 6 18:04:39 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1660 | Re: Crafted URL causes elog to coredump |
Stefan Ritt wrote: |
No, the above link just works fine, just click it. |
Quote: | I was afraid to try . Ok, then the issue *might* be rev 1660 or perhaps the fact that compiled under Solaris it does this. Any suggestions on how to find out? |
|
1757
|
Mon Mar 6 18:06:32 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1660 | Re: Crafted URL causes elog to coredump |
Stefan Ritt wrote: |
No, the above link just works fine, just click it. |
Quote: | I was afraid to try . Ok, then the issue *might* be rev 1660. On my production version running 2.5.3 I get the expected "Invalid URL: <name>" box. Any suggestions on how to find out? |
|