Let me start by saying that I really like ELOG-- it's a nice tool.

I'm trying out version 2.3.3. The problem that I'm having is with
attachments disappearing when I do the following:

1. create a new entry that contains one or more attachments.
2. verify that the new entry from step 1 saved correctly.
3. reply to the entry from step 1.
4. return to the entry from step 1 only to find the attachments gone.

The attachement files are still in the logbook directory, it's just that
they are no longer attached to the entry.

FWIW, I've attached the elog.config that I'm using...

Thanks,

Greg

I wondered if there was a config line that enabled/disabled the forward and backward navigation keystrokes that were implemented in 2.7.0?

The current definitions (Control-PgUp/PgDown/Home/End) interfere with those keys I use to navigate between tabs in Firefox.  It'd be nice if they could either be turned off.. or redefined.

I have tried to set Email Format = 111 but still receiving attachments in the notification emails.  Does anyone know how to configure?  So the notification email will not include attachments.

Thanks in advance,

H. Dao

Hi,

Is it possible to disable the Previewbutton?

Regards
Ulf Olsson

Hi, I have a logbook where users can add entries and edit entries.

The delete option has been removed from the menu, but when they edit an entry they are able to delete the entry.

Is there a way to remove the Delete option from the menu that appears when Editing an entry?

Please advise,

Thanks,

John

I am trying to unify several existing logbook collections that run on
seperate servers under a single server using groups.  For a top group, under
"[global topgroupname]", I would like to redefine the resource directory or
the logbook directory so that everything except for the .cfg is at it
original location.  However, it seems like "Resource dir" and "Logbook dir"
can not be redefined in the global section for specific groups.  Is it
possible to redefine these directories for each top group, or is it feature
that could be added?

I could probably do what I want with soft-links, but redefining the resource
dir just seems to be right way to do this.  (For one thing, I would like
different favicons for each group.)

We have about 10 logbooks running on the same Elog that all get fair use. Many people have turned off new entry emails because they were filling up inboxes, but are still interested in what's new. I saw the option to add "?last=1" to the start page, although I'm afraid using it might cause confusion over how to get to the older posts.

I was trying to figure out a way of creating a "digest" of sorts, a list of entry subjects posted in the past day or week, something similar to what's generated by "?last=1?mode=threaded", but for every logbook (similar layout to the selection page with nested logbooks). This could either be a page, or a regular email.

Is there way to generate such a cross-logbook page? What about a scheduled email formatted based on a given filter?

PS: The elog has been invaluable to us, a big thanks to all involved!

Hi,

I just implemented a different way CSS files are handled in ELOG. Previously, we had the default.css, which could be adjusted for specific needs. Some people did that (like myself). So I changed a few colors etc. When I now implement a new feature in elog, it might need a new CSS class which I put in default.css. But this means that people who have modified this file get it either overwritten, or do not get the new styles.

In order to fix this, the default.css is now called elog.css and is always inluded in any ELOG page. If one specifies a CSS file with "CSS = <file.css>", then this CSS file is loaded in addition to elog.css. So one can put only the modifications into that file and inherits all the rest from elog.css. If new features come in elog.css, the installation with the personalized CSS file will then get the new features from the new elog.css automatically, and just overwrite a few settings in the personalized file. Here is an example:

elog.css:

td {
  color:black;
  font-size:12px;

}

Personalized file special.css, activated with "CSS = special.css" in the elogd.cfg file:

td {
  font-size:18px;
}

This personalized file now overwrites the font size from elog.css to 18 pixel, while maintaining all the rest from elogd.css.

The modification is committed to GIT and will be contained in the next release of elog.

/Stefan