ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
225
|
Wed Feb 19 01:46:03 2003 |
| Fred Hooper | fhooper@sushisoft.com | Question | | | Postdating the Entry Date | Is is possible to postdate the Entry Date for an entry?
The documentation lists the ability to forward date an entry, but I don't
see any ability to backdate an entry (edit the date to a date in the past).
Given that the entry date is part of the logbook entry file structure, it
wasn't obvious how to make this change.
thanks
fred |
224
|
Tue Feb 18 09:21:34 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | | | | Re: New Version | > I noticed the site has been updated as far as the documentation for 2.3.1,
> however the latest version in the downloads section is 2.3.0, any other
> places where I can get 2.3.1
>
> Cheers
Patience, patience! 2.3.1 is currently kind of in "beta" version, but will be
released this week. Not that you can always get the latest snapshot from the
CVS tree at
http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c
- Stefan |
223
|
Tue Feb 18 08:07:10 2003 |
| Nick | nikc@cnic.com | | | | New Version | I noticed the site has been updated as far as the documentation for 2.3.1,
however the latest version in the downloads section is 2.3.0, any other
places where I can get 2.3.1
Cheers |
222
|
Wed Feb 12 19:54:21 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Lost features since upgrade to 2.3.0 | > 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 |
221
|
Wed Feb 12 19:10:26 2003 |
| Kutlay Topatan | ktopatan@worldbank.org | Question | | | Re: Lost features since upgrade to 2.3.0 | 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 |
220
|
Wed Feb 12 08:56:29 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | | Re: Find | > 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? |
219
|
Wed Feb 12 08:54:05 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: Feature request | > > > 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 |
218
|
Wed Feb 12 01:11:08 2003 |
| Nick | Nick@nick.com | Info | | | Re: Feature request | > > 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
----
|
|