Re: Find empty attributes, posted by Andreas Luedeke on Wed Feb 17 18:08:53 2016
|
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
|
|
|
Re: Find empty attributes, posted by Stefan Ritt on Wed Feb 17 18:33:18 2016
|
Cool, I didn't know that trick myself, thanks for sharing.
| Andreas Luedeke wrote: |
|
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
|
|
|
|
Re: Custom input forms implementation, posted by JD on Fri Jul 8 12:09:45 2016
|
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.
|
|
|
Re: Custom input forms implementation, posted by Andreas Luedeke on Sat Jul 9 10:44:45 2016
|
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.
|
|
|
string length limit in url tag, posted by Don on Wed Jul 20 16:03:24 2016
|
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. |
|
Re: string length limit in url tag, posted by Andreas Luedeke on Thu Jul 21 06:15:44 2016
|
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.
|
|
New elog version 3.1.2, posted by Stefan Ritt on Mon Sep 5 10:31:02 2016
|
A new version 3.1.2 of elog has been released today and can be retrieved through the normal download section. Since it fixes some vulnerabilities, it is recommended to update to this version.
Stefan |
|
Display of draft entries in elog, posted by Stefan Ritt on Fri Dec 2 13:54:36 2016
|
Dear all,
there seems to be still lots of confusion with the new "draft modus" introduced in elog 3.1.2. Here is how it works:
If you edit an old or new entry, your changes are written to the elog server every few seconds. The entry in the elog database is marked as "draft". The idea behind that is that if your browser crashes or you navigate away from the elog page without saving your entry, the "draft" entry is sill in the elog database and can be recovered later. This is typically useful on some shift logbooks, where people keep the entry open for many hours and add things every few minutes. If they have a crash, they would loose a few hours of information.
The draft modus now has a few drawbacks:
- If you have some draft entries in your elog database, you don't see them until you hit "New" the next time. Then the system offers you to continue the open draft entries.
- Once you change an existing entry, you cannot go back to the version of that entry before you started to make modifications. The only option is to keep the current version or delete the whole entry. The old version of your entry in the database is overwritten every few seconds with the current contents of your edit text field.
To fix the first problem, I introduced a new flag "List drafts = 0|1". If this flag is 1, the draft entries are shown in the list view. The default value for this flag is 1, so normally you should see the draft entries in the database. You should refrain from editing these entries if you know that currently somebody else is working on them, otherwise you will overwrite each other's modifications. The modification is in the current git version of elog which is 3.1.2-6ec506b.
The scond drawback is harder to address. In order to go back to previous version, you would need a full version system (ala git), which is far beyond the scope of elog. I'm working on a partial fix by storing the contents on an entry inside the browser when you start editing an entry. You can then "cancel" your modifications by pasting back the original version from your browser. This works of course only if your browser does not crash or you do not navigate away from the elog page, in which case the original version will be lost.
If anybody has a strong opinion about these changes, please post them here.
Stefan |
|