You could write a shell script, run it through cron and send mail from that. (even in windows I assume)

I'm (ab)using elog as a database and would like to use conditional attributes, like:

Attributes = PC Name, Operating System, Version, Distribution
Options Operating System = Linux{1}, Windows{2}
{1} Show Attributes Edit = Operating System, Distribution, PC Name
{2} Show Attributes Edit = Operating System, PC Name, Version

Problem is that there are several conditions and the list of attributes is rather long. Also, since it's a
rather dynamic environment I have to make new attributes all the time, and adding them to all "show attributes"
 lists is not only tedious, but bound to cause errors as well.
 

So... 

I was thinking, would it be an idea to make the list of attributes to be shown or hidden on a per attribute base.

 

Like:

Attributes = PC Name, Operating System, Version, Distribution

# hide specific attributes
Hide attributes = Distribution, PC Name

# or configure which fields should be shown allways
Show Attributes = Operating System, Version

# add attributes based on OS
Options Operating System = Linux{1}, Windows{2}
{1} Show Attribute Edit = Distribution
{2} Show Attribute Edit = PC Name

(just thinking out loud here).

Greetings,

I was wondering, is it possible to wrap lines in the config file ? 

I have to add a dropdown lost which is kinda long and typing everything on one line will make ik kinda unreadable.
Somehow wrapping the line so each entry will get on a separate line would make it much better readable. (which
makes less errors).

W.
 

Hello, I have installed ELOG in an Ubuntu 22.04 machine and is working great, but I have found a small bug with Author names.

I have the config set like this for the Author attribute:

Preset Author = $long_name
Locked Attributes = Author

For context, my name is Víctor, which includes the accented "í". When creating a new entry and submitting immediately seems to work well. However, if I create a new entry, save it as draft, go back to the list, and then go to the draft entry, the accented "í" has transformed into "Ã". If I repeat the process, it turns into "ÃÂ", and so on. As I have configured the Author to not be editable, the user cannot fix this manually.

I found a way around this bug by setting

Subst Author = $long_name

Which is okay for us, but might not be for everyone.

In fact I saved this entry as a draft and then on another tab tried to edit it and it wouldn't let me edit because the author name now did not match.

Hi,

sorry for bugging you with this, but I could not find any information for making migration of elog system from one server to another.
The migration should be done from one server version (CentOS 6.10 to CentOS 7.6). Also we are talking about migration from one subdomain to another. Example subdomain1.example.com to subdomain2.example.com. Old elog application version is 3.1.2 and I would like to migrate to the latest version 3.1.4 

Is the migration from one system to another possible?  What are the prerequisites for migration?
Are there any instructions how to do it?

Thank you in advance and have yourself a lovely day,
Warmest regards
 

Hello folks,

Can we have a better support under modern Linux distributions?

I'm trying to install elog in our webserver and it's becoming a boring task. First of all theres only RPM packages. And we really don't like the Red Hat method, so we use Debian Servers. More package mainteners would be nice.

The software appears to be working correctly, but there are some bugs (or perhaps missing dependencies?); the init script put in /etc/rc.d/init.d is broken under Debian:

First of all because it's in /etc/rc.d.

The second problem is in this line:

# Source function library.

#. /etc/rc.d/init.d/functions

The file doesn't even exists.

The third problem is the echo_success; echo_failure commands that doesn't even exist. As I can see it's definitions are sourced in the functions file that doesn't exist.

After removing this missing commands or files from the init.d; I can call elogd script and start the daemon under root. Appears to be working...

And last but not least; there's a way to standardize the init script to run in other Linux distros, so we can put it to start automatically at boot time?

Many thanks in advance,

Vinícius Ferrão 

PS: I'm not asking to support any creepy distros, but to support the .deb package format and system style.