Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 138 of 807  Not logged in ELOG logo
    icon2.gif   Re: Add date and time stamp to file upload, posted by Fergus Lynch on Tue Oct 9 11:48:17 2007 

Stefan Ritt wrote:

Fergus Lynch wrote:
I would like to request a new feature - add date and time stamp to file upload. We use ELOG (amongst other things!) as a change log and this would really allow allow more accurate records to be kept. For instance we upload router config files (to record changes)and having the exact upload date would be a big enhancement, especially when there are a lot of attachments.


There is already a time and a date stamp. If you look in the logbook directory, you see attachments preceded with the date and time when they were submitted. You can see this date/time when you click on the attachment, such as in

http://midas.psi.ch/elogs/Config+Examples/040519_000348/elogd.cfg

where you will see it even in the URL (May 19th, 2004, 0:03:48) in the above case. I agree that this is not so obvious. If you make a proposal where this date/time should be displayed, I can easily add it.


Hi, I think this would be great new functionality, so I would propose the date/time stamp for an uploaded file was placed just after the file size text that appears at the far right hand side of all attachments.

Many Thanks
Fergus
    icon2.gif   Re: Add date and time stamp to file upload, posted by Stefan Ritt on Fri Oct 19 21:44:00 2007 

Fergus Lynch wrote:
Hi, I think this would be great new functionality, so I would propose the date/time stamp for an uploaded file was placed just after the file size text that appears at the far right hand side of all attachments.


I implemented this as you can see at elog:Linux+Demo/14 . The new feature will be contained in the next release, and will also work for entries made before this feature was implemented.
icon5.gif   Behaviour of text when using quote marks in header fields , posted by Fergus Lynch on Wed Feb 11 15:06:38 2004 
Hi,

First off let me say what an excellent program, simple yet powerful...

I've noticed some erratic behaviour when using "quote marks" in header 
fields.  Basically all text to the right of a " disappears.  Try adding an 
entry with quote marks or replying to this post.

Presume this is a bug.

Keep up the good work

Fergus
    icon2.gif   Re: Behaviour of text when using "quote marks" in header fields , posted by Stefan Ritt on Fri Feb 13 21:34:57 2004 
Like this one ^^^ ???

I'm joking! I fixed the bug and updated the elogd server. Please find the new 
version under CVS.

- Stefan
    icon7.gif   Re: Behaviour of text when using "quote marks" in header fields , posted by Fergus Lynch on Fri Feb 13 21:50:59 2004 
> Like this one ^^^ ???
> 
> I'm joking! I fixed the bug and updated the elogd server. Please find the new 
> version under CVS.
> 
> - Stefan

Blimey! That was quick!

Many thanks for amending this.  You'll be pleased to hear that my IT Operations  
Team think this is the best thing since sliced bread...its going to replace a 
blizzard of spreadsheets.

Cheers
Fergus
icon1.gif   Addition of a "Restrict edit attribute" option?, posted by Justin Ellison on Tue Mar 13 17:27:49 2007 
It would be a nice addition to have a config file option named "Restrict edit attribute".

Basically, I would like to have an attribute that was either:

a) An Option Attribute named Status with options of "Open" or "Closed"
b) An Option Attribute named Closed that was boolean.

Then, we could leave the item as editable until either choice "a" above was set to closed or choice "b" was true, at which point only admins could edit the item.

Sound plausible?

Justin
    icon2.gif   Re: Addition of a "Restrict edit attribute" option?, posted by Stefan Ritt on Tue Mar 13 20:58:07 2007 

Justin Ellison wrote:
It would be a nice addition to have a config file option named "Restrict edit attribute".

Basically, I would like to have an attribute that was either:

a) An Option Attribute named Status with options of "Open" or "Closed"
b) An Option Attribute named Closed that was boolean.

Then, we could leave the item as editable until either choice "a" above was set to closed or choice "b" was true, at which point only admins could edit the item.


Conditional attributes? Like:
Attributes = ..., Status
Options Status = Open{1}, Closed{2}

{2}Locked attributes = Status

Unfortunately once it's locked, the admin has to change the config file to unlock it.
    icon2.gif   Re: Addition of a "Restrict edit attribute" option?, posted by Justin Ellison on Wed Mar 14 15:03:41 2007 
Sorry, I didn't explain it enough.

This feature is like "Restrict edit time", but instead of setting an entire entry as read only after n hours, we set it read only if attribute y is true. Admin would be able to go in and reset that attribute to false to unlock the entry for editing, but no one else would be able to.

That make more sense?

Justin
ELOG V3.1.5-3fb85fa6