> > The only caveat is that
> > when you edit an entry, the "Last Edit" is displayed really in seconds since 1970, but I will
> > fix this in the next release.
> 
> I just fixed this in SVN revision #2010. If you would have filled out which operating system you use
> with elog, I could tell you how to upgrade.

Thank you for pointing out the method to identify Last Edit as a datetime type so that it will sort properly. I now have created Last Edit in several 
preexisting logbooks. 

I want to use 
Start page = ?rsort=Last Edit
to set the default sorting of each logbook to be by Last Edit. 

However, all of the entries made before I added Last Edit have no value for that field, so they are all grouped together at the end of the sort. So I 
decided to go through the older entries and set Last Edit equal to the original entry date, as a starting value.

I tried to use the command
Subst on edit Last Edit = $entry time
but it gives a "-" for the Last Edit value when I edit an entry. 

I think this is because $entry time is not a variable supported by Subst. Can you add that support, or else tell me if you know a better way to go about 
doing what I'm attempting? Is there perhaps a way to globally process a group of entries in a logbook and set one attribute's value to be equal to 
another's?

Thanks

 You've probably seen my other posts on this subject.

I want to be able to re-edit some entries but I need some way to know the dates entries were re-edited.

Am I just approaching this the wrong way? Should I disable re-editing of entries and use threads to follow changes by posting replies to an entry?

The only problem with that is that if I make a mistake I will have to submit a new entry to fix it. 

Thank you for your advice.

Hmm, I see your point, but wouldn't using the RSS feed have the same effect? Or are you saying the users just wouldn't know about it, so they wouldn't complain? 

I haven't explored the RSS feed options yet. I'll study them.

Hmm. Is there some way to set up a private RSS feed for me only?

If not, I would humbly ask that you add an option. I don't want to generate unnecessary email to users, but I need to always be notified for some logbooks. I'm responsible for some hardware on our project and I want to know any time someone reports a problem. The best solution is to still let users decide whether they want to subscribe to logbooks, and whether entry notification should be suppressed or not, but also have an admin override privilege. There could be a disclaimer "admin is automatically notified of all entries" at the top of the edit page.

If this can be done with a private RSS feed to me only, then that's fine. I still don't use or understand RSS feeds very well, sorry. I'd rather all users did not have the option to be alerted to every new entry, when email suppression is enabled. That would be contradictory, I think.

 Thanks for listening!

We are using elog to allow users to enter their time spent on a project and we would like them to be able to see the entries that they themselves have

created but not the entries that other users have created.

Thanks,

Herman