| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67675
|
Mon Mar 10 15:18:51 2014 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.9.2-2455 | Re: Author drop-down menu length |
| Kay Graf wrote: |
|
I am handling several ELOGs for medium-sized collaborations (scientific experiments) with a large number of authors (~250) and chose to have single-user access and entries for every author - in the config file, the "Options Author"-List contains ~150 name for now.
However, the Author drop-down menu stops after ~100 names - is that a ELOG-webserver hard limit? I checked there is nothing strange in the author names following (no strange character, etc.).
I tested it on Firefox, Chrome, Safari - it does not seem to be a browser issue.
Any help would be highly appreciated.
|
Hello Kay,
I had to look it up in the source code: yes, you are right, it is hard-coded in elogd.h
⇄
English (auto-detected) » English
elogd.h:#define MAX_N_LIST 100
You can of course change the limit and recompile.
As an alternative, you could have sub-menus with less than 100 entries (disclaimer: the following is untested example):
Attributes = author_range, author, ...
options author_range = A-K{1}, L-Z{2}
{1} options author = Andi, Bob, Camilla, Dennis, ..., Kay
{2} options author = Lily, Max, Norbert, Oscar, ..., Zeta
Cheers
Andreas |
|
67674
|
Mon Mar 10 12:15:07 2014 |
 | Kay Graf | kay.graf@fau.de | Question | Linux | 2.9.2-2455 | Author drop-down menu length | I am handling several ELOGs for medium-sized collaborations (scientific experiments) with a large number of authors (~250) and chose to have single-user access and entries for every author - in the config file, the "Options Author"-List contains ~150 name for now.
However, the Author drop-down menu stops after ~100 names - is that a ELOG-webserver hard limit? I checked there is nothing strange in the author names following (no strange character, etc.).
I tested it on Firefox, Chrome, Safari - it does not seem to be a browser issue.
Any help would be highly appreciated. |
|
67673
|
Wed Mar 5 07:53:01 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | V2.9.0-241 | Re: How to upload several images at once |
| Alejandro Gomez wrote: |
|
Hi
I just want to know if there is a way to upload a bunch of images at once. I need to upload ~50 images per day and of course it is really tedious.
Thanks!!
|
The "standard" HTML protocol does not allow multiple selection of images. You can use the "elog" command-line utility to upload images from the terminal window. We plan in the summer this year a switch to HTML5, which does allow upload of multiple images plus a drag-and-drop functionality.
/Stefan |
|
67672
|
Wed Mar 5 03:58:51 2014 |
| Alejandro Gomez | alefisico@gmail.com | Question | Linux | V2.9.0-241 | How to upload several images at once | Hi
I just want to know if there is a way to upload a bunch of images at once. I need to upload ~50 images per day and of course it is really tedious.
Thanks!! |
|
67671
|
Tue Mar 4 19:48:02 2014 |
| Donald | don.drummel@gmail.com | Question | Windows | 2.9.2-2475 | Re: XML import Error |
| Andreas Luedeke wrote: |
|
| Donald wrote: |
|
Hi
I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.
When i attempt a import i get this error
"XML file does not contain <ENCODING> element"
The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.
is there something obvious that I'm missing?
here is the config of the log book:
[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type
|
Hi Donald,
yes, the import function gave me some headache in the past, too.
⇄
English (auto-detected) » English
Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.
(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)
In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.
My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)
I hope this helps.
|
Hi Andreas
That worked, thank you so much. now I'm on to a new error.
Now every time i try to do the import it crashed the elogd.
OS is windows server 2008 R2. I have the elogd installed as a service.
here is the even log:
Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Exception code: 0xc0000417
Fault offset: 0x000682da
Faulting process id: 0x558
Faulting application start time: 0x01cf37d8870fc9a1
Faulting application path: D:\Program Files (x86)\ELOG\elogd.exe
Faulting module path: D:\Program Files (x86)\ELOG\elogd.exe
Report Id: defc3f39-a3cb-11e3-9dd5-005056954c86
I have attached the Data file I'm using to generate the fault every time. same config as before. Any Ideas?
|
| Attachment 1: new__2.xml
|
<?xml version="1.0" encoding="UTF-8"?>
<ELOG_LIST>
<ENTRY>
<MID>
2
</MID>
<DATE>
2014-02-24 22:28
</DATE>
<OBJECT>
Archived Client:
</OBJECT>
<ACTION>
Archived Client:
Archived Client to Manual_Archive and took a full backup of it
</ACTION>
<ENCODING>plain</ENCODING>
<TEXT>
ticket: 123456
Decommission of client.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
<ENTRY>
<MID>
3
</MID>
<DATE>
2014-02-20 20:15
</DATE>
<OBJECT>
Added client:
</OBJECT>
<ACTION>
Added client:
Added client to VMware policy
</ACTION>
<ENCODING>plain</ENCODING>
<TEXT>
Ticket 1919191
New DHCP server needed to be backed up.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
</ELOG_LIST>
|
|
67670
|
Mon Mar 3 15:42:29 2014 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 2.9.2-2475 | Re: XML import Error |
| Donald wrote: |
|
Hi
I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.
When i attempt a import i get this error
"XML file does not contain <ENCODING> element"
The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.
is there something obvious that I'm missing?
here is the config of the log book:
[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type
|
Hi Donald,
yes, the import function gave me some headache in the past, too.
⇄
English (auto-detected) » English
Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.
(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)
In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.
My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)
I hope this helps. |
|
67669
|
Thu Feb 27 15:15:55 2014 |
| Donald | don.drummel@gmail.com | Question | Windows | 2.9.2-2475 | XML import Error | Hi
I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.
When i attempt a import i get this error
"XML file does not contain <ENCODING> element"
The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.
is there something obvious that I'm missing?
here is the config of the log book:
[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type |
| Attachment 1: new__2.xml
|
<?xml version="1.0" encoding="UTF-8"?>
<ELOG_LIST>
<ENTRY>
<MID>
2
</MID>
<DATE>
2014-02-24 22:28
</DATE>
<OBJECT>
Archived Client:
</OBJECT>
<ACTION>
Archived Client:
Archived Client to Manual_Archive and took a full backup of it
</ACTION>
<TEXT>
ticket: 123456
Decommission of client.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
<ENTRY>
<MID>
3
</MID>
<DATE>
2014-02-20 20:15
</DATE>
<OBJECT>
Added client:
</OBJECT>
<ACTION>
Added client:
Added client to VMware policy
</ACTION>
<TEXT>
Ticket 1919191
New DHCP server needed to be backed up.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
</ELOG_LIST>
|
|
67668
|
Fri Feb 21 13:43:03 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.9.2 | Re: Google Places API AutoComplete |
| Garret Delaronde wrote: |
|
G'day everyone.
Looking for some input on this idea.
I work for an organization which uses elog extensively for day to day operations.
In several of our logbooks we use a "location" attribute where we would enter an address or intersection.
I am working with the google places api and am able to create the auto complete form in a separate html page, but am interested if anyone has a good direction how i could change the input box into the google map autocomplete search box.
I have the code already for the api search box. but when i add it to the config it doesn't really do anything different.
Attached is the html file i setup with the api code.
the autocomplete works great, now i just want it to work in elog.
Any help is much appreciated!
And perhaps the Elog Powers that be might be interested in making it a function down the road? :)
|
Looks like a nice idea. You can sneak in any JavaScript code into elog pages with the "Top text" option. Like
Top text = <script>window.onload = function() {...}</script>
Then you parse the DOM tree to find your input field for the location, and attache your JS code to it. All the input fields have the "name" attribute in the HTML code set, so it should be easy to find the input field in the DOM tree.
/Stefan
|
|