Lost features since upgrade to 2.3.0, posted by Nick on Fri Feb 7 18:38:56 2003
|
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 ?????? |
Re: Lost features since upgrade to 2.3.0, posted by Stefan Ritt on Fri Feb 7 19:52:41 2003
|
> 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 |
Re: Lost features since upgrade to 2.3.0, posted by Nick on Fri Feb 7 22:26:13 2003
|
> 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 |
Re: Lost features since upgrade to 2.3.0, posted by Stefan Ritt on Tue Feb 11 09:03:18 2003
|
> 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
Well, I decided to make all entries in a table a link, to be consistent with
the threaded display. But I changed the style such that they look like
before, but are actually links. This way it cannot hurt (like having too
much underlined text). The style can be changed via classes ".list1"
and ".list2" in the style sheet.
The modification will come in 2.3.1, or you can get the source code from CVS
under
http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c
and
http://midas.psi.ch/cgi-bin/cvsweb/elog/themes/default/default.css
> > > 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
What happened. If you tell your initial problems, I can maybe put something
into the docs so that others won't have it...
- Stefan |
Re: Lost features since upgrade to 2.3.0, posted by Nick on Tue Feb 11 11:17:29 2003
|
> > > > 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
>
> What happened. If you tell your initial problems, I can maybe put something
> into the docs so that others won't have it...
>
> - Stefan
I upgraded to version 2.3.0 the previous version didnt seem to work with
stylesheets, when you viewed the html source there was no stylesheet defined
in it.
Please see my other posts for feature requests.
Many Thanks - FANTASTIC program btw |
Re: Lost features since upgrade to 2.3.0, posted by Kutlay Topatan on Wed Feb 12 19:10:26 2003
|
Stefan,
When will you have 2.3.1 out? I just upgraded to 2.3.0 and would like to see
the links in my summary view. If it is going to be out soon I will wait
instead of compiling from source.
Thanks for great software,
k.
> > 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
>
> Well, I decided to make all entries in a table a link, to be consistent with
> the threaded display. But I changed the style such that they look like
> before, but are actually links. This way it cannot hurt (like having too
> much underlined text). The style can be changed via classes ".list1"
> and ".list2" in the style sheet.
>
> The modification will come in 2.3.1, or you can get the source code from CVS
> under
>
> http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c
>
> and
>
> http://midas.psi.ch/cgi-bin/cvsweb/elog/themes/default/default.css
>
> > > > 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
>
> What happened. If you tell your initial problems, I can maybe put something
> into the docs so that others won't have it...
>
> - Stefan |
Re: Lost features since upgrade to 2.3.0, posted by Stefan Ritt on Wed Feb 12 19:54:21 2003
|
> When will you have 2.3.1 out? I just upgraded to 2.3.0 and would like to
see
> the links in my summary view. If it is going to be out soon I will wait
> instead of compiling from source.
2.3.1 will come out next week, since this week I'm at home. But you always
can get the sources from CVS (see below).
> > The modification will come in 2.3.1, or you can get the source code from
CVS
> > under
> >
> > http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c
> >
> > and
> >
> > http://midas.psi.ch/cgi-bin/cvsweb/elog/themes/default/default.css |
Find , posted by eric wooten on Mon Feb 10 23:36:31 2003
|
When you do a find in elog, records per page (some crazy large number - for
your forum logbook, display 57 entries seem to cause the problem, then
select last year (1 years worth of logs),(don't select printable)
the results appear way off the screen (the message body looks fine, but the
title, etc extend way off the screen).
Printable doesn't have this problem. |
Re: Find , posted by Stefan Ritt on Wed Feb 12 08:56:29 2003
|
> When you do a find in elog, records per page (some crazy large number - for
> your forum logbook, display 57 entries seem to cause the problem, then
> select last year (1 years worth of logs),(don't select printable)
>
> the results appear way off the screen (the message body looks fine, but the
> title, etc extend way off the screen).
>
> Printable doesn't have this problem.
I could not reproduce this problem. Can you send me the exact URL (the
address with all the parameters from your browser's address bar like
http://midas.psi.ch/elogdemo/Forum/?npp=57...) and tell me exactly under
which browser this happens? |
Feature request, posted by Nick on Tue Feb 11 11:26:03 2003
|
Can you consider implementing the following additions to the functionality
1) Subt on edit <attribute> = xyz
This would be fantastic for implementing version control so you can see who
has edited a posted or a db entry.
2) Have a SORT fieldname flag so you can decide which column to sort things
by on a display listing in conjunction to the display flags, it current
defaults to the # column and I find i am directly linking to a sorted
display
3) Have the elogd.conf track actual log entries people have changed
detailing date and time etc.
4) Ability to export contents of the log books to files on disk for backup
purposes as all data is contained within a single log file which causes
problem for command line searches.
Many thanks |
Re: Feature request, posted by Stefan Ritt on Tue Feb 11 11:45:22 2003
|
> Can you consider implementing the following additions to the functionality
>
> 1) Subt on edit <attribute> = xyz
>
> This would be fantastic for implementing version control so you can see
who
> has edited a posted or a db entry.
Can you give me an example of how you would use that?
> 2) Have a SORT fieldname flag so you can decide which column to sort
things
> by on a display listing in conjunction to the display flags, it current
> defaults to the # column and I find i am directly linking to a sorted
> display
Sorting is not done by the "#" column but by the sequence when messages have
been entered. You can sort the table differently by clicking on the table
titles (twice for reverse sort). To sort by default on a column, for example
sort by the author, you can add
Start page = ?sort=author
into elogd.cfg which does the job.
> 3) Have the elogd.conf track actual log entries people have changed
> detailing date and time etc.
Revision management is not forseen by the structure of the ELOG database.
What you can do is if you edit a message you check "Resubmit as new entry",
then you keep a copy of the old version.
> 4) Ability to export contents of the log books to files on disk for backup
> purposes as all data is contained within a single log file which causes
> problem for command line searches.
Well, you have already all log book files on disk in a simple format:
YYMMDDa.log
(Year/Month/Day) which you can easily backup. By a mask like 02*a.log you
can backup all data from 2002 and so on. The idea of having separate log
files for each day is to have this possibility to simply backup various date
intervals.
What kind of command line searches are you interested in?
- Stefan |
Re: Feature request, posted by Nick on Wed Feb 12 01:11:08 2003
|
> > Can you consider implementing the following additions to the functionality
> >
> > 1) Subt on edit <attribute> = xyz
> >
> > This would be fantastic for implementing version control so you can see
> who
> > has edited a posted or a db entry.
>
> Can you give me an example of how you would use that?
-----
Lets say you are storing configuration information relating to a customers
solution, you need the ability to track who has made what changes to the
config information stored in the log book so you can backtrack who changed
what and when, for example
If you have a field name called Last Edited by this field is locked and not
editable using the Lock attributes flag, but if you had Subt on edit
everytime that entry is updated it places your login name into this field and
therefore stamps it to say you have edited it, as the field isnt free txt it
cant be spoofed as the $long_name comes from your login details.
-----
>
> > 2) Have a SORT fieldname flag so you can decide which column to sort
> things
> > by on a display listing in conjunction to the display flags, it current
> > defaults to the # column and I find i am directly linking to a sorted
> > display
>
> Sorting is not done by the "#" column but by the sequence when messages
have
> been entered. You can sort the table differently by clicking on the table
> titles (twice for reverse sort). To sort by default on a column, for
example
> sort by the author, you can add
>
> Start page = ?sort=author
>
> into elogd.cfg which does the job.
----
Excellent I didnt know what Ill try that tomorrow
----
|
Re: Feature request, posted by Stefan Ritt on Wed Feb 12 08:54:05 2003
|
> > > Can you consider implementing the following additions to the
functionality
> > >
> > > 1) Subt on edit <attribute> = xyz
> > >
> > > This would be fantastic for implementing version control so you can see
> > who
> > > has edited a posted or a db entry.
> >
> > Can you give me an example of how you would use that?
>
> -----
>
> Lets say you are storing configuration information relating to a customers
> solution, you need the ability to track who has made what changes to the
> config information stored in the log book so you can backtrack who changed
> what and when, for example
>
> If you have a field name called Last Edited by this field is locked and not
> editable using the Lock attributes flag, but if you had Subt on edit
> everytime that entry is updated it places your login name into this field
and
> therefore stamps it to say you have edited it, as the field isnt free txt
it
> cant be spoofed as the $long_name comes from your login details.
Ok, I implemented "Subst on edit", it will be contained in Version 2.3.1
which is supposed to come out next week.
- Stefan |
elog notification process causes the email to be truncated when going to Blackberry, posted by eric wooten on Mon Feb 10 23:05:36 2003
|
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 |
Re: elog notification process causes the email to be truncated when going to Blackberry, posted by eric wooten on Mon Feb 10 23:11:25 2003
|
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 |
Re: elog notification process causes the email to be truncated when going to Blackberry, posted by eric wooten on Mon Feb 10 23:19:50 2003
|
I just noticed that the notifications I receive from your ELOG system,
doesn't show anyone in the "TO:" section but myself. Or is ELOG configured
to only send myself a message?
> 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 |
Re: elog notification process causes the email to be truncated when going to Blackberry, posted by Stefan Ritt on Tue Feb 11 08:57:39 2003
|
> I just noticed that the notifications I receive from your ELOG system,
> doesn't show anyone in the "TO:" section but myself. Or is ELOG
configured
> to only send myself a message?
This is on purpose. I have many people registered for the Forum. So when a
notification is sent, it is not a good idea if everybody sees everybody
else's mail addresses. Therefor I have
Omit Email to = 1
in the config file. This way the "To:" field is omitted to "hide" the mail
recipients from each other. Your mail client realizes that and fills in your
own address automatically, that's why you only see yourself. Maybe you try
that option, might help with your previous problem as well.
- Stefan |
Author attribute as a Quick Filter?, posted by eric wooten on Thu Feb 6 15:16:30 2003
|
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 |
Re: Author attribute as a Quick Filter?, posted by Stefan Ritt on Thu Feb 6 15:46:11 2003
|
> 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. |
Write only, posted by Matthew on Thu Jan 30 19:52:46 2003
|
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? |
Re: Write only, posted by Stefan Ritt on Fri Jan 31 09:49:43 2003
|
> 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. |
Re: Write only, posted by Matthew on Fri Jan 31 20:47:51 2003
|
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. |
Re: Write only, posted by Stefan Ritt on Fri Jan 31 21:09:47 2003
|
> 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. |
confused name in the attributes section, posted by Etienne Van Caillie on Tue Jan 21 10:04:46 2003
|
do not use confused name in attributes
**************************************
like
Attributes Type, Type2
the info on Type2 will be placed in the Type also
see attachment 1
Never use confused name like '
Attributes PC_Memory, Memory
If Stephan need more info I can send a exemple of the logbooks
Etienne |
Re: confused name in the attributes section, posted by Stefan Ritt on Fri Jan 24 12:24:18 2003
|
> do not use confused name in attributes
> **************************************
> like
> Attributes Type, Type2
> the info on Type2 will be placed in the Type also
> see attachment 1
>
> Never use confused name like '
> Attributes PC_Memory, Memory
I acknowledge the problem. It had to do with the fact that for checkbox
options, the first checkbox is submitted in the above case as "Type0", the
second as "Type1", and the third as "Type2" which conficts with the other
attribute. I fixed that and use now "Type#0" and so on which should be fine.
The fix will be included in V2.2.6.
Stefan |
call a shell from ELOG / new button [Submit & Notify], posted by Etienne Van Caillie on Sat Jan 11 19:44:29 2003
|
propose to put
[Submit] [Back] [Submit & Notify] button on top/bottom
new parameter 'shell option'
[test]
...
Attributes = NotifyMode, Param1....Param10, Adresse, Subject, ...
Options NotifyMode = mail, SMS, Fax, printer...
; this command will invoque a shell command
; example
ShellCommand = <my shell command> parameters ...
like in WINDOWS 2000
ShellCommand = START.EXE notify.bat $NotifyMode $Param1, $Param2, $Param3
; in this case no necessity to modify the C source
; in windows I suggest the start.exe with a exit command
; so no necessary to wait the return code from the shell |
Re: call a shell from ELOG / new button [Submit & Notify], posted by Stefan Ritt on Mon Jan 13 11:45:18 2003
|
I put this on the wish list.
- Stefan |