| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
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. |
|
675
|
Thu Aug 19 16:20:16 2004 |
| | | | | | |
Here are some things for your wish list:
1) elogd should report quota or disk-full problem: In case a logbook
entry cannot be saved (quota or disk full) then a message like
'Could not save last entry. Please contact administrator.' should
be displayed. Currently nothing happens. Only the submitted
entries 'vanish'.
2) default page view per user, i.e. the 'Back' link goes to
?mode=Full,summary,... depending on the user that is logged in.
Some users complained that 'Back' is not really back. Maybe
consider renaming 'Back' to 'Default View' or something.
3) (related to 1) the 'Back' link should go back to the last used mode
(full, summary, threaded,...) and not to the default mode
4) mark messages as unread/read on a per user basis: The
implementation of this might be quite involved but it would be
rather useful. One way would be to add a default attribute 'Seen
by' to each entry, which lists the login names of the users. Or
files LOGIN_NAME.has_seen can be created which contain the entry
IDs of the viewed entries for each user.
5) alignment of attribute table (using <td colspan=2> for multi line
stuff): see elog:669 :)
You can count my vote for:
- Use "and" and "or" operands in queries
|
|
689
|
Wed Sep 8 12:25:20 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | | Linux | | Re: Admin rights lost after upgrade 2.5.2 to 2.5.4 |
> 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.
The button name has been changed from "change elogd.cfg" to "change config file"
since the file name is now variable (can be changed during compile time). But I
guess this is not your problem.
Can you try with the demo logbook (contained in the distribution). Just add
"password file = ..." and "admin user = ..." to the sample elogd.cfg. If I do that
here, everything works fine. You also can send me your elogd.cfg so I can have a look. |
|
701
|
Wed Sep 15 00:16:19 2004 |
| | | | | | |
I g |
|
710
|
Tue Sep 28 22:44:50 2004 |
| roets | jim.roets@valero.com | Question | Linux | | Attachment file "" empty or not found |
I am getting the following error message with version 2.5.4-4 when I try to
add a new entry to a log book.
Attachment file "" empty or not found
If I add the following line to me elogd.cfg I do not get the error, but will
not be able to use attachments.
Enable attachments = 0
I recently upgraded from version 2.2.5 which did not have the problem. I
did not see anything in the changelog referencing this type of change to how
attachments are handled.
I there something I need to set in the config so that an attachment is not
expected every time a new entry is made? |