| 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. |
| Yoshio Imai wrote: | | I noticed that this thread seems to be broken in the Forum. When I view the thread start in single view (http://midas.psi.ch/elogs/Forum/1739), I have access to all subsequent posts, but the first reply seems to be interpreted like a new thread, i.e. when clicking onto it (http://midas.psi.ch/elogs/Forum/1741), the thread start is no longer displayed and accessible in the list of posts. Is this intentional, or is it a bug? |
Some how it got screwed up, such that ID 1741 did not have a back-link to 1739. I have no clue how this could have happened, but I fixed it by manually editing the log file. |
| Steve Jones wrote: | | Stefan, I have previously reported that elog crashes with a specific URL -- I have now re-created the crash running under WindowsXP Pro using the pre-packaged Windows installation that I just downloaded. I am attaching screenshots, etc. for your information but I think the source of the problem stems from using "Top Group". I hope that you are able to look into this as I have logged other issues that i believe are specifically related to the use of the Top Group feature. I am also including the .cfg that I used on my Windows box which is the same .cfg that I use in our Solaris environment. |
Steve,
again I could not reproduce your problem. See the attached screenshots. It just works fine with me (of course I miss the HTML files for the header and footer). I use however the most recent version of elog (Revision 1675). I also have a different password file. So try the following:
- look into your password file (it's a simple XML text file), it should contain something like
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
<user>
<name>stefan</name>
<password>zFDkjoZsg==</password>
<full_name>Stefan Ritt</full_name>
<email>stefan.ritt@psi.ch</email>
<last_logout>Thu Feb 23 15:35:19 2006</last_logout>
<last_activity>Wed Mar 15 09:22:02 2006</last_activity>
<email_notify>
<logbook>demo</logbook>
</email_notify>
</user>
</list>
- make sure that you have the most recent version of elogd. Try at least elog261-3.exe under Windows.
- are you sure you need top groups? Top groups are ment for groups of logbooks which are completele unrelated, like from different departments, with different admins etc. Historically top groups were implemented because some elog installations had several elogd servers running in parallel for different departments. In you case, I suspect that "normal" groups might be enough, like:
Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs = TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL
|