> 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.

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

> 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.

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 ??????

> 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

> 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?

I think the first option is the better one, having the first columns data in 
the list be linkable for example i am using this to store customer 
configuration and the list needs to be in alphabetical order so it has to be 
the first column but needs to be linkable :)

Would be nice if you can specify which columns data has links as a flag or 
setting of some sorts, as opposed to either the first or all, but given a 
choice I would want the first column to be the linkable one 

My config looks like this

Display search = Customer Name, Account ID, Author, Date, #

I think the better option is first item (being the first column entries) all 
have links to the logbook entries (which is how it was in the previous 
version) 

> 
> > 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.

I resolved this problem, many thanks for your help

Hi Stefan,

Many users have there email forward to Blackberry devices.  Although I 
wasn't aware, it appears the Blackberry has a limit (or maybe one was set) 
of how big the message can be (still checking for that though).

Previously, a modification was made that addressed the issue of slow ELOG 
response when saving the elog entry.   I think the change was for ELOG to 
generate one email and send to all the users designated to receive the 
notification.  This caused everyone to show up as "TO" addresses.

This change makes the Email header increase in size (length).  I guess the 
Blackberry counts the Header portion as part of the email size limit.

Any ideas?

Thanks, 
Eric

Another Question:  Could ELOG be configured to send notifications as a Blind 
Copy?  Just wondering if that would take care of the problem?

> Hi Stefan,
> 
> Many users have there email forward to Blackberry devices.  Although I 
> wasn't aware, it appears the Blackberry has a limit (or maybe one was set) 
> of how big the message can be (still checking for that though).
> 
> Previously, a modification was made that addressed the issue of slow ELOG 
> response when saving the elog entry.   I think the change was for ELOG to 
> generate one email and send to all the users designated to receive the 
> notification.  This caused everyone to show up as "TO" addresses.
> 
> This change makes the Email header increase in size (length).  I guess the 
> Blackberry counts the Header portion as part of the email size limit.
> 
> Any ideas?
> 
> Thanks, 
> Eric