Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 686 of 807  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  66743   Thu Mar 11 15:44:01 2010 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.8-2282Re: Thread view problem in searches

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. 

  66745   Fri Mar 12 08:18:06 2010 Entry Cliff Shawcliff.shaw@stratosglobal.comBug reportMac OSX2.7.8 Elogd crashes when closing more than ten entries

Hi Stefan,

I have noticed a problem when closing multiple log entries i.e entries which have more than 10 threads. I use Select -> Click the box that appears next to the thread I wish to close -> Edit.

As soon as I click on Edit the elogd service crashes and Windows displays an error message window. The only work around has been opening up all the threads and individually changing the "Status" to Closed. 

Forgive me if this issue has been raised before but I have looked throughout the Forum and could not see anyone experiencing the same problem.

Thanks

Cliff

  66749   Fri Mar 12 09:27:25 2010 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.8-2282Re: Problem using attribute type

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.

  66754   Fri Mar 12 12:59:25 2010 Reply Stefan Rittstefan.ritt@psi.chBug reportOtherV2.7.8-227Re: Show Attributes

Ulf Helmersson wrote:

 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

 

The option

Show Attributes =

has been changed to

Show Attributes Edit =

to distinguish between normal entry display an edit mask. So please adjust your configuration file and everything will be fine again.

  66755   Fri Mar 12 13:54:14 2010 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX2.7.8 Re: Elogd crashes when closing more than ten entries

Cliff Shaw wrote:

Hi Stefan,

I have noticed a problem when closing multiple log entries i.e entries which have more than 10 threads. I use Select -> Click the box that appears next to the thread I wish to close -> Edit.

As soon as I click on Edit the elogd service crashes and Windows displays an error message window. The only work around has been opening up all the threads and individually changing the "Status" to Closed. 

Forgive me if this issue has been raised before but I have looked throughout the Forum and could not see anyone experiencing the same problem.

Unfortunately I cannot reproduce your error. In my test set-up it works fine, so it might be related to your configuration. Can you send me your config file, a zip with the needed logbook entries (xxxxxxa.log files), and a recipe what to click exactly in what order.

  66758   Sat Mar 13 09:40:37 2010 Reply Mirza Ehsanmirza@cpjeddah.comBug reportWindows2.6.1-1681Re: eLog crash

Stefan Ritt wrote:

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. 

 Thanks for the reply. I found problem with existing version. I opened log book group  without  opening log book details in configuration, that is why at submitting or opening elog was not able to find log book for that group and was getting lost.

Regarding moving to 2.7.8, I want to know that in this new version file location for pwd and log books will remain same or are changed. If changed then I have to change location manually. Also how I can perform password recovery.

  66759   Sun Mar 14 20:57:26 2010 Reply soren poulsensoren.poulsen@cern.chBug reportLinux2.7.8-2282Re: 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 Reply soren poulsensoren.poulsen@cern.chBug reportLinux2.7.8-2282Re: 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
elog.jpg
ELOG V3.1.5-3fb85fa6