Is there any way to log child events on the detail pages for a fixed number of entries on the main page? For example, I have 15 vehicles to enter on the main page, ID'd by Vehicle Number. Within each of those entries I will be logging ongoing repair service entries with certain attributes.

So how might I design this concept without having repeating vehicle entries on the main page for every service event, and preferably without splitting the information between two linked logbook tabs?

Can the size of the application log file affect performance?

Is there any potential impact/concern with the Log4j exploit in Elog applications?

We're up to 30 logbooks, 3.2GB data total and Elog damen has now become slow. Performance stats show 100%CPU on startup then reduces. Searches and general UI activity is slow. It runs on a VM with 4GB memory allocated. Up to 15 concurrent users.

Trimming and archiving some data files may help but I gather overall this is underpowered hardware in this instance so what is recommended system requirements for a config like this?

Got the same problem, solved by manually unzipping "scripts/fckeditor.zip" from the sources to the installation directory (/usr/local/elog/scripts)

A better solution is to modify the Makefile :

@unzip -q -f scripts/fckeditor.zip -d $(ELOGDIR)/scripts/

which doesn't work on my Ubuntu 8.04; however changing to:

@unzip -q scripts/fckeditor.zip -d $(ELOGDIR)/scripts/

does...

I seem to be having some trouble with Find when using conditional attributes.

when I change the primary attribute in the find field, the corrispnding secondary attribute dosn't refresh properly with the list of values.

I am able to use the conditional options as expected when creating a new logbook.

I am using version ELOG V3.1.1-0767eb0 running on debian wheezey (compiled from sid sources)

This may be due to how I have my config file setup

Example:

Attributes = A, B
Options B = Please Select A
Options A = One{1}, Two{2}
{1} Options B = 1, 2,
{2} Options B = 3, 4,
 

Uppon closer inspection, removing the option to preset the secondary attribute as a Option list dosn't do anything for the find page.

This:

Attributes = A, B
Options A = One{1}, Two{2}
{1} Options B = 1, 2
{2} Options B = 3, 4

Still fails to set attribute B to a option list on  the find page.