Re: restrict access, posted by Stefan Ritt on Fri Jun 23 13:43:03 2006
|
| Gerald Ebberink wrote: | | As you can see, I have implemented a temporary fix in the way of allowing only certain hosts access. But where does this Internal error come from. |
I only can identify this error if you send me your current ("de-sensified") elogd.cfg. |
|
Re: Corrupt page link, posted by Stefan Ritt on Wed Jul 5 12:51:25 2006
|
| Arno Teunisse wrote: | Just installed the previous version :
====================================
[C:\Program Files\ELOG]elogd -c elogd.cfg
elogd 2.6.1 built May 24 2006, 08:59:09 revision 1688
Indexing logbooks ... done
Server listening on port 8080 ...
And the problem is gone. !!!!
problem is in version :
==========================
[C:\Program Files\ELOG1]elogd -c elogd.cfg
elogd 2.6.1 built Jun 13 2006, 08:43:21 revision 1691
Indexing logbooks ... done
Server listening on port 8080 ...
|
Thanks for your detailed information. The hint with the two different revisions heally helped. I fixed that in revision 1695, and made an intermediate release 2.6.1-7. This will fix the problem. Can you please check that this is working? |
|
Re: Canīt run command "make" in OSX, posted by Stefan Ritt on Mon Jul 10 11:15:25 2006
|
| Gerald Ebberink wrote: | | This sounds like something I have not encountered, so I think you'll need to wait for Mr. Ritt to solve this. |
No, I can't solve this becaue I have no MAC.
Sorry,
Stefan |
|
Re: Setting Subject for ELog email notification, posted by Stefan Ritt on Thu Jul 13 08:11:33 2006
|
| Alan Stone wrote: | Hi,
I have the following elogd.cfg syntax:
; Email notification
Suppress Email to users = 1
Omit Email To = 1
User Email Subject = $subject
Use Email Heading Edit = $subject
Email Report Notify-CMSROC = alstone@fnal.gov
1) The subject is using some default, instead of capturing the $subject string (as
it does with Reply). |
You made a typo. It should be
Use Email Subject = $subject
instead of User Email ...
| Alan Stone wrote: | | 2) I want to control the output header "A new entry...". |
You do with with
Use Email Heading = $subject
The option Use Email Heading Edit = $subject is only for entries which are edited (as opposed to new entries). Just read the manual!
| Alan Stone wrote: | 3) The formatting of email body is awkward. For example, "AuthorAlan Stone"
should have at least a space, and maybe a hyphen or colon, "Author: Alan Stone" |
The email is formatted in HTML. Standard email programs like Thunderbird display them properly. If you email client has a problem with it, you can switch to plain text encoding with
Email encoding = 1
Best regards,
Stefan |
|
Re: Inserting images via Internet Explorer, posted by Stefan Ritt on Thu Jul 13 15:16:53 2006
|
| Elaine Cristina Franchini dos Anjos wrote: | I observed that there is a difference between IE and others browsers.
When I use "insert image" button in Netscape, for instance,
it creates automatically a tag like [IMG]elog:1/1[/IMG] and
includes an attachment in the ELOG entry.
When a try to do the same action in Internet Explorer, only
the attachment is created without the tag [IMG]elog:1/1[/IMG] . |
This is a problem of the JavaScript implementation of Internet Explorer. After some externsive research I found now a way to convince IE to do the right thing. The fix is contains in SVN revision 1701 and will be released with 2.6.2-2 soon. |
|
Re: Elogd.exe crashes on windows, posted by Stefan Ritt on Thu Jul 13 15:25:44 2006
|
| Tim Fowler wrote: | I have elog setup to send emails based on the priority of one of the attributes. When a new entry is created, the emails are sent successfully, however if the entry is edited or if you changed the attribute, elogd.exe will crash with a memory access error.
I have tried this and received the same results on different computers and different versions on Elog down to versions 2/6.0 beta 5. (it works correctly in that version).
The attribute in question is setup something like below:
Attributes = Ticket #, Site, Shift, Type, Area, System Name, Description, Priority, Status, Total Down Time, Last Revision
...(omitted config)
Options Priority = High, Medium, Low
...(omitted config)
Use Email Subject = $Site -- $System Name $Description
Use Email From = testuser@myexample.com
;Send email if priority is set to high
Email Priority High = testuser2@myexample.com
Display Email recipients = 1
Email Format = 14 |
This problem has now been fixed in version 2.6.2. |
|
Re: astonished icon, posted by Stefan Ritt on Sat Jul 15 17:58:46 2006
|
| Elaine Cristina Franchini dos Anjos wrote: | Hi Stefan,
I've been trying to use the astonished icon, but the preview or entry
display shows only a broken image.
I found in the elogd.c at line 5556 :
{"8o", "<img src=\"%sicons/eek.png\">"}
I copied the "astonished.png" to "eek.png" and it worked.
Is it the reason of the problem ? ?) |
Actually the C code should be "astonished.png" instead of "eek.png". I changed that in revision 1704. BTW, thanks for the Brazilian translation.  |
|
Re: Duplicate of a reply should be a reply, posted by Stefan Ritt on Mon Jul 17 13:49:37 2006
|
| Gerald Ebberink wrote: | Hello everybody
This weekend I found that if I duplicate a reply it does not become a reply it self.
Is this on purpouse?
I have been through the source a little (not much time for that) and I can not find a reason where the "in reply to" value is dropped.
Could anyone give me an pointer? |
This is on purpuse. The Duplicate functionality is ment to "clone" an existing entry, to save some typing work if an existing entry contains most of what one wants in a new entry. If one duplicates a reply, it is detached from the original thread, so there is not entry to attach the duplicate to. I guess you want to make a new reply to an existing entry, and then have another existing reply as a template for that, but this is not possible. If I would not drop the "in reply to" value, the duplicate would point to the wrong entry. |