ELOG Forum

I was wondering if anyone out there has had any success with importing XML data into ELOG. Using the XML schema which I derive from the EXPORT data from ELOG into XML format or creating the file from scratch, I either blowup the system and have to restart elogd or it doesn't work and says, XML file doesn't contain ELOG_LIST element (which I create and it still doesn't work).

Basically, I am trying to take spreadsheet data, convert it into XML and upload it as a logbook so I don't have to perform lots of data entry. I also tried .CSV but have had no luck.

Any thoughts or ideas?

What happens if you just export as .CSV and then import that file again. Does that work?

If not, can you post your .CSV file here and I will have a look.

Stefan

67352

Wed Oct 3 14:23:55 2012

Re: Formating input fields with size and width

UlfO wrote:

Hi,

Why is the color of an inputfield changing when I have changed the size and width?

I have attached a example.

Regards
/UlfO

Please post your configuration file (or the relevant section therein) so that I can have a look.

/Stefan

67354

Wed Oct 3 14:34:58 2012

Re: Formating input fields with size and width

UlfO wrote:

Stefan Ritt wrote:

UlfO wrote:

Hi,

Why is the color of an inputfield changing when I have changed the size and width?

I have attached a example.

Regards
/UlfO

Please post your configuration file (or the relevant section therein) so that I can have a look.

/Stefan

OK!

Here it comes:

[Deployment-Plan-PRIMA]
Logbook Tabs = 0
Theme = default
Title Image= <img border=0 src="konturlogo_dynamate.png" alt="DynaMate logo">
Use Email From = weblog@dynamate.se
Use Lock = 1
Mode commands = 0
Comment = Deployment plan PRIMA SSG
Attributes = Activity number, Main Activity task, Activity task, Resources, Task Type, Status, Start Time
Options Main Activity task = Activities pre deployment, Install Changes into Prima, Post Go Live activities week after Go Live
Options Task Type = Depl, Pre, Prep Depl, Prep Test, Prod, Test
Options Status = Finished, Not started, Ongoing
Extendable options = Resources, Task Type, Main Activity task
Moptions Resources = BMM, PMM
Format Activity number = ,,,3,3
Type Start Time = Datetime
Type Activity Number = Numeric

Cell Style Status Finished = background-color:green
Cell Style Status Not started = background-color:red
Cell Style Status Ongoing = background-color:yellow
List Menu Commands = New, Last day, Help
Menu commands = List, New, Edit, Delete, Help
List Display = Activity number, Main Activity task, Activity Task, Start time, Resources, Task Type, Status
Page Title = Deployment plan PRIMA SSG - $Subject
List after submit = 1
Reverse sort = 1
Quick filter = Main Activity task, Resources, Task Type, Status

Ok, here it is. You wrote

Format Activity number = ,,,3,3

who told you that you can just leave out the first three arguments? The documentation says that you can trailing parameters can be omitted, not leading. So what you want is

Format Activity number = 0,attribname,attribvalue,3,3

/Stefan

67375

Wed Nov 7 13:14:15 2012

Re: Support for modern Linux

Vinícius Ferrão wrote:

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.

I'm not using Debian so I cannot give support there. There was some Debian support a few years ago, but the maintainer has gave this up. If you find someone who volunteers to do the job (yourself?) I'm happy to include the Debian specific files in the distribution.

Stefan

67382

Tue Nov 20 08:45:59 2012

Re: Need for email address in login?

Jeff Kozloski wrote:

How can I skip the need for an email address when registering and logging in? Our IT dept will not give an email address to each guy I want on the log.

I never thought that someone will not have an email address. One basic feature of ELOG is its automatic notification if there is a new entry, and that only works over email. It's like social networks, you cannot register for Facebook if you don't have an email address.

So if you absolutely want to omit this, just give a fake email address, like nobody@no.where. ELOG just checks if there is a "@" and a "." somewhere.

67389

Fri Nov 30 13:19:37 2012

Re: Default filtered view

UlfO wrote:

Hi,

Is it possible to have a default filtered view in E-log?

Lets say we have a record with status finished on one attribute.

Is it possible to have a default list view that just shows records with this status?

Sure. Lets assume you have a "Status" attribute, which can be "open" and "finished", then you need

Options Status = open, finished Quick Filter = Status Start page = ?Status=open

The quick filter gives you a drop-down box where you can switch quickly between "open" and "finished", while the "Start page" automatically filters for "open".

Goto page Previous 1, 2, 3 ... 321, 322, 323 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6