Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 311 of 806  Not logged in ELOG logo
IDdown Date Icon Author Author Email Category OS ELOG Version Subject
  67312   Thu Aug 16 16:12:49 2012 Reply harley skorpenskeh9s@ornl.govQuestionLinux V2.9.1Re: Drop down search list?

Stefan Ritt wrote:

I know that this is for searching. But you don't get the point. You have attributes, like Date, Category, Subject. Each attribute can either contain arbitrary text (like the subject), or one of a set of predefined values. So category can be, let's day, "one", "two", "three". You define the possible options of the category with

Options Category = one, two, three

If you then define the quick filter

Quick filter = Category

then you get for the category a drop-down box where you can select "one", "two" or "three". If you do so, elog shows all logbook entries where the category attribute has the selected value.

I hope that this is clearer now. 

Thanks Stefan, I think I understand, and now I see the options definition on the syntax page.  I apologize for taking up your time and thank you for the great software.  I think this is right now:

Options Search = Date, Subject, Subtext

Quick filter = Search

  67311   Thu Aug 16 15:59:53 2012 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux V2.9.1Re: Drop down search list?

harley skorpenske wrote:

I forgot to mention - this is for searching the logbook.   So would the config file look more like this:

 

 

[global]

port = 8080

 

usr = vulcanstaff

Max content length = 1073741824

Menu commands = New, Edit, Delete, Reply, Find, Last day, Move to, Copy to, Import, Help

RSS Title = $subject, posted by $author on $entry time

RSS Entries = 10

Options Category = Date, Subject, Subtext

Quick filter = Date, Subject, Subtext

Use Lock = 1

Reverse sort = 1

Required Attributes = Author, Subject

 

 

I know that this is for searching. But you don't get the point. You have attributes, like Date, Category, Subject. Each attribute can either contain arbitrary text (like the subject), or one of a set of predefined values. So category can be, let's day, "one", "two", "three". You define the possible options of the category with

Options Category = one, two, three

If you then define the quick filter

Quick filter = Category

then you get for the category a drop-down box where you can select "one", "two" or "three". If you do so, elog shows all logbook entries where the category attribute has the selected value.

I hope that this is clearer now. 

  67310   Thu Aug 16 15:55:32 2012 Reply harley skorpenskeh9s@ornl.govQuestionLinux V2.9.1Re: Drop down search list?

Stefan Ritt wrote:

harley skorpenske wrote:

 I'm having some confusion with configuring my logbook.  In the global section of the logbook I have the quick filter enabled, but it is not a drop down list, only an editable text field:

 

Screen_Shot_2012-08-16_at_9.21.35_AM.png

 

I think it is an attributes issue, but I'm having some trouble making sense of those from the syntax page.  Here is my config file:

 

 

[global]

port = 8080

 

usr = vulcanstaff

Max content length = 1073741824

Menu commands = New, Edit, Delete, Reply, Find, Last day, Move to, Copy to, Import, Help

RSS Title = $subject, posted by $author on $entry time

RSS Entries = 10

Quick filter = Date, Subject, Subtext

Use Lock = 1

Reverse sort = 1

Required Attributes = Author, Subject

 

[Experiment_Logbook]

Theme = default

Comment = Experiment Logbook

Attributes = Author, Author Email, Type, Category, Subject

Options Type =  Other

Options Category = Start Up

Extendable Options =Category

Page Title = $Subject

 

 

You get a drop-down list if you define several options for an attribut, like

Options Category = Start Up, Start Down, Other

The you can select one of the categories from the drop-down list.

 

I forgot to mention - this is for searching the logbook.   So would the config file look more like this:

 

[global]

port = 8080

 

usr = vulcanstaff

Max content length = 1073741824

Menu commands = New, Edit, Delete, Reply, Find, Last day, Move to, Copy to, Import, Help

RSS Title = $subject, posted by $author on $entry time

RSS Entries = 10

Options Category = Date, Subject, Subtext

Quick filter = Date, Subject, Subtext

Use Lock = 1

Reverse sort = 1

Required Attributes = Author, Subject

 

  67309   Thu Aug 16 15:39:43 2012 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux V2.9.1Re: Drop down search list?

harley skorpenske wrote:

 I'm having some confusion with configuring my logbook.  In the global section of the logbook I have the quick filter enabled, but it is not a drop down list, only an editable text field:

 

Screen_Shot_2012-08-16_at_9.21.35_AM.png

 

I think it is an attributes issue, but I'm having some trouble making sense of those from the syntax page.  Here is my config file:

 

 

[global]

port = 8080

 

usr = vulcanstaff

Max content length = 1073741824

Menu commands = New, Edit, Delete, Reply, Find, Last day, Move to, Copy to, Import, Help

RSS Title = $subject, posted by $author on $entry time

RSS Entries = 10

Quick filter = Date, Subject, Subtext

Use Lock = 1

Reverse sort = 1

Required Attributes = Author, Subject

 

[Experiment_Logbook]

Theme = default

Comment = Experiment Logbook

Attributes = Author, Author Email, Type, Category, Subject

Options Type =  Other

Options Category = Start Up

Extendable Options =Category

Page Title = $Subject

 

 

You get a drop-down list if you define several options for an attribut, like

Options Category = Start Up, Start Down, Other

The you can select one of the categories from the drop-down list.

 

  67308   Thu Aug 16 15:27:34 2012 Question harley skorpenskeh9s@ornl.govQuestionLinux V2.9.1Drop down search list?

 I'm having some confusion with configuring my logbook.  In the global section of the logbook I have the quick filter enabled, but it is not a drop down list, only an editable text field:

 

Screen_Shot_2012-08-16_at_9.21.35_AM.png

 

I think it is an attributes issue, but I'm having some trouble making sense of those from the syntax page.  Here is my config file:

 

[global]

port = 8080

 

usr = vulcanstaff

Max content length = 1073741824

Menu commands = New, Edit, Delete, Reply, Find, Last day, Move to, Copy to, Import, Help

RSS Title = $subject, posted by $author on $entry time

RSS Entries = 10

Quick filter = Date, Subject, Subtext

Use Lock = 1

Reverse sort = 1

Required Attributes = Author, Subject

 

[Experiment_Logbook]

Theme = default

Comment = Experiment Logbook

Attributes = Author, Author Email, Type, Category, Subject

Options Type =  Other

Options Category = Start Up

Extendable Options =Category

Page Title = $Subject

 

  67307   Fri Aug 10 11:47:49 2012 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.0-2411Re: Authentication problem with wget and links (text browser)

cowden wrote:

Hello,

I'm not able to authenticate to a logbook using my text based browser links, so I've started investigating with wget hoping solving the problem one will lead to a solution for the other.  I've seen some examples on how to use wget to parse logbook entries in this forum, but my attempts keep returning the login page.  Any advice would be helpful and appreciated.  Here are a couple of the command line arguments I've tried:

wget --save-cookies cookie.txt --keep-session-cookies -d "http://hostname/LOGBOOK?unamee=YYY&upassword=XXX" -O elog.txt

wget --save-cookies cookie.txt --keep-session-cookies -d --post-data="redit=&uname=YYY&upassword=XXX&remember=1" -e robots=off "http://hostname/LOGBOOK" -O elog.txt

After these executions, my cookies.txt file remains empty.  Running subsequent command with "--load-cookies=cookies.txt" still points me to the login page.

Many Thanks,

Chris

I've just checked that 'wget --no-check-certificate --save-cookies cookie.txt --keep-session-cookies -d "https://elog-gfa.psi.ch/SLS?uname=uuu&upassword=ppp" -O elog.txt'

created a file cookie.txt. The file contains three lines of data if uname and upassword are a valid login, and it is empty (beside of three comment lines) if they are not a valid login (wrong user or wrong password).

Could it be related to the set-up of your particular logbook?

  67306   Wed Aug 8 21:23:59 2012 Question cowdenchristopher.cowden@ttu.eduQuestionLinux2.9.0-2411Authentication problem with wget and links (text browser)

Hello,

I'm not able to authenticate to a logbook using my text based browser links, so I've started investigating with wget hoping solving the problem one will lead to a solution for the other.  I've seen some examples on how to use wget to parse logbook entries in this forum, but my attempts keep returning the login page.  Any advice would be helpful and appreciated.  Here are a couple of the command line arguments I've tried:

wget --save-cookies cookie.txt --keep-session-cookies -d "http://hostname/LOGBOOK?unamee=YYY&upassword=XXX" -O elog.txt

wget --save-cookies cookie.txt --keep-session-cookies -d --post-data="redit=&uname=YYY&upassword=XXX&remember=1" -e robots=off "http://hostname/LOGBOOK" -O elog.txt

After these executions, my cookies.txt file remains empty.  Running subsequent command with "--load-cookies=cookies.txt" still points me to the login page.

Many Thanks,

Chris 

 

  67305   Sun Jul 29 15:43:20 2012 Reply Phil Rubinprubin@gmu.eduQuestionLinuxlatestRe: ssh tunneling with elog running under Apache

Phil Rubin wrote:

In a configuration with elog running (8080) under Apache (80) [as explained in admin guide], what is the syntax for tunnelling in with ssh, of both the ssh command and the browser locator?

Maybe some more information will help with the question.  Here's the results of my playing around with URL = /host.domain/subdir in elog.cfg.  Commented out, I can access locally with http://localhost:8080 and tunnelled (1234:host.domain:8080) with http://localhost:1234, with and without Apache (i.e., Apache is bypassed?).  URL = /host.domain/elog in elog.cfg works locally with browser locator localhost:8080 (of course), localhost/elog, and host.domain/elog, but the tunnel directly to 8080 no longer works, nor does http://localhost:4321/elog (even though this ends up showing the same URL on the remote browser as on the local browser) (4321:host.domain:80).  http://localhost:4321 brings up the Apache window.  Every other URL assignment I tried failed both locally and remotely, so, I assume the ssh tunnel directive is wrong, or the browser locator, or maybe still URL = .  Anyway, my question is, what am I doing wrong?

ELOG V3.1.5-3fb85fa6