Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 685 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  66689   Fri Jan 15 17:36:54 2010 Reply george papalexisgp@emich.eduBug reportWindows2.7.8Re: email message id

Stefan Ritt wrote:

george papalexis wrote:

We noticed some elog email messages were not showing up in our inboxes at random.  What we believe is happening is when a elog entry is created it is assigned a message id that the mail servers will use.  If a message is edited that same message id is used and some mail servers involved will ignore the duplicate message id.  We have also noticed when a elog entry is deleted the next entry created will assume the deleted entry message id and just like above the email will be ignored since it has a duplicate message id. 

The message ID is part of the "user data" of the email, not of the standard email header. So the mail servers "do not know" about the message ID, which make it strange that double messages are filtered. Nobody else reported this problem before. Maybe is it related to your SPAM filter? Can you check if the double entries are classified as SPAM in your case? 

 Here is the mail log:

Jan 12 13:51:54 techies lmtpunix[3184]: dupelim: eliminated duplicate message to user.jf id <neteng-1067@emich.edu> (delivery)

The message id we are experiancing problems with is in the header;

Message-ID: <neteng-1073@emich.edu>

Thank you for the help.

 

 

  66711   Wed Feb 17 17:02:38 2010 Question soren poulsensoren.poulsen@cern.chBug reportLinux2.7.8-2282Problem using attribute type

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).

 

 

 

 

 

  66712   Thu Feb 18 13:21:15 2010 Reply soren poulsensoren.poulsen@cern.chBug reportLinux2.7.8-2282Re: Problem using attribute type

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

 

  66713   Thu Feb 18 15:37:07 2010 Reply soren poulsensoren.poulsen@cern.chBug reportLinux2.7.8-2282Re: Problem using attribute type

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

  66724   Wed Feb 24 15:54:40 2010 Question Ulf Helmerssonulfhe@ifm.liu.seBug reportOtherV2.7.8-227Show Attributes

 This programing have stoped working, I guess after last update.

Elog is running on Solaris.

Ulf Helmersson

 

 

 

Options Type = Journal Article{1}, Proceeding Article{2}, Book chapter{3}, Book{4}, Patent{5}

{1} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Abbrivated journal name, Volume, First page, Year, Elsevier format, AIP/APS format, IOP format

{2} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Conference name, Place, Country, First page, Year, Month.Days, Volume, Elsevier format Proceeding

{3} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Book Title, Editors, Publisher, Place, First page, Year, Elsevier format Book chapter

{4} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Publisher, Place, First page, Year, Elsevier format Book, IOP format Book

{5} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Patent number, Year, First page, Elsevier format Patent

 

  66733   Sat Mar 6 20:53:25 2010 Warning soren poulsensoren.poulsen@cern.chBug reportLinux2.7.8-2282Re: 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

 

  66736   Wed Mar 10 10:36:02 2010 Entry Mirza Ehsanmirza@cpjeddah.comBug reportWindows2.6.1-1681eLog crash

I am using eLog ELOG V2.6.1-1681 which has 7 log books under 8 categories. Out of 7 log books, 2 are daily used. It happened that two weeks back. I modified information on two log books which were not used for quite longtime. Hence using CONFIG, I updated these log books, changing text etc. After that eLog in general started giving error. Any time when we click SUBMIT button in any log book, eLog shows page not found. That submit crashes eLog and as a result elogd service stops. Restarting elogd service, eLog operation comes back and the log which I submitted was actualy saved. Difficulty is that this problem is happening with every single submit action. 

I searched forum and learnt that upgrading eLog to newest version 2.7.8 will solve this problem. Upgrade created more problems, I was not able to open any log, authentication was not accepted. I restored that backup and went back to previous version. eLog started working but with submit error.

If any one can help me in fixing this problem

  66741   Thu Mar 11 15:36:39 2010 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.6.1-1681Re: eLog crash

Mirza Ehsan wrote:

I am using eLog ELOG V2.6.1-1681 which has 7 log books under 8 categories. Out of 7 log books, 2 are daily used. It happened that two weeks back. I modified information on two log books which were not used for quite longtime. Hence using CONFIG, I updated these log books, changing text etc. After that eLog in general started giving error. Any time when we click SUBMIT button in any log book, eLog shows page not found. That submit crashes eLog and as a result elogd service stops. Restarting elogd service, eLog operation comes back and the log which I submitted was actualy saved. Difficulty is that this problem is happening with every single submit action. 

I searched forum and learnt that upgrading eLog to newest version 2.7.8 will solve this problem. Upgrade created more problems, I was not able to open any log, authentication was not accepted. I restored that backup and went back to previous version. eLog started working but with submit error.

If any one can help me in fixing this problem

I propose that you get 2.7.8 working. If the authentication fails, try do do password recovery, or recreated the accounts. 

ELOG V3.1.5-3fb85fa6