| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68262
|
Wed Feb 17 18:08:53 2016 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Info | All | ELOG V3.1.1-3f3 | Re: Find empty attributes | It is possible for normal string attributes: the regular expression pattern "^$" can be used to search for an empty string.
E.g. in this Forum "ELOG Version" is a required attribute, and should never be empty. But if you search for:
you'll find a couple of entries from a time where it apparently wasn't a required attribute.
Cheers
Andreas
| Arno Teunisse wrote: |
|
Want to use the find function from ELOG to search for empty fields ( Attributes that are not defined )
How to do that ?
Could not find it in the Forum.
Greetings Arno Teunisse
|
|
|
Draft
|
Sat Jul 9 10:44:45 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | Windows | 3.1.1 | Re: Custom input forms implementation | 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:
And here is how it looks on the iPad:
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.
|
|
|
|
68363
|
Thu Jul 21 06:15:44 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | Linux | ELOG V3.1.0-241 | Re: string length limit in url tag | Several strings in ELOG are limited to 256 chars. It is likely the limit for URLs, too.
The magic number "256" appears 285 times in the elogd.c file.
It is probaly easier if you compress long URLs with goo.gl
Cheers, Andreas
| Don wrote: |
|
What is the string length limit in url tag and how to increase it?
For example,
[url=http://example.com?<text_string>]click here[/url]
When I provide very long <text_string>, it was truncated and showed partial link only.
|
|
|
68591
|
Thu Apr 6 11:01:30 2017 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | Windows | 3.1.2 | Re: pre defined Find as Home page | It's very simple, no need for the find command. E.g.: Start page = ?Author=luedeke&Category=Question&mode=summary
in this forum would do https://midas.psi.ch/elogs/Forum/?Author=luedeke&Category=Question&mode=summary
| Paraic Fahey wrote: |
|
This command makes the Homepage a FIND page: Start page = ?cmd=Find
My question is: can we pre-populate some of the search fields and execute the search so that the homepage becomes the SEARCH RESULTS
|
|
|
68830
|
Tue Aug 7 10:53:45 2018 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Info | Linux | elog-3.1.3 | Problem with eloglang.german_UTF8 | I had a problem with restarting ELOG since about a year, and finally I found the culprit. I just want to share it here, to prevent anyone else to make the same mistake,
Apparently the files resources/eloglang.* are rather sensitive to the syntax. But it doesn't tell you: no warning or error message comes up.
The file eloglang.german_UTF8 contains some "missing translations" at the end - and it looks like they produce some problems.
If you don't follow the instructions to create eloglang.german_UTF8 from eloglang.german, but use the file as it is, then the language handling will be corrupted:
some (very few) language strings will point into some void and display garbage strings.
In very rare cases this will even crash "elogd", in all other cases it will confuse your users.
Sometimes ELOG commands like "?Cmd=New" were affected, which makes ELOG unusable.
What made it very hard to debug was the fact that with every restart a different string was affected.
Everything looked fine, and later you see a string in the configuration page is wrong. Restarting fixed that string, but then some other string is gone.
So if you see such a behaviour, check your language file for "unusual syntax".
I haven't checked if the problem is limited to UTF8 - I only saw the problem with the eloglang.german_UTF8 file.
Cheers, Andreas |
|
69398
|
Thu Oct 21 00:42:42 2021 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | Linux | Unknown | Re: How to access PSI Elog data from other web clients | There is a python API to access ELOG via HTTP: https://github.com/paulscherrerinstitute/py_elog
| Lin Wang wrote: |
|
We want to develop separate mobile web pages for the web applications deployed at CSNS accelerator, including the PSI Elog.
In Elog, is there RESTful API or HTTP/JSON or HTTP/XML interface for other web clients to access?
Or is there any workaround?
|
|
|
1731
|
Tue Feb 28 09:56:55 2006 |
| Alex H | alex@synergie-inf.com | Info | Windows | 2.6.1-1653 | Re: MOptions problem ? | Hi Holger,
> Which ELOG version do you use?
I'am using the version V2.6.1-1653 of Elog
> From which logbook are the screenshots? (I assume it's Liste - right?)
Right :)!
I've just seen that Stefan has build a V2.6.1-1663 version of ELOG.
I try to install this new version and gave you answer as soon as possible :)! |
|
1733
|
Tue Feb 28 12:08:42 2006 |
 | Alex H | alex@synergie-inf.com | Info | Windows | 2.6.1-1668 | [SOLVED] Re: MOptions problem ? | Yop,
I think I found the solution! I was in fact a conditions conflict!
See the attached picture for easiest comprehension.
My list box type's conditions (FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}) conflict with my Equipment's conditions. It seems that the condition ID must be unique across the whole elogd.cfg.
So I have replaced my "Options Type = FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}"
by : "Options Type = FWL1{101}, FWL2{102}, FWL4{103}, VPN1{104}, VPN2{105}, CLIVPN-PROC"
and it works well  ! |
| Attachment 1: gotcha.gif
|
|
|