ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67293
|
Wed Jun 27 14:56:43 2012 |
| Graham Medlin | glmedlin@ncsu.edu | Bug report | Linux | 2.9.2-2455 | Attachment URL login redirect error |
If I have a couple of attachments in a log book entry, I can link to that entry "http://example.edu/elog/Sandbox/7 ", I get the appropriate log in page, and after logging it, it takes me to the entry.
However, if I link directly an attachment, "http://example.edu/elog/Sandbox/7/1 ", I receive a plain log in page that doesn't have the stylesheet applied, and logging in, I am directed to " http://example.edu/elog/Sandbox/7/" which throws an invalid error. If I am already logged in the browser, it links correctly.
I assume the problem must stem from messed up relative URL somewhere, hence the lack of stylesheet, or from the redirect incorrectly handling the /. (Looking at the source for the two login pages, the only difference is "<input type=hidden name=redir value="7"> " versus "<input type=hidden name=redir value="7/1"> ". ) But that reaches the end of my ability...
This breaks the attachment links in emails.
Any help would be much appreciated! |
67294
|
Sun Jul 1 19:55:38 2012 |
| Per Eriksson | pelle@sm4xiu.eu | Info | Linux | Any | Re: Compiling Elog for QNAP NAS x86 |
Per Eriksson wrote: |
Per Eriksson wrote: |
Hi All,
I am interested to have ELOG installed in my QNAP x86 based NAS (239 Pro II)
Have someone done this already or is there a write-up of a normal compile-procedure which I can have as a base when I attempt to compile?
Regards,
Per
|
I solved it.
I don't really know if I really needed to compile it but I complied this on the NAS itself so now it is 100% compatible (I believe)
Per
|
I managed to package Elog v2.92 build 2462 into and QNAP installer QPKG package.
This is for x86 based QNAP NAS only.
Note: You must have adduser package installed prior to installation.
Login to the NAS with SSH and type:
apt-get update
apt-get install adduser
BR,
Per |
Attachment 1: Elog_2.9.2_2462.qpkg
|
67295
|
Tue Jul 3 09:46:19 2012 |
| Ze Li | zejili@gmail.com | Question | Linux | 2.8.1-2350 | move a type of entries to another logbook |
Hi,
I have logbook A and logbook B. Is it possible to move one type of entries in logbook A to logbook B? If yes, may I know how you do it? Thank you.
Ze |
67298
|
Wed Jul 4 14:18:21 2012 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.8.1-2350 | Re: move a type of entries to another logbook |
Ze Li wrote: |
[...] I have logbook A and logbook B. Is it possible to move one type of entries in logbook A to logbook B? If yes, may I know how you do it? Thank you.[...]
|
-
You can add the "Move to = B" command in logbook A.
-
Then you add "select" in "List Menu commands = ..., select, ...".
-
Now you "Find" all entries of the type you want (for convenience choose "Display 9999 entries per page").
-
You press "toggle all" and then "Move to B"
|
67304
|
Sun Jul 29 00:59:51 2012 |
| Phil Rubin | prubin@gmu.edu | Question | Linux | latest | ssh tunneling with elog running under Apache |
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? |
67305
|
Sun Jul 29 15:43:20 2012 |
| Phil Rubin | prubin@gmu.edu | Question | Linux | latest | Re: 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? |
67306
|
Wed Aug 8 21:23:59 2012 |
| cowden | christopher.cowden@ttu.edu | Question | Linux | 2.9.0-2411 | Authentication 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
|
67307
|
Fri Aug 10 11:47:49 2012 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.9.0-2411 | Re: 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? |