| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
581
|
Mon Jul 12 09:31:03 2004 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | All | | Re: multiple "text entry" field |
> Is it possible to add one more "text entry" field ?
I guess you mean the main body text, which is multi-line. No, this is not
possible right, now, but I added your vote to the wishlist istem "Multi-line
attributes". |
|
589
|
Wed Jul 14 08:57:37 2004 |
| darshak | oradrs@yahoo.com | Question | All | | Re: multiple "text entry" field |
Your guess is correct. I would like to have that feature in ELOG.
Thanks
> > Is it possible to add one more "text entry" field ?
>
> I guess you mean the main body text, which is multi-line. No, this is not
> possible right, now, but I added your vote to the wishlist istem "Multi-line
> attributes". |
|
637
|
Fri Jul 30 02:03:59 2004 |
 | Guenter Nowak | Guenter.Nowqak@t-systems.at | | | | ?cmd=New&pType=PC does not work |
according to the users guide,
http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC
should create an entry with the type value set to PC, but this doesn't work |
|
638
|
Fri Jul 30 09:15:39 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | | | | Re: ?cmd=New&pType=PC does not work |
> according to the users guide,
>
> http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC
>
> should create an entry with the type value set to PC, but this doesn't work
Now it works. Updated elog version under CVS and as a snapshot (see Download Page) |
|
639
|
Fri Jul 30 12:26:10 2004 |
 | Guenter Nowak | Guenter.Nowqak@t-systems.at | | | | Re: ?cmd=New&pType=PC does not work |
> according to the users guide,
>
> http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC
>
> should create an entry with the type value set to PC, but this doesn't work
Thanks! |
|
659
|
Wed Aug 11 15:38:07 2004 |
 | Jen Manz | jennifer.manz@lmco.com | Question | Windows | | Restricting viewing messages |
I am working on a logbook for a lab. I have two questions...
First - Some of the logbook entries should not be viewed by certain users.
What would be the easiest way to restrict viewing some entries?
Second - I have a welcome page for the ELOG that lists some info about the
ELOG. When I start the ELOG, the user sees the login page. After the user
logs in, the welcome page appears listing the restrictions. Right now, I
have a hyperlink that takes the user to new, find, etc. But I would like
to take the user right to the logbook and not have to come back to the
welcome page everytime. How can I do this?
I have attached the code I have so far. They are in .txt format for easier
viewing.
Thanks! |
| Attachment 1: Welcome_Login.txt
|
<h1>Welcome to the PEBL Logbook</h1>
<u1>
<li><a href="?cmd=new">Enter</a> new entry in the logbook
<P ALIGN=CENTER>Information included herein is controlled.</P>
</ul>
|
| Attachment 2: elogd.txt
|
[global]
logbook tabs = 0
port = 8080
Admin user = jmanz
Logfile = c:\Program Files\ELOG\logbooks\PEBL_Log
Logging level = 2
[PEBL]
Welcome page = Welcome_Login.html
Theme = default
Comment = PEBL Logbook
Attributes = Author, Material Group, Type, Category, Subject
Find Menu commands = New, Reply, Find, Logout, Help
Options Material Group = Computers, Consoles, Other
ROptions Category = Hardware, Software, Both, Neither
Preset Category = Hardware
Required Attributes = Author, Material Group, Type, Category
Preset Text = Restricted Info
Page Title = ELOG - $subject
Attachment comment=Use "Browse" to select the attachment and "Upload" to save the attachment. Repeat for multiple attachments.
Message comment = Restricted Info
Reverse sort = 1
Quick filter = Date
Entries per page = 100
password file = c:\Program Files\ELOG\elog.pwd
Self Register = 1
Login expiration = 0
Protect Selection page = 1
Suppress Email to users = 1
Suppress default = 2
Restrict Edit = 1
Locked Attributes = Author
Preset Author = $short_name
Subst on reply Subject = Re: $subject
|
|
660
|
Wed Aug 11 16:02:52 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | | Re: Restricting viewing messages |
> First - Some of the logbook entries should not be viewed by certain users.
> What would be the easiest way to restrict viewing some entries?
The easiest way is to define two logbooks, with two different password files.
The more restricted logbook contains only those users who are allowed to see the
restricted entries. Use the commands "Move to" to move entries between the two
logbooks (see documentation).
> Second - I have a welcome page for the ELOG that lists some info about the
> ELOG. When I start the ELOG, the user sees the login page. After the user
> logs in, the welcome page appears listing the restrictions. Right now, I
> have a hyperlink that takes the user to new, find, etc. But I would like
> to take the user right to the logbook and not have to come back to the
> welcome page everytime. How can I do this?
Right now you need an exteral page on a public webserver. This page contains
then links to your elog server. I the next version I will implement the
possibility to server *.html files directly through elog. You can then put your
welcome page under themes/default/Welcome.html, and access it through the
starting link:
http://your.elog.server/logbook/Welcome.html
You will only see the Welcome page once, since all links in elog will point back
to .../logbook/ and not to .../logbook/Welcome.html. The config option "Welcome
page = Welcome.html" you have to remove then of course. |
|
673
|
Wed Aug 18 11:12:56 2004 |
| nait tauh | nait@no2bl.no-ip.com | | Linux | | Admin rights lost after upgrade 2.5.2 to 2.5.4 |
The upgrade was done by just replacing elogd from 2.5.2 to 2.5.4 from the rpm.
Somehow elogd 2.5.4 treat all users as normal user. When clicking on
"config". All admin users has no "change elogd.cfg" button. Revert back to
2.5.2 OK.
Is there anything I need to change to upgrade other than replaceing elogd?
Clearing the cookies didn't help.
Thanks,
.nait. |