ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 382 of 808

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6457 Entries

Goto page Previous 1, 2, 3 ... 381, 382, 383 ... 806, 807, 808 Next

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 "&nbsp" (repeated); in the lines in Find.

Let me re-install with the latest version and see if I can solve it like that.

Soren

66764

Mon Mar 15 13:20:17 2010

Re: Invalid URL for groups beneath top groups in overview page

Stefan Ritt wrote:

Bertram Metz wrote:

Hi,

I'm trying to implement top groups and started with the sample configuration shown in the 'Syntax of elogd.cfg' chapter of the documentation. But now I'm facing a problem with the links in the logbook selection page.

Here's my group configuration:

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1

The selection page for the top groups is displayed correctly, but the URL for the groups beneath the top group is incorrect. The URL for the Linux PCs group for instance is http://localhost:8080/engineering/engineering/ . The URLs for the logbooks within the Linux PCs groups is correct (e.g. http://localhost:8080/Debian/)

Has anybody an idea what's going wrong in y configuration?

Bertram

Thanks for reporting this bug. I fixed it in the intermediate release 278-4 which is ready for download.

Thanks for the quick bug fix.

Bertram

66763

Mon Mar 15 11:21:30 2010

Re: Invalid URL for groups beneath top groups in overview page

Bertram Metz wrote:

Hi,

Here's my group configuration:

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1

Has anybody an idea what's going wrong in y configuration?

Bertram

Thanks for reporting this bug. I fixed it in the intermediate release 278-4 which is ready for download.

66762

Mon Mar 15 09:29:11 2010

Invalid URL for groups beneath top groups in overview page

Hi,

Here's my group configuration:

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1

Has anybody an idea what's going wrong in y configuration?

Bertram

Attachment 1: elogd.cfg

[global]
Port=8080
Logbook tabs = 1
Expand selection page = 0
;Main tab = "Overview"
Use Lock = 1
Default encoding = 1
Resolve host names = 0


Logfile = elogd.log
Logging level = 3

Logout to main = 1
Options Author = BMetz  
Admin user = BMetz

Password file = ./passwd
;Protect selection page = 0

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1


[Red Hat]
Comment = Red Hat Logbook
Time format = %Y-%m-%d 

[Debian]
Comment = Debian Logbook
Time format = %Y-%m-%d 

[Mandrake]
Comment = Mandrake Logbook
Time format = %Y-%m-%d 

[NT]
Comment = NT Logbook
Time format = %Y-%m-%d 

[XP]
Comment = VR11/VP11
Time format = %Y-%m-%d 

[Employees]
Comment = Employess
Time format = %Y-%m-%d 

[Purchases]
Comment = Purchases
Time format = %Y-%m-%d

66761

Mon Mar 15 08:23:45 2010

Re: Thread view problem in searches

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?

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:

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

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:

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

66758

Sat Mar 13 09:40:37 2010

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.

Goto page Previous 1, 2, 3 ... 381, 382, 383 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6