ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
207
|
Fri Feb 7 19:52:41 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Lost features since upgrade to 2.3.0 |
> Problem 1 - Since upgrading to version 2.3.0 I seem to have lost the some
> functionality explained below. When i first log into my logbook (i only
> have a single one) it defaults to the summary view and the first field is
> one called Customer Name as opposed to # as i wanted the list sorted by
> this field, the link for that logbook entry is no longer available on the
> first field (being Customer Name) but only on the # field), however if you
> use Summary threaded view the whole line is a link.
I revised the way links are placed into the summary table, so I could have
lost some functionality (I did not try all config combinations since there
are too many now). So I can fix your problem in two ways now: Either always
have the first item in a list be a link, or have each item be the (same)
link. What do you think is a better solution?
> Problem 2 - no matter what i try in the config file i cannot get elogd to
> use stylesheets ive tried specifying and even editing and removing the
> default.css style sheet i downloaded but it just seems to ignore its there.
First question: Does your elog pages have color? If so, the default.css is
loaded correctly. Otherwise your page would contain text but all would be
white.
So I presume you see color, that means your default.css is loaded correctly.
It can now be that your browser caches that stylesheet. I use MS Internet
Explorer and Mozilla and a "reload" on the browsers refreshes the
stylesheet, but you really have to press the "reload" button (or clear the
browser cache). Have you tried that?
- Stefan |
206
|
Fri Feb 7 18:38:56 2003 |
| Nick | nikc@cnic.com | Question | | | Lost features since upgrade to 2.3.0 |
Ive got 2 issues which I cant see to resolve I was wondering if anyone can
help.
Problem 1 - Since upgrading to version 2.3.0 I seem to have lost the some
functionality explained below. When i first log into my logbook (i only
have a single one) it defaults to the summary view and the first field is
one called Customer Name as opposed to # as i wanted the list sorted by
this field, the link for that logbook entry is no longer available on the
first field (being Customer Name) but only on the # field), however if you
use Summary threaded view the whole line is a link.
Is there a flag or setting to the make the first field a link?
Problem 2 - no matter what i try in the config file i cannot get elogd to
use stylesheets ive tried specifying and even editing and removing the
default.css style sheet i downloaded but it just seems to ignore its there.
Any help or advice ?????? |
205
|
Thu Feb 6 15:46:11 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Author attribute as a Quick Filter? |
> When ELOG is configured for Self-Register=3, is it still possible
> to use the Author attribute as a Quick Filter?
>
> When I try it, the Author drop down box doesn't display anything.
>
> Thanks,
> Eric
The "Quick Filter" facility only works for attributes which are avaiable as
an "Options <attribute> = ..." list. So if you have a "free" attribute like
the author, the systen would have to scan the whole logbook to find all
possible authors, which would result in some unacceptable performance
degradation. Nevertheless, in systems with a limited number of authors one
can add the "options author = ..." statement to get the selection box. The
behaviour is independent of the "Self-Register" setting. |
204
|
Thu Feb 6 15:16:30 2003 |
| eric wooten | wootene@verizon.net | Question | | | Author attribute as a Quick Filter? |
When ELOG is configured for Self-Register=3, is it still possible
to use the Author attribute as a Quick Filter?
When I try it, the Author drop down box doesn't display anything.
Thanks,
Eric |
203
|
Fri Jan 31 21:09:47 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: Write only |
> Does this truly disable the edit command or just hide it?
You're right! In some earlier versions, it did disable it, but in 2.2.5 it
just hides it. I fixed that bug and from 2.3.0 on it will really disable
that command again, such that if someone enters manually
http://midas.psi.ch/elogdemo/Forum/202?cmd=Edit
will produce and error if the command is not in the menu list. |
202
|
Fri Jan 31 20:47:51 2003 |
| Matthew | greggmc@yahoo.com | Info | | | Re: Write only |
Does this truly disable the edit command or just hide it?
> > I'm interested using elog for a lab notebook. Once entries have been
> > entered they cannot be changed/edited.
> > Is it possible for elog to be setup to support something like this? A write
> > only mode?
>
> What you need is an entry in the elogd.cfg file:
>
> Manu commands = Back, New, Reply, Find, Config, Logout, Help
>
> As you see, the "Edit" and "Delete" commands are missing here and therefore
> do not get displayed. So you can enter a message with "New", but you cannot
> change it afterwards. |
201
|
Fri Jan 31 09:49:43 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: Write only |
> I'm interested using elog for a lab notebook. Once entries have been
> entered they cannot be changed/edited.
> Is it possible for elog to be setup to support something like this? A write
> only mode?
What you need is an entry in the elogd.cfg file:
Manu commands = Back, New, Reply, Find, Config, Logout, Help
As you see, the "Edit" and "Delete" commands are missing here and therefore
do not get displayed. So you can enter a message with "New", but you cannot
change it afterwards. |
200
|
Thu Jan 30 19:52:46 2003 |
| Matthew | greggmc@yahoo.com | Question | | | Write only |
I'm interested using elog for a lab notebook. Once entries have been
entered they cannot be changed/edited.
Is it possible for elog to be setup to support something like this? A write
only mode? |