ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1770
|
Mon Mar 13 12:57:33 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.6.1-1671 | Broken thread structure in Forum? |
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. |
1774
|
Wed Mar 15 09:28:42 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.6.1-1668 | Re: elogd 2.6.1 program Crash is repeatable under Windows |
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
|
Attachment 1: Capture.jpg
|
|
Attachment 2: Capture.jpg
|
|
1781
|
Sat Apr 1 15:30:32 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.61 | Re: Anonymous vs user posts |
Chris Warner wrote: | If I have a logbook that will let both registered users Anonymous users post. I would like the author attribute to default to the value in $long_name but if the post is Anonymous display a default text string "Anonymous". Is it possible to do this? |
I added that functionality into the intermediate release 2.6.1-4 which you can download from the ELOG site. |
1783
|
Mon Apr 3 10:35:37 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.1-1681 | Re: Change in encoding close entry |
> Maybe it is a wrong configuration, because in this forum it works well.
> If I change the encoding in the logbook entry I get "Submit modified ELOG entry?",
> and after clicking OK the entry is closed. Because this behavior is on all loggbooks
> it must be a global config entry, but I dont know, which.
>
> ...
> Use Lock = 1
> ...
I comes from using the lock. If you remove that, you won't get this dialog box any more. |
1786
|
Mon Apr 3 16:32:52 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.6 | Re: Numerous questions that I am hoping to get a response on |
Steve Jones wrote: | Stefan, I have several issues/questions that I am still hoping to get an answer on. Any chance? If you would rather you can send email to me directly. |
I'm pretty busy these days, since we have a deadline on April 18th. I started already working weekends, so not much time is left for ELOG. But I hope it will get better by the end of this month. |
1788
|
Mon Apr 3 17:09:19 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.6.1-1668 | Re: elogd 2.6.1 program Crash is repeatable under Windows |
Steve Jones wrote: | BTW, Stefan, unless you can make the most recent version of a Windows eLog available I cannot test the most recent -- I do not have access to a Windows development environment. Solaris-Yes, Linux-Yes, Windoze-No. |
There is a 2.6.1-4 version for Windows for download, which contains the most recent code. |
1790
|
Tue Apr 4 08:15:29 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | | 2.6.1 | Re: Simple math within an elog form |
Steve Jones wrote: | This may sound a little strange but I am trying to determine if it is possible to create a series of attributes that may be assigned an integer value via OPTIONS, and then take the selected values and perform some simple math and display the result. |
This item is already on the wishlist, so I added your vote there. But due to my workload, it will certainly not be implemented in the next few weeks. |
1791
|
Tue Apr 4 20:45:28 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.1-1681 | Re: Change in encoding close entry |
> So if I switch the encoding the whole entry is reloaded, and the JS take it as leaving.
> Is it possible to change this behavior? Changing encoding should be handled different as
> "regular" leaving.
I fixed that in the current SVN version. |