| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1741
|
Thu Mar 2 07:15:27 2006 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.6.1-1622 | Re: 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 |
| Alexandre Gauthier | supernaut@underwares.org | Bug report | Linux | 2.6.1-1622 | Re: 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 
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! |
|
1747
|
Sat Mar 4 06:04:53 2006 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.6.1 | Re: Top Groups and logbook directorys |
| Steve Jones wrote: | I am re-working our elog setup and am seriously looking at using the "Top Group" feature. What I like best is the ability to create [global] configurations for a group (or type) of logbook when I host multiple types on the same server. I also like being able to specify a different password file, etc.
A limitation that I run into is I would really like the actual directory names used for storing the logbooks for the different types to be identical - which isn't possible when all logbooks (regardless of context) exist at the same directory level. For example, I might have:
3 physical locations: ABC, DEF, GHI
For each location I want to maintain two *groups* of logbooks - CircuitTests and BoardTests. What I would like to end up with is:
- CircuitTests
----ABC
----DEF
----GHI
- BoardTests
----ABC
----DEF
----GHI
Under current elog this is not possble as far as I know. Since each logbook is a physical directory, each logbook requires a unique name. The concept of a named [global] area fills the bill for all things but it would be nifty if one could do:
[global circuittests]
Logbook dir = circuittestlogbooks
[global boardtests]
Logbook dir = boardtestlogbooks
I suppose the poorman's way of doing this is for each logbook to do the following:
[ABC]
Subdir = boardtestlogbooks/ABC
[DEF]
Subdir = boardtestlogbooks/DEF
[GHI]
Subdir = boardtestlogbooks/GHI
or something like that, but I was hopic for something a little more integrated - like creating the hierarchical stuff via the GUI. Anyway, this probably sounds like a major overhaul, which definitely wouldn't be worth it unless I have completely missed something glaringly obvious.
Thanks! |
| Steve Jones wrote: | | Perhaps it is best to ignore this -- I went for a workaround that I like. I am running into a few quirky things with Top Group but it is likely due to the fact that I have never used it. |
|
|
1749
|
Mon Mar 6 13:06:59 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | 2.6.1 | Re: Find in multiple logbooks returns wrong pages |
This problem has been fixed in SVN revision 1671. |
|
1750
|
Mon Mar 6 13:40:40 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.6.1 | Re: Allow $attributes in "Comment = " option |
| Steve Jones wrote: | | Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks? |
The "Comment =" option for logbooks gives a general comment, like Discussion forum about ELOG for this forum. Since this comment is global, it does not make sense to have $attribute substitution. |
|
1751
|
Mon Mar 6 13:50:07 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.6.1-1668 | Re: require smileys to have whitespace on either side? |
| Glenn Horton-Smith wrote: | It would be nice if elog would only interpret something as a smiley if it is surrounded by whitespace. It can be particularly annoying that an 8 followed by a right paren becomes a "cool" smiley -- e.g., a parenthetical reference to event eighteen (18) becomes mangled... [That was "18" inside the parens.]
Is there already a way to solve this issue (other than always previewing your entries and adding spaces before parans)? Is the feature hard to implement? |
Interpreting smileys only if they are surrounded by whitespace does not solve the problem completely. It will solve it for (1\8), but not if you have (1, \8) (1, 9) in your text. So it's not a good solution. If you have problems with simleys, I would post my text in plain mode, or surround your numbers with [code]...[/code] tags. If you write
[code](1\8)[/code]
then it will look like
(18)
which should be fine. |
|
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. |
|