> Short of manually editing the logbook files, is there a way I can change the
> date of an entry?  I want to transfer my "Linux Journal", which I have been
> writing as a regular document for several months, into elog so I can take
> advantage of the threading, sorting, find, etc.

You cannot change the entry date, since this is kind of system stamp which 
should not be modified. But you can add an attribute like "Issue" for your 
Linux Journal, where you can add manually the month and year of release or so. 
Then you can preset this attribute with the current date, which you can change 
for older issues, like

Attributes = ...., Issue
Preset Issue = $date
Date format = %B %Y

Hope this helps.

- Stefan

> > Short of manually editing the logbook files, is there a way I can change the
> > date of an entry?  I want to transfer my "Linux Journal", which I have been
> > writing as a regular document for several months, into elog so I can take
> > advantage of the threading, sorting, find, etc.
> 
> You cannot change the entry date, since this is kind of system stamp which 
> should not be modified. But you can add an attribute like "Issue" for your 
> Linux Journal, where you can add manually the month and year of release or so. 
> Then you can preset this attribute with the current date, which you can change 
> for older issues, like
> 
> Attributes = ...., Issue
> Preset Issue = $date
> Date format = %B %Y
> 
> Hope this helps.
> 
> - Stefan


Yes! Thank you.  But now another question.  How can I hide the entry date
attribute on the summary screens and automatically sort by Issue?  No point in
showing both dates.

> > > Short of manually editing the logbook files, is there a way I can change the
> > > date of an entry?  I want to transfer my "Linux Journal", which I have been
> > > writing as a regular document for several months, into elog so I can take
> > > advantage of the threading, sorting, find, etc.
> > 
> > You cannot change the entry date, since this is kind of system stamp which 
> > should not be modified. But you can add an attribute like "Issue" for your 
> > Linux Journal, where you can add manually the month and year of release or so. 
> > Then you can preset this attribute with the current date, which you can change 
> > for older issues, like
> > 
> > Attributes = ...., Issue
> > Preset Issue = $date
> > Date format = %B %Y
> > 
> > Hope this helps.
> > 
> > - Stefan
> 
> 
> Yes! Thank you.  But now another question.  How can I hide the entry date
> attribute on the summary screens and automatically sort by Issue?  No point in
> showing both dates.


I figured out how to hide columns, using the "Display search" parameter.  (BTW,
suggest you modify the Administrator manual to mention that "Display search" applies
  to the initial display as well as any "Find"s.  I had seen this, but assumed it
only applied to actual search results.)  Still have not figured out how to change
the default sort attribute however.

> I figured out how to hide columns, using the "Display search" parameter.  (BTW,
> suggest you modify the Administrator manual to mention that "Display search" applies
>   to the initial display as well as any "Find"s.  I had seen this, but assumed it
> only applied to actual search results.) 

Fully agree. The name comes from historical reasons. I renamed "Display search" 
to "List Display". Will come in the next version.

> Still have not figured out how to change
> the default sort attribute however.

There is a little trick to do that:

Start page = ?rsort=Issue

Since sorting is done only lexically, you need a special date format like

Date format = %Y %m %d

in order to sort correctly.

> > I figured out how to hide columns, using the "Display search" parameter.  (BTW,
> > suggest you modify the Administrator manual to mention that "Display search" applies
> >   to the initial display as well as any "Find"s.  I had seen this, but assumed it
> > only applied to actual search results.) 
> 
> Fully agree. The name comes from historical reasons. I renamed "Display search" 
> to "List Display". Will come in the next version.
> 
> > Still have not figured out how to change
> > the default sort attribute however.
> 
> There is a little trick to do that:
> 
> Start page = ?rsort=Issue
> 
> Since sorting is done only lexically, you need a special date format like
> 
> Date format = %Y %m %d
> 
> in order to sort correctly.

Thanks again!  That did the trick.  One little hassle is that I had to go back and edit
all the Issue fields in my existing records so they would have the correct date format.

Rock on OSS!

Not really, you are the first one reporting this issue. Just some thoughts:

- Can you see the changes if you look at elogd.cfg with a text editor such as notepad?

- Some write protection of elogd.cfg

- Do you have more than one server running at the same time and changing the wrong one's config?

- Stefan 

>- Can you see the changes if you look at elogd.cfg with a text editor such as notepad?

I change the configuration directly on elogd.cfg, (after i save and update my web page, and i not modification immediately)

>- Some write protection of elogd.cfg

no

- Do you have more than one server running at the same time and changing the wrong one's config?

i have one server with elog

 Let me report when I see this behaviour.

If I use a text editor on elog.cfg directly, while elog is running, then when I save the file, the new elog.cfg is in place,

but the running elog is still running with the old configuration.  You have to restart elog for it to read the new config file and

use the new settings.

This does not apply if you edit elog.cfg via the "config" option in the menu command, where elog will read the new elog.cfg

just after it has been saved.

The reason I sometimes edit the file directly is if I want to create a new logbook, but with all the configuration of another logbook,

and it's quickest to cut-and-paste,  change the heading, create a new directory and restart elog.

This may be completely off what is being reported.