Re: Inline images URL not working, posted by Stefan Ritt on Thu Mar 2 07:15:27 2006
|
| 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. |
|
Re: Re: Inline images URL not working, posted by Alexandre Gauthier on Thu Mar 2 14:35:54 2006
|
| 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 
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! |
Crafted URL causes elog to coredump, posted by Steve Jones on Sat Mar 4 06:08:29 2006
|
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? |
|
Re: Find in multiple logbooks returns wrong pages, posted by Stefan Ritt on Mon Mar 6 13:06:59 2006
|
This problem has been fixed in SVN revision 1671. |
|
Re: Crafted URL causes elog to coredump, posted by Stefan Ritt on Mon Mar 6 14:04:12 2006
|
| 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. |
|
Re: Crafted URL causes elog to coredump, posted by Steve Jones on Mon Mar 6 17:35:52 2006
|
| 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. |
|
|
Re: Crafted URL causes elog to coredump, posted by Stefan Ritt on Mon Mar 6 17:45:18 2006
|
No, the above link just works fine, just click it. |
|
Re: Crafted URL causes elog to coredump, posted by Steve Jones on Mon Mar 6 18:04:39 2006
|
| 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? |
|