ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
2185
|
Tue Apr 3 15:19:00 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.4-1795 | Re: Multiple ideas for multiple logbooks |
Stefan Ritt wrote: | To distinguish betwen logbooks, one would need cookies in the form <logbook name>_unm and <logbook name>_upwd. |
Actually this is not a good idea. Most people I know have several logbooks, but a common password file. Access control is then fine-tuned via 'Login user = ...'. Now if I implement a per-logbook cookie, these people would have to log in once for each logbook. If the go to a new browser which does not contain their old cookies, or if the cookies expire, they would have to log in again once for each logbook. On installations with 20 and more logbooks this can be cumbersome. So all these people would complain. |
2190
|
Wed Apr 4 08:38:30 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.4-1795 | Re: Multiple ideas for multiple logbooks |
Yoshio Imai wrote: | 1. Multiple login
Is there any way to change the cookie structure so as to allow one (physical) user to be logged on as more than one elog user at a time? |
Actually there is a way, but I completely forgot about that. The manual says:
ELOG manual wrote: |
If any of the password statements are in the [global] area of the configuration files, they are used for all logbooks. If one logs in at one logbook, access is automaticlly granted to all logbooks. If the password statements are in the individual logbook sections, one has to log in to each logbook separately. |
That should help. Just put the password file = ... into the individual logbook sections, and you should get what you want. You can check this by inspecting the cookies (first you have to delete all cookies in your browser). With passoword files for individual logbooks you should see an associated Path for each logbook, so the login cookie only gets submitted to that logbook, allowing differnt user names/passwords for different logbooks. |
2191
|
Wed Apr 4 11:37:56 2007 |
| Yoshio Imai | | Request | Linux | 2.6.4-1795 | Re: Multiple ideas for multiple logbooks |
Stefan Ritt wrote: | Actually there is a way |
... and it works! Thank you!
Stefan Ritt wrote: | I fixed that now in the updated elcode.js. |
That works now, too!
Stefan Ritt wrote: | Your other problem of ignoring the control keys at all I could not reproduce. Try to reproduce it in a well-defined way and let me know. |
I will try to do that (new beamtime, new occasions ... ).
Stefan Ritt wrote: | Maybe you used a userlist attribute for the author? |
No, I didn't. I will try to investigate this further and let you know if I find anything.
So for the moment ... thanks for the help! |
2195
|
Tue Apr 10 04:03:59 2007 |
| marion | marion@spiderweb.com.au | Question | Windows | 2.6.4-1795 | HOW TO change http://localhost:8080/ to an address where users can access? |
hi folks
thankyou for your time
have read the user docs
and admin docs
and faqs
i used the latest windows installer to have the script runner as a server on windows
BTW i have been looking for over 3 years for this sort of thing - so i had given up for the i would say, i have looked at over 120 scripts and progs for possibilites - could this really be it?
i have managed to make another logfile using the config example
from stev ritt accelerator logbook
with a slight variation (changed file attached)as i could not make the original work for me as i do not know what i am doing.
i placed this in the demo config, underneath the code that was already there ie
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
I REPLACED BELOW CODE
; use user level password access
Password file = passwd
Login expiration = 1000
Admin user = ritt
Self register = 1
WITH THIS CODE
; use user level password access
Password file = XXXXXX
Login expiration = 1000
Admin user = XXXXXX
Self register = 1
==============================================
MY QUESTION:
HOW do i change the automated address http://localhost:8080/ to an address where users can access?
or do i tell them the address is http://localhost:8080/ - somehow i think that is not going to work for them even though it does for me.
my address is
http://organicparents.org |
Attachment 1: elogdPUBLIC.cfg
|
[Accelerator]
Comment = Accelerator Logbook
; use user level password access
Password file = XXXXX
Login expiration = 1000
Admin user = XXXXX
Self register = 1
; look and feel
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Login, Help
Date format = %B %d, %Y
; attributes
Attributes = Author, Author Email, Category, Subject
Options Category = Routine entry, Shift summary, Problem, Fix, Question, Info, Other
Extendable attributes = Category
Required Attributes = Category, Subject
Thread display = $Subject, entered by $author on $Entry date
Quick filter = Date, Category
; title as shown in the browser
Page Title = Accelerator Logbook - $subject
; preset author and email
Preset Author = $long_name
Preset Author Email = $user_email
; these attributes cannot be changed
Locked Attributes = Author, Author Email
; only author can change its own entry
Restrict edit = 1
; options for reply
Subst on reply subject = Re: $Configuration Name
Remove on reply = Author, Author Email
; No Email notification
Suppress Email to users = 1
|
2200
|
Tue Apr 10 10:17:27 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.4-1795 | Re: HOW TO change http://localhost:8080/ to an address where users can access? |
If you run elog on the machine which has the internet address organicparents.org, then you will be able to access elog under http://organicparents.org:8080, given that your firewall allows this access from outside. |
2202
|
Wed Apr 18 13:59:14 2007 |
| marion | marion@spiderweb.com.au | Question | Windows | 2.6.4-1795 | Re: HOW TO change http://localhost:8080/ to an address where users can access? |
Stefan Ritt wrote: |
If you run elog on the machine which has the internet address organicparents.org, then you will be able to access elog under http://organicparents.org:8080, given that your firewall allows this access from outside. |
hi again stefan
i am getting the idea that i am supposted to upload elog to my website ? is this correct?
ie e should make a directory for ELOG and load files - what files?
or all the files that came from the downloaded ELOG PROGRAM that i placed in my c-d rive ?
marion |
2203
|
Wed Apr 18 15:04:25 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.4-1795 | Re: HOW TO change http://localhost:8080/ to an address where users can access? |
marion wrote: | i am getting the idea that i am supposted to upload elog to my website ? is this correct?
ie e should make a directory for ELOG and load files - what files?
or all the files that came from the downloaded ELOG PROGRAM that i placed in my c-d rive ?
marion |
Where is your website? If it's hosted at a company, it's probably impossible to run elog there, since they only allow PHP scripts etc. |
2204
|
Wed Apr 18 22:45:57 2007 |
| marion | marion@spiderweb.com.au | Question | Windows | 2.6.4-1795 | Re: HOW TO change http://localhost:8080/ to an address where users can access? |
Stefan Ritt wrote: |
marion wrote: | i am getting the idea that i am supposted to upload elog to my website ? is this correct?
ie e should make a directory for ELOG and load files - what files?
or all the files that came from the downloaded ELOG PROGRAM that i placed in my c-d rive ?
marion |
Where is your website? If it's hosted at a company, it's probably impossible to run elog there, since they only allow PHP scripts etc. |
where - i am not sure what you mean by where . it is hosted by franceso - i have full access to everything - i have cpanel -
Operating system Linux
Service Status Click to View
Kernel version 2.6.11-1.1369_FC4
Machine Type i686
Apache version 1.3.37 (Unix)
PERL version 5.8.4
Path to PERL /usr/bin/perl
Path to sendmail /usr/sbin/sendmail
Installed Perl Modules Click to View
PHP version 4.4.6
MySQL version 4.1.21-standard
cPanel Build 10.9.0-RELEASE 7965
Theme cPanel X v2.6.0
Documentation Click to View |