Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 227 of 796  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6364 Entries 
Goto page Previous  1, 2, 3 ... 226, 227, 228 ... 794, 795, 796   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subjectup
  69019   Sat Sep 28 09:07:05 2019 Reply Qisheng Wangwangqisheng@zjlab.org.cnInfoWindows3.1.1Re: Custom input forms implementation

Dear Andreas,

The same problem by using the shiftchecklist and the cfg in Stefan's mail. It report the no password file, even the absolute path wroten in cfg file.  The author field also failed to be read, it is shown as "?" in the page . Did there miss some other files?

Any suggestion is welcome. Thank you very much.

Qisheng

Andreas Luedeke wrote:

You might try to specify an absolute path to the password file in the configuration.

I would need a complete minimal configuration that creates that problem.

 

JD wrote:

Hello Stefan,

I created a custom form with the example you provided. When I enter the Data and Submit the Form I get the error message "Datei passwordfile.xml kann nicht geöffnet werden: No such file or directory".  Posting stuff works in all other logbooks.  Only in the "logbook with the form" there seems to be an error. (or misconfiguration on my side)

sections from my conf. File:

[global]
Password file = passwordfile.xml

(...)

[ShiftCheck]
Comment = Shift Check List

Attributes = Hardware, Raith-Mitarbeiter, Rechnername, Rechnername-alt, Details, SN, AV-Nummer, System, Key, IT-Mitarbeiter, Erledigt_datum, Ausgemustert_datum
Quick filter = Shift, Author
Options Shift = Morning, Evening, Night

Enable attachments = 0
Show text = 0
Custom new form =forms\shiftcheck.html
Custom edit form = forms\shiftcheck.html
Custom display form = forms\shiftcheck.html
List after submit = 1

I tried copying the password file to the forms directory, the logbook directory, the ShiftCheck logbook directory and the elog root folder.  I always get the same error.  I tried entering the absolute path, there was no difference in the result.

When I disable the password file I am able to post without any problems.  Can you help me out? 

Jonathan

 

Stefan Ritt wrote:

Dear ELOG users,

starting with SVN revision 2328, custom input forms are implemented. This allows application specific formats for check lists etc. In our specific case we had to implement a shift check list, which was quite long. Furthermore the check list should be optimized for an iPad, which we take in the field and record various checks and readings (in our case some gas pressure gauges at the PSI particle accelerator). Since the standard ELOG interface was too inflexible, a completely hand-written form was needed. The form can be activated by the new configuration options Custom New Form, Custom Edit Form and Custom Display Form, one for a new entry, an entry to edit and and entry to display. In our case we used the same form for all three cases. This is how the shift check list looks under the Safari Browser on a PC:

Capture.png

And here is how it looks on the iPad:

IMAG0036.jpg

Each section can be collapsed and expanded (blue arrows at the left), and various internal checks are made before the check list can be submitted.

Implementing such forms is however more something for the advanced user, since you have to hand-write HTML with CSS and JavaScript code. It can then however be a powerful method for check lists. Please find in the attachments the elogd.cfg configuration for that logbook and the shiftcheck.html source code file. It is a bit complicated since the page is a static page, elogd just serves it from the file. This requires all the dynamic functions to be implemented inside the HTML file with JavaScript. To display an entry for example, the JavaScript loads the raw data with the "?cmd=Download" command and the populates the form fields. The collapsing and expanding is done by using CSS properties. The integrated style sheet was optimized for the rendering on an iPad. Rather large fonts were chosen so that the items can be checked easily with your finger tips. Various parameters are sent between the browser and the elogd program via hidden fields and cookies. So only something for experts! But if you go through the effort and hand-write the form, it can be very handy. Note that you have to upgrade to SVN revision 2328 for the three new options.

 

 

 

 

  68044   Wed Jul 15 21:30:47 2015 Reply Erkcan Ozcanerkcan@gmail.comQuestionLinux3.1.0-5be245eRe: Customized email subject line for an updated entry

Since there were no responses, I decided to make good use of the fact that the software is thankfully open-sourced. I modified elogd.c and added just a couple of lines to get what I wanted.

22245,22250d22244
<    if (old_mail && getcfg(lbs->name, "Use Email Subject Edit", subject, sizeof(subject))) {
<       i = build_subst_list(lbs, slist, svalue, attrib, TRUE);
<       sprintf(str, "%d", message_id);
<       add_subst_list(slist, svalue, "message id", str, &i);
<       strsubst_list(subject, sizeof(subject), slist, svalue, i);
<    } else

 

These lines just follow the comment line: /* compose subject from attributes */

 

Erkcan Ozcan wrote:

Hi,

The default email subject line for a new entry is: "New ELOG entry", and the default email subject line for an edited entry is: "Updated ELOG entry". However when we set "Use Email Subject", both new entries and the updated entries use the same email subject. Is there an equivalent of "Use Email Heading Edit" for the subject line? I tried "Use Email Subject Edit", to no avail.

Thanks in advance,

e.

 

  68066   Tue Aug 4 13:29:45 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.0-5be245eRe: Customized email subject line for an updated entry

Thanks, I added your code to the distribution and updated the documentation.

Erkcan Ozcan wrote:

Since there were no responses, I decided to make good use of the fact that the software is thankfully open-sourced. I modified elogd.c and added just a couple of lines to get what I wanted.

22245,22250d22244
<    if (old_mail && getcfg(lbs->name, "Use Email Subject Edit", subject, sizeof(subject))) {
<       i = build_subst_list(lbs, slist, svalue, attrib, TRUE);
<       sprintf(str, "%d", message_id);
<       add_subst_list(slist, svalue, "message id", str, &i);
<       strsubst_list(subject, sizeof(subject), slist, svalue, i);
<    } else

 

These lines just follow the comment line: /* compose subject from attributes */

 

Erkcan Ozcan wrote:

Hi,

The default email subject line for a new entry is: "New ELOG entry", and the default email subject line for an edited entry is: "Updated ELOG entry". However when we set "Use Email Subject", both new entries and the updated entries use the same email subject. Is there an equivalent of "Use Email Heading Edit" for the subject line? I tried "Use Email Subject Edit", to no avail.

Thanks in advance,

e.

 

 

  67523   Mon Jun 3 15:53:22 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2Re: Daemonizing vs. shell execution

Martin Rongen wrote:

Hi all

I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.

Any ideas how I can resolve this problem?

Martin

Usually the problem comes from the fact that a daemon runs from the root directory ('/') by definition. I might not find your scripts if they are not in the path. Try to call them explicitly with the ful path like "/usr/local/elog/script.sh".

/Stefan 

  67527   Tue Jun 4 13:26:02 2013 Reply Martin Rongenmartin.rongen@rwth-aachen.deQuestionLinux2.9.2Re: Daemonizing vs. shell execution

Stefan Ritt wrote:

Martin Rongen wrote:

Hi all

I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.

Any ideas how I can resolve this problem?

Martin

Usually the problem comes from the fact that a daemon runs from the root directory ('/') by definition. I might not find your scripts if they are not in the path. Try to call them explicitly with the ful path like "/usr/local/elog/script.sh".

/Stefan 

 I didn't know that. Thanks for the quick response. I have it working now :)

  65733   Mon Feb 11 22:24:37 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux | WindowsV2.7.2Re: Data Export:: Date Problem

Richard Ecclestone wrote:

Hi

Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,

the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.

This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.

  What about exporting record separated by a semicolong ";" ?

  65734   Mon Feb 11 22:33:37 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux | WindowsV2.7.2Re: Data Export:: Date Problem

Stefan Ritt wrote:

Richard Ecclestone wrote:

Hi

Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,

the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.

This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.

  What about exporting record separated by a semicolong ";" ?

I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string.

  65735   Tue Feb 12 08:54:48 2008 Reply Richard Ecclestonerichard.ecclestone@cern.chBug reportLinux | WindowsV2.7.2Re: Data Export:: Date Problem

Stefan Ritt wrote:

Stefan Ritt wrote:

Richard Ecclestone wrote:

Hi

Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,

the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.

This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.

  What about exporting record separated by a semicolong ";" ?

I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string.

Hi Stefan

Thanks for the quick reply.

We seem to be running 2012 - Which may explain the problem - I will see with our system administrator why we are not running 2040. By the way I also had this problem when running the windows version.

Cheers.. Richard

Goto page Previous  1, 2, 3 ... 226, 227, 228 ... 794, 795, 796   Next  
ELOG V3.1.5-2eba886