| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66733
|
Sat Mar 6 20:53:25 2010 |
 | soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.8-2282 | Re: Thread view problem in searches |
|
soren poulsen wrote:
|
|
Hi,
When I upgrade from build 2278 to 2282 the thread view changes when performing searches: The thread children are not indented and there are no "thread icons" in the search list (e.g. like the read right arrow for replies).
On the forum site I also note that the thread view is not indented when performing searches.
Does anyone have an idea ?
Soren
|
This seems to be a bug. I reproduced it with a different browser (Opera) with the default ELOG configuration. When I do Find and select Display Threads I have the message icons but the layout is not correct. Also, all message icons are of the "reply" type even if they are new threads.
This concerns only the latest build 2282.
Soren
|
|
66759
|
Sun Mar 14 20:57:26 2010 |
 | soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.8-2282 | Re: Problem using attribute type |
| Stefan Ritt wrote: |
|
| soren poulsen wrote: |
|
| soren poulsen wrote: |
|
| soren poulsen wrote: |
|
Hi,
This little logbook has a problem:
------------------------
Attributes = Author, Category, Type, Subject, Number
Type Number = numeric
Options Category = General{1}
{1} Options Type = Routine
------------------------
(it was of course more complicated to start with).
When creating a new entry and selecting the Category option, there is a problem with the JavaScript which will populate the Type option.
To avoid the problem, I just comment out the line "Type Number ... "
Is this a bug ?
Thanks for your time
Soren
(P.S. Using a reserved name as an attribute name is maybe not optimal, but it does not seem to be the problem).
|
To overcome this problem it is sufficient to switch language from "Language = french" to "Language = english"
It was a mistake not to include the "global" settings in this bug report.
What probably happens is that something in the French translation (accents ?) disturbs the java scripting.
Soren
|
To use "Language = french" it is necessary to remove or substitute the accent character ' with something else in eloglang.french and then the Javascript code works again.
Soren
|
Indeed it was the JavaScript line
if (document.form1.Number.value != '- garder les valeurs d'origine -') {
which caused the trouble. The "'" character closed the string '- garder les valeurs d', which caused an exception. I changed it to
if (document.form1.Number.value != "- garder les valeurs d'origine -") {
and now it should work fine.
|
Thanks a lot for changing that. Now French should work as well.
Soren |
|
66760
|
Sun Mar 14 21:04:44 2010 |
| soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.8-2282 | Re: Thread view problem in searches |
| Stefan Ritt wrote: |
|
| soren poulsen wrote: |
|
|
soren poulsen wrote:
|
|
Hi,
When I upgrade from build 2278 to 2282 the thread view changes when performing searches: The thread children are not indented and there are no "thread icons" in the search list (e.g. like the read right arrow for replies).
On the forum site I also note that the thread view is not indented when performing searches.
Does anyone have an idea ?
Soren
|
This seems to be a bug. I reproduced it with a different browser (Opera) with the default ELOG configuration. When I do Find and select Display Threads I have the message icons but the layout is not correct. Also, all message icons are of the "reply" type even if they are new threads.
This concerns only the latest build 2282.
Soren
|
That's not a bug, that's a feature 
But honestly, this feature was requested recently and implemented. See https://midas.psi.ch/elogs/Forum/66670. So when searching, the thread organization is broken up and messages are treated independently. If you want to see the thread for a certain entry in you search result page, click on that entry and you will see the full thread above the entry.
|
That sounds fine but I think there is a problem with rendering under Opera. I enclose a screen shot: There is too much white space in the lines, it seems  $
The problem only appears in Find
Soren |
| Attachment 1: elog.jpg
|
|
|
66765
|
Mon Mar 15 18:35:26 2010 |
| soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.8-2282 | Re: Thread view problem in searches |
| Stefan Ritt wrote: |
|
| soren poulsen wrote: |
|
That sounds fine but I think there is a problem with rendering under Opera. I enclose a screen shot: There is too much white space in the lines, it seems $
The problem only appears in Find
|
I just tried myself with V10.50, and things work fine, even in the find page:
Can you try on the forum, just to check if it's specific to your configuration?
|
Thanks. The Forum is fine. The problem is - apparently - specific to my installation. The white space origins in long sequences of " " (repeated); in the lines in Find.
Let me re-install with the latest version and see if I can solve it like that.
Soren |
|
66766
|
Mon Mar 15 18:58:06 2010 |
| soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.8-2282 | Re: Thread view problem in searches |
| soren poulsen wrote: |
|
| Stefan Ritt wrote: |
|
| soren poulsen wrote: |
|
That sounds fine but I think there is a problem with rendering under Opera. I enclose a screen shot: There is too much white space in the lines, it seems $
The problem only appears in Find
|
I just tried myself with V10.50, and things work fine, even in the find page:
Can you try on the forum, just to check if it's specific to your configuration?
|
Thanks. The Forum is fine. The problem is - apparently - specific to my installation. The white space origins in long sequences of " " (repeated); in the lines in Find.
Let me re-install with the latest version and see if I can solve it like that.
Soren
|
I have re-installed the latest, fastest, smartest, brightest version. And it all works perfectly! Thanks a lot for your help.
Soren |
|
66767
|
Tue Mar 16 11:58:55 2010 |
 | soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.8-2282 | Re: Thread view problem in searches |
| soren poulsen wrote: |
|
| soren poulsen wrote: |
|
| Stefan Ritt wrote: |
|
| soren poulsen wrote: |
|
That sounds fine but I think there is a problem with rendering under Opera. I enclose a screen shot: There is too much white space in the lines, it seems $
The problem only appears in Find
|
I just tried myself with V10.50, and things work fine, even in the find page:
Can you try on the forum, just to check if it's specific to your configuration?
|
Thanks. The Forum is fine. The problem is - apparently - specific to my installation. The white space origins in long sequences of " " (repeated); in the lines in Find.
Let me re-install with the latest version and see if I can solve it like that.
Soren
|
I have re-installed the latest, fastest, smartest, brightest version. And it all works perfectly! Thanks a lot for your help.
Soren
|
Everything is fine. But my users do not like that the threads are broken into individual entries and not shown as full threads as before. So I am stuck with the "old" version. This is probably asking for too much but would it be difficult to have a flag to specify if you want to benefit from the new behaviour or keep pre-2282 behaviour (with its inconvenience which led to the presentation change). It could even be a compile tag flag, if it just me (well, my users) who is asking for this.
Soren |
|
66769
|
Wed Mar 17 22:39:59 2010 |
| soren poulsen | soren.poulsen@cern.ch | Question | Windows | 2.7.7 | Re: Fail to connect to SMTP server on WinXP but works on Win2K |
| David Spindler wrote: |
|
| David Spindler wrote: |
|
| Stefan Ritt wrote: |
|
| David Spindler wrote: |
|
| David Spindler wrote: |
|
Fantastic. I forgot the icon and when I resent nothing was left.
Here goes again!
I have been running Elog for years on a Win2K machine with no email problems. I have been forced to move it to a WinXP machine and I always get this message under WinXP: "Error sending Email via "netsvr10.prod.company.com": Cannot connect to server"
I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.
Here is an entry from the elog.log file when it worked under Win2K:
28-Oct-2009 18:28:38 [609144@199.82.127.9] {Generals} NEW entry #0
28-Oct-2009 18:28:38 [609144@199.82.127.9] {Generals} Email from <christophermeyer@fedex.com> to david.spindler@company.com, SMTP host smtp.mail.company.com
28-Oct-2009 18:28:42 [609144@199.82.127.9] {Generals} 220 netsvr10.prod.company.com -- Server ESMTP (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit))
Here is an entry from today's elog.log under WinXP that does not work.
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} NEW entry #0
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} Email from <david.spindler@company.com> to david.spindler@company.com, SMTP host smtp.mail.company.com
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} READ entry #1612
We use an SMTP server without authentication.
|
I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.
06-Mar-2010 10:31:43 [117361@199.81.166.149] {Gbld} READ entry #1691
06-Mar-2010 10:39:10 [117361@199.81.166.149] {Gbld} NEW entry #0
06-Mar-2010 10:39:11 [117361@199.81.166.149] {Gbld} Email from <david.spindler@company.com> to david.spindler@company.com, SMTP host smtp.mail.company.com
|
The only idea I have is that your Windows firewall prevents outgoing network traffic on port 25 (SMTP). You should put an exception into the firewall rule. You can try that by opening a DOS box and entering
telnet smtp.mail.company.com 25
if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.
|
I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.
|
The only idea I have is that your Windows firewall prevents outgoing network traffic on port 25 (SMTP). You should put an exception into the firewall rule. You can try that by opening a DOS box and entering
telnet smtp.mail.company.com 25
if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.
My apologies. I just realized that my first answer to you was lost. I turned the firewall completely off with no luck. I also tried the telnet and it worked. So, it does not appear to be the firewall. I tried the VM's afterwards. Another puzzle is that the Win2K VM works on a WinXP host. It seems like it is only the WinXP elog that fails. I have tried to obtain some our company's IT help with no luck.
|
Just an idea: could you try specifying an IP address for your SMTP server instead of smtp.mail.company.com ?
I would also try to make a manual SMTP session to see if that works.
Otherwise, next step would be to create a VM installed with Wireshark to record the network traffic that ELOG generates when it makes the SMTP connection.
Soren |
|
66772
|
Fri Mar 19 13:45:13 2010 |
| soren poulsen | soren.poulsen@cern.ch | Question | Windows | 2.7.7 | Re: Fail to connect to SMTP server on WinXP but works on Win2K |
| David Spindler wrote: |
|
| David Spindler wrote: |
|
| soren poulsen wrote: |
|
| David Spindler wrote: |
|
| David Spindler wrote: |
|
| Stefan Ritt wrote: |
|
| David Spindler wrote: |
|
| David Spindler wrote: |
|
Fantastic. I forgot the icon and when I resent nothing was left.
Here goes again!
I have been running Elog for years on a Win2K machine with no email problems. I have been forced to move it to a WinXP machine and I always get this message under WinXP: "Error sending Email via "netsvr10.prod.company.com": Cannot connect to server"
I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.
Here is an entry from the elog.log file when it worked under Win2K:
28-Oct-2009 18:28:38 [609144@199.82.127.9] {Generals} NEW entry #0
28-Oct-2009 18:28:38 [609144@199.82.127.9] {Generals} Email from <christophermeyer@fedex.com> to david.spindler@company.com, SMTP host smtp.mail.company.com
28-Oct-2009 18:28:42 [609144@199.82.127.9] {Generals} 220 netsvr10.prod.company.com -- Server ESMTP (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit))
Here is an entry from today's elog.log under WinXP that does not work.
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} NEW entry #0
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} Email from <david.spindler@company.com> to david.spindler@company.com, SMTP host smtp.mail.company.com
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} READ entry #1612
We use an SMTP server without authentication.
|
I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.
06-Mar-2010 10:31:43 [117361@199.81.166.149] {Gbld} READ entry #1691
06-Mar-2010 10:39:10 [117361@199.81.166.149] {Gbld} NEW entry #0
06-Mar-2010 10:39:11 [117361@199.81.166.149] {Gbld} Email from <david.spindler@company.com> to david.spindler@company.com, SMTP host smtp.mail.company.com
|
The only idea I have is that your Windows firewall prevents outgoing network traffic on port 25 (SMTP). You should put an exception into the firewall rule. You can try that by opening a DOS box and entering
telnet smtp.mail.company.com 25
if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.
|
I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.
|
The only idea I have is that your Windows firewall prevents outgoing network traffic on port 25 (SMTP). You should put an exception into the firewall rule. You can try that by opening a DOS box and entering
telnet smtp.mail.company.com 25
if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.
My apologies. I just realized that my first answer to you was lost. I turned the firewall completely off with no luck. I also tried the telnet and it worked. So, it does not appear to be the firewall. I tried the VM's afterwards. Another puzzle is that the Win2K VM works on a WinXP host. It seems like it is only the WinXP elog that fails. I have tried to obtain some our company's IT help with no luck.
|
Just an idea: could you try specifying an IP address for your SMTP server instead of smtp.mail.company.com ?
I would also try to make a manual SMTP session to see if that works.
Otherwise, next step would be to create a VM installed with Wireshark to record the network traffic that ELOG generates when it makes the SMTP connection.
Soren
|
Thanks, I will give it a try.
|
I cannot send an email from elog using an IP address.
I can send an email manually through SMTP.
I will have to locate a copy of wireshark and set up a VM. I cannot access any site that has it from here.
|
We will get there. What is the output of "ipconfig /all" of the Win2K and WinXP machines respectively ?
Maxbe the DNS suffix is missing on XP ?
Soren
|
|