Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 218 of 806  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  66024   Thu Oct 30 04:17:09 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.7.5-2130Re: (How) can I hide columns in List view?

 

T. Ribbrock wrote:

Originally, all information about our machines was stored in a spreadsheet with one sheet for the hardware of the machines and one for the software. By now, I've sucessfully moved the software part to an elog logbook and am now looking at transferring the hardware part as well.

As both lists are machine-name based, one of the options would be to merge both lists, as this would place all machine-related info into one logbook. The downside of this is that I get so many columns in list view that the result is quite unwieldy. Hence, I would like to hide some columns - ideally creating a "hardware view" and a "software view".

From the documentation, the only option I could find that seemed suitable was "List conditions". Unfortunately, I do not quite understand from the manual how this is supposed to work, so I'm quite possibly doing something wrong. I've tried this:

; General settings
List conditions = 1

; Attributes
Attributes = Type, Created, StatusA, StatusB, Archived

; Options & Tooltips
Options Type = Type1{10}, Type2{11}

; Conditionals
{10}List display = Edit, Type, Created, Status
{11}List display = Edit, Type, Created, StatusA, StatusB, Archived

but no matter how I set "Type", it does not seem to have any effect on the List display. One thing I don't understand for example is how does elog decide in List view which entry sets the condition? If all entries are set to the same value (in this example e.g. "Type1")? The first entry? Or am I missing something altogether?

Also, if there are alternative ways how I could accomplish my goal, I'd also be most grateful for suggestions.

Thanks in advance,

Thomas

 

 Indeed you got something wrong. The conditional attributes are meant for the input form, so you can turn some attributes on and off or choose different options for an attribute depending on the value of another attribute.

The only way I see how you can achieve what you want is to define two separate logbooks, but serve them from the same directory (via the "Data dir" option). Both logbooks should share the same attribute definition, but use different "List display" options.

  66025   Thu Oct 30 04:28:05 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5-2130Re: Standard login Screen - bottom text

 

Barend wrote:

Hi Stefan.

I have been "playing" around with this great tool and found an interesting "issue" ...

I use multiple logbooks and have both "Protect Selection page = 1" and "Expand Selection Page = 1".

When I open my elog, I get a Standard Login Screen with the Standard Bottom Text "ELOG V2.7.5-2130" which will link to your this website.

When I "Logout" and "Login" again from the Logbook page, I get another Login Screen with my own "Bottom text login" which will link to my own elog page.

How can I apply my own Bottom Text to the Standard Login Screen ?

Thanks & Regards, Barend
 

 

 By using the configuration option "Bottom Text Login = ..."

  66026   Thu Oct 30 04:33:43 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.4-2111Re: Error Message During Uploads

 

Kevin O'Sullivan wrote:

We've been having toruble with uploads not working and I notice that every time someone uploads to our elog the same error message appears in /var/log/syslog:

Cannot restore original GID/UID.

How can I fix thsi error? Or, perhaps more importantly, could it cause elog to "lock up" (note, it doesn't crash)?

I'm runing elog on Ubuntu kernel version 2.6.24-server.

 

 Probably something is wrong with the account under which you run elog. Normally (at least if you install elog from the RPM) you have an account "elog" and group "elog" under which you run elogd. You compile and install elogd under root (so that it can bind to port 80 for example), and then you put 

usr = elog
grp = elog

into the configuration file. So when you start elogd, it binds to the server port, then falls down to user "elog" and gives up root privileges. If the elog account for example does not exist, you get the above error message. The only problem I see there is if elog stays as root, it can do more harmful things in case it misbehaves.

  66031   Mon Nov 3 07:33:08 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5-2130Re: Standard login Screen - bottom text

Barend wrote:

Stefan,

I have defined the "Bottom Text Login = ..." in each Logbook Configuration section. But when I use this option in the Global Section, ELOG fails to start.

Barend

 

 That's strange. I just tried myself following configuration file:

[global]
port = 8080
Bottom text = <center>Hello</center>
Bottom text login = <center>Login Hello</center>
Password file = passwd

[demo1]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Page Title = ELOG - $subject

[demo2]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject

and everything works fine as can be seen from the login screen:

Capture.jpg

so can you check if above file works for you?

  66032   Mon Nov 3 13:15:52 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5Re: Server derived time
Grant Jeffcote wrote:

I'm also having issues with conditional entries in the Find page. If a conditional statement is used to hide attributes or change displayed attributes in the entry page then the attribute that is used in the conditional statement is not permanently selectable in the 'Find' page. It is available as a choice but as soon as selected the conditional action removes it? Is it possible to make conditional options/actions in the 'Find' page optional?

Hope that makes a little sense?

Many thanks

 

Many people want conditional attributes on the find page, so I cannot remove it. Before adding another parameter to disable this optionally, I would like to ask you to first try the "Show attributes edit = ..." option, which is not evaluated in the "find" page. Maybe you can achieve what you want with this option.

  66036   Thu Nov 6 08:11:57 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux Re: Proxy Error

 

Glen MacLachlan wrote:

A problem recently developed for our elog...after running without much problem the elog daemon was restarted on an ubuntu server running apache2. Now the server gives 502 Proxy Error messages:

 

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /elog.

Reason: Error reading from remote server

I did a force-reload of apache after making sure the modules are enabled. I also restarted elogd but to no avail. One symptom seems to be that the GET request is empty...that is before it was:

"GET /elog/sample_elog/etcetera HTTP/1.1"

but now it is just

"GET /elog HTTP/1.1"

 

Just started out of the blue...

 

Any ideas?

 

 I have a similar problem when I restart the elogd daemon. To fix that, I usually also restart Apache.

  66047   Mon Nov 17 10:08:01 2008 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.7.5Re: Sorting Museremail

 

Steve Williamson wrote:

Hi

I've just upgraded to 2.7.5 mainly because I wanted to have Museremail sorted.  We use this to list contacts on an RFC form and it's much easier to find the ones you want when they are in a predictable sequence.  As an extension to this it would be great if they could be sorted by the last part of their real name - typical user, give him a sweetie and he wants jam on it!

cheers

Steve

 

 That's a bit hard since different groups enter their names differently. While for a human it's easy to figure out what the family name is (usually), this must not be true for a computer. So I would propose that you enter the real names in the sequence family name, given name like

Ritt, Stefan
Doe, John

then sorting will work as you like.

  66048   Mon Nov 17 10:18:52 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.5Re: Special characters in attribute names

 

Steve Williamson wrote:

Hi

Thanks for elog - it's a brilliant piece of software.  I'd looked all over for open source software to log/manage change requests before discovering elog; it's so flexible that I've been able to do everything I need with it.

However, I think that I've just discovered my first undocumented 'feature'.  Attribute names containing punctuation characters (e.g. / and :) cause "Redirection limit for this URL exceeded" errors in Firefox 3.0.2 and corrupt the URL if they're used in a Quick Filter.  I often use '/' in attribute names for brevity, e.g. "Old/New Versions" but hadn't used one in a Quick Filter before.

 

Quick answer: Don't use '/' in attribute names ;-) but I guess you were kind of afraid to get this answer.

Somehow longer answer: I tried to reproduce your problem with following configuration:

[demo]
Attributes = Author, Type, Subject, Old/New
Options Old/New = Old, New
Quick filter = Type, Old/New

But I was not successful. Everything worked fine using ELOG V2.7.5-2137. Can you please check with the above configuration and tell me exactly when the redirection problem occurs? Is it during filtering on already on creating a new entry?

 

ELOG V3.1.5-3fb85fa6