ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
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
----
|
2108
|
Wed Jan 10 22:54:56 2007 |
| Exaos Lee | Exaos.Lee@gmail.com | Info | All | SVN1780 | Chinese language files updated | As the attachment.
Sorry for no update long time. |
Attachment 1: eloglang-zh_CN.tgz
|
65780
|
Fri Mar 7 21:26:18 2008 |
| David Pilgram | David.Pilgram@epost.org.uk | Info | Linux | ELOG V2.7. | Re: Message ID and trouble ticketing system | >Stefan Ritt wrote:
>
>Ok, now I got the point, also Richard had the same problem. Assume we have 10 threads, and thus
>ticket numbers 1-10. Now we get a reply to #2, which then pops up to the top of the list. A new
>message increments the top entry of all entries, and then wrongly gives a new #3, instead of #11.
>
>I fixed this in SVN revision 2073, where elogd searches *all* logbook entries for the largest
>index, then increments this one by one. The fix will be contained in the next release.
----
Great! Thanks Stefan, off to download right now!
Great program, by the way, but don't think you need to be told that yet again! |
65781
|
Fri Mar 7 21:53:28 2008 |
| David Pilgram | David.Pilgram@epost.org.uk | Info | Linux | 2.7.3-2073 | Re: Message ID and trouble ticketing system | >>Stefan Ritt wrote:
>>
>>Ok, now I got the point, also Richard had the same problem. Assume we have 10 threads, and thus
>>ticket numbers 1-10. Now we get a reply to #2, which then pops up to the top of the list. A new
>>message increments the top entry of all entries, and then wrongly gives a new #3, instead of #11.
>>
>>I fixed this in SVN revision 2073, where elogd searches *all* logbook entries for the largest
>>index, then increments this one by one. The fix will be contained in the next release.
>
>----
>
>Great! Thanks Stefan, off to download right now!
>
>Great program, by the way, but don't think you need to be told that yet again!
---
Oh ho!
I've tried this on an existing database, where most entries do not have a ticket #. The previous entry #
(previous in ID sense) is T00550, say. But when I start a new thread, the ticket # is T00001. Is it being put
out by no entry for ticket # in most of the database?
LATER UPDATE.
On a small database (12 entries, with 45 comments in total), this worked as expected if most or all entries have ticket numbers, even if the previous (by id #) had not had a ticket number. (I had to edit every entry to put in ticket numbers).
The only thing I can think of is the number of entries that don't have a ticket #, or a line in the .log file entry saying "Ticket: " but am looking further into this.
(BTW, am posting this way to get around the proxy server problem I have!) |
66675
|
Wed Jan 13 10:59:44 2010 |
| David Pilgram | David.Pilgram@epost.org.uk | Info | Linux | 2.7.8 | Proxy Error | Having made one entry in the thread about message ID, I could neither edit the entry or add an additional reply
without getting "Proxy Error" messages. I've had this trouble on this forum before, a long time ago. Perhaps
it is connected with the html coding? |
66677
|
Wed Jan 13 11:15:10 2010 |
| David Pilgram | David.Pilgram@epost.org.uk | Info | Linux | 2.7.8 | Re: Proxy Error | > Having made one entry in the thread about message ID, I could neither edit the entry or add an additional reply
> without getting "Proxy Error" messages. I've had this trouble on this forum before, a long time ago. Perhaps
> it is connected with the html coding?
Hi Stefan,
I now cannot even reply to you in the message id thread; I keep getting:
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST /elogs/Forum/.
Reason: Error reading from remote server
Apache/2.2.3 (Scientific Linux) Server at midas.psi.ch Port 443
It is, I think, something to do with the html coding (as I normally use plain, I don't come across this as an issue).
However, in the cause of the experiment, I will submit this entry, then go back and edit it, and if I don't get
Proxy Error, then that certainly will be something to do with the html coding.
And this is an extra edited line - if you see this, I got past the proxy error issue this time. But did you get two
emails? |
66678
|
Wed Jan 13 11:17:39 2010 |
| David Pilgram | David.Pilgram@epost.org.uk | Info | Linux | 2.7.8 | Re: Proxy Error | > > Having made one entry in the thread about message ID, I could neither edit the entry or add an additional reply
> > without getting "Proxy Error" messages. I've had this trouble on this forum before, a long time ago. Perhaps
> > it is connected with the html coding?
> Hi Stefan,
>
> I now cannot even reply to you in the message id thread; I keep getting:
>
> Proxy Error
>
> The proxy server received an invalid response from an upstream server.
> The proxy server could not handle the request POST /elogs/Forum/.
>
> Reason: Error reading from remote server
>
> Apache/2.2.3 (Scientific Linux) Server at midas.psi.ch Port 443
>
> It is, I think, something to do with the html coding (as I normally use plain, I don't come across this as an issue).
>
> However, in the cause of the experiment, I will submit this entry, then go back and edit it, and if I don't get
> Proxy Error, then that certainly will be something to do with the html coding.
>
> And this is an extra edited line - if you see this, I got past the proxy error issue this time. But did you get two
> emails?
That is interesting. I can make 1 (one) submission to a thread which uses html coding, then I get hit by proxy errors.
But I can edit, play around or whatever if it is in plain coding. Yet to see how many emails were generated... |
66679
|
Wed Jan 13 11:19:59 2010 |
| David Pilgram | David.Pilgram@epost.org.uk | Info | Linux | 2.7.8 | Re: Proxy Error | > > > Having made one entry in the thread about message ID, I could neither edit the entry or add an additional reply
> > > without getting "Proxy Error" messages. I've had this trouble on this forum before, a long time ago. Perhaps
> > > it is connected with the html coding?
> > Hi Stefan,
> >
> > I now cannot even reply to you in the message id thread; I keep getting:
> >
> > Proxy Error
> >
> > The proxy server received an invalid response from an upstream server.
> > The proxy server could not handle the request POST /elogs/Forum/.
> >
> > Reason: Error reading from remote server
> >
> > Apache/2.2.3 (Scientific Linux) Server at midas.psi.ch Port 443
> >
> > It is, I think, something to do with the html coding (as I normally use plain, I don't come across this as an issue).
> >
> > However, in the cause of the experiment, I will submit this entry, then go back and edit it, and if I don't get
> > Proxy Error, then that certainly will be something to do with the html coding.
> >
> > And this is an extra edited line - if you see this, I got past the proxy error issue this time. But did you get two
> > emails?
>
> That is interesting. I can make 1 (one) submission to a thread which uses html coding, then I get hit by proxy errors.
> But I can edit, play around or whatever if it is in plain coding. Yet to see how many emails were generated...
Hi Stefan,
I only got one email in response to the second entry of this thread, no email was received after the edit of the entry. The
next email received was due to the third entry of this thread. |
|