Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 637 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 636, 637, 638 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  1741   Thu Mar 2 07:15:27 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.1-1622Re: Inline images URL not working

Alexandre Gauthier wrote:
Whenever I try to insert an inline picture by using the 
elog:1741/1
paths with ELCode, the link becomes "logbookname2/1" (Where logbookname is the name of my logbook) and hence, doesn't work. I recall that it worked once. The image did not display, but the URL seemed correct...


The problem has been fixed in version 2.6.1-3, so just upgrade.


Alexandre Gauthier wrote:
EDIT: i inserted a space in the elog URL above because regardless of the code brackets, it would still get interpreted.


You have to put a "\" in front of everything which should not get converted into a link, so elog:1741/1 does not get interpreted.
  1742   Thu Mar 2 14:35:54 2006 Reply Alexandre Gauthiersupernaut@underwares.orgBug reportLinux2.6.1-1622Re: Re: Inline images URL not working

Stefan Ritt wrote:

Alexandre Gauthier wrote:
Whenever I try to insert an inline picture by using the 
elog:1741/1
paths with ELCode, the link becomes "logbookname2/1" (Where logbookname is the name of my logbook) and hence, doesn't work. I recall that it worked once. The image did not display, but the URL seemed correct...


The problem has been fixed in version 2.6.1-3, so just upgrade.


Alexandre Gauthier wrote:
EDIT: i inserted a space in the elog URL above because regardless of the code brackets, it would still get interpreted.


You have to put a "\" in front of everything which should not get converted into a link, so elog:1741/1 does not get interpreted.


Hello Smile

This is what I have done, I checked out the trunk from subversion and built it inside my powerpc QEMU. I just updated the executables and the elcode.js file, and now it works.

Thanks!
  1748   Sat Mar 4 06:08:29 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1660Crafted URL causes elog to coredump
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?
  1749   Mon Mar 6 13:06:59 2006 Reply Stefan Rittstefan.ritt@psi.chBug report 2.6.1Re: Find in multiple logbooks returns wrong pages
This problem has been fixed in SVN revision 1671.
  1752   Mon Mar 6 14:04:12 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.6.1-1660Re: 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 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1660Re: 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.



Quote:
Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.
  1755   Mon Mar 6 17:45:18 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.6.1-1660Re: Crafted URL causes elog to coredump

Steve Jones wrote:
Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.


No, the above link just works fine, just click it.
  1756   Mon Mar 6 18:04:39 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1660Re: Crafted URL causes elog to coredump

Stefan Ritt wrote:

Steve Jones wrote:
Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.


No, the above link just works fine, just click it.



Quote:
I was afraid to try Big grin . 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?
Goto page Previous  1, 2, 3 ... 636, 637, 638 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6