Passing html code for table using elog command, posted by Remington Tyler Thornton on Thu May 22 21:39:55 2014
|
Hey,
I am testing out automated entries using elog on the command line. The file I pass has html code for a table; the resulting entry shows the html code for the table instead of generating the table. Is there a way to make elog parse the code to show a formatted table?
Thanks in advance. |
Re: Passing html code for table using elog command, posted by Andreas Luedeke on Mon May 26 09:55:06 2014
|
Remington Tyler Thornton wrote: |
Hey,
I am testing out automated entries using elog on the command line. The file I pass has html code for a table; the resulting entry shows the html code for the table instead of generating the table. Is there a way to make elog parse the code to show a formatted table?
Thanks in advance.
|
⇄
English (auto-detected) » English
The elog command has the option "-n <n>" to tell elog, what type of text it should expect.
[-n 0|1|2] Encoding: 0:ELcode,1:plain,2:HTML
⇄
English (auto-detected) » English
You'll find it explained in the documentation https://midas.psi.ch/elog/userguide.html#misc
It is necessary for elog to know the type of encoding, otherwise it would not show non-html content correctly. |
A couple of observations, posted by David Pilgram on Fri Mar 28 14:29:24 2014
|
Hi Stefan and Andreas,
When I submitted the previous entry, I had an error message about not able to send via psxxxx.psi.ch come up as
a red bar at the top of the elog page - sorry, cannot remember the subdomain name correctly.
The observations I was going to make is firstly the change in layout of the Find section - maybe I'll get used
to it but the change in layout wasn't warmly welcomed.
Also, shame that moving from Subversion means that the increments are no longer in easy numerical order. So I
believe that I am commenting on the latest possible version available, a738232.
A question. My logbooks directory is now 1.8GB. Yes, there are a lot of attachments etc to bulk it out, but
it's all plain text comments. Is there a limit as to the size, or total number of entries? Elog takes a
notible amount of time to index it all these days, and I have wondered whether a couple of "instabilities" might
be caused by this. Anyone any thoughts?
I don't know how I managed it, but I got elog to generate two entries with the identical ID no. The new entries
were different as well. The log file faithfully had recorded the two separate replies to the entry having the
same ID no as well. Unfortunately I went and corrected it by editing the YYMMDDa.log file without keeping a
copy. I have also had a mysterious entry ID0 appear in threaded display, despite there being no entry 0; and if
it appears, it appears in two or three places within the list of threaded entries. |
Re: A couple of observations, posted by David Pilgram on Fri Mar 28 14:55:16 2014
|
I tried to attach a screenshot showing this, but kept getting a 502 bad gateway error.
The message in the red banner is
Error sending Email via <i>"psquad.psi.ch"</i>
with that html showing, by the way.
> Hi Stefan and Andreas,
>
> When I submitted the previous entry, I had an error message about not able to send via psxxxx.psi.ch come up as
> a red bar at the top of the elog page - sorry, cannot remember the subdomain name correctly.
>
> The observations I was going to make is firstly the change in layout of the Find section - maybe I'll get used
> to it but the change in layout wasn't warmly welcomed.
>
> Also, shame that moving from Subversion means that the increments are no longer in easy numerical order. So I
> believe that I am commenting on the latest possible version available, a738232.
>
> A question. My logbooks directory is now 1.8GB. Yes, there are a lot of attachments etc to bulk it out, but
> it's all plain text comments. Is there a limit as to the size, or total number of entries? Elog takes a
> notible amount of time to index it all these days, and I have wondered whether a couple of "instabilities" might
> be caused by this. Anyone any thoughts?
>
> I don't know how I managed it, but I got elog to generate two entries with the identical ID no. The new entries
> were different as well. The log file faithfully had recorded the two separate replies to the entry having the
> same ID no as well. Unfortunately I went and corrected it by editing the YYMMDDa.log file without keeping a
> copy. I have also had a mysterious entry ID0 appear in threaded display, despite there being no entry 0; and if
> it appears, it appears in two or three places within the list of threaded entries. |
Generation of .png files for attachments, posted by David Pilgram on Fri Mar 28 14:15:18 2014
|
Hi Stefan and Andreas,
With the latest incremental version of elog (a738232), I have noticed that when attaching a pdf file, the
.png thumbnail is not generated when the "upload" button is pressed - there is just the usual small line saying
what the latest attachment is. If this happens, a subsequent attachment will force the generation of the
thumbnail for the *previous* attachment, and again no thumbnail for the latest attachment.
Submitting the comment will also generate the thumbnail.
As of yet, I cannot find any consistent pattern to this. Also, it's hardly a disaster, but I have been fooled
when attaching a pdf file that subsequently turned out to be damaged and thus unreadable. |
Problem with ELOG, posted by Markus Grosse-Kock on Thu Mar 13 11:34:58 2014
|
Hi,
we have a problem. After windows updates, the elog service doesn´t start:


What can we do?
Best regards,
Markus |
Re: Problem with ELOG, posted by Markus Grosse-Kock on Thu Mar 13 12:39:41 2014
|
Markus Grosse-Kock wrote: |
Hi,
we have a problem. After windows updates, the elog service doesn´t start:


What can we do?
Best regards,
Markus
|
After I uninstalled the software and reinstalled, the function is working again.
Thanks.
Best regards,
Markus |
XML import Error, posted by Donald on Thu Feb 27 15:15:55 2014
|
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 |
Re: XML import Error, posted by Andreas Luedeke on Mon Mar 3 15:42:29 2014
|
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. |
Re: XML import Error, posted by Donald on Tue Mar 4 19:48:02 2014
|
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?
|
Re: XML import Error, posted by Donald on Tue Mar 11 15:17:36 2014
|
Donald wrote: |
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?
|
Anyone have any luck reproducing the error? or have suggestions on how to fix it? |
Author drop-down menu length, posted by Kay Graf on Mon Mar 10 12:15:07 2014
|
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. |
Re: Author drop-down menu length, posted by Andreas Luedeke on Mon Mar 10 15:18:51 2014
|
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 |
Re: Author drop-down menu length, posted by Kay Graf on Tue Mar 11 09:19:06 2014
|
Andreas Luedeke wrote: |
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
|
Hello Andreas,
thanks a lot for your quick reply - both options are valid and working. For simplicity (the author list is generated automatically from a shell script) I opted for the first one.
Best regards,
Kay
|
How to upload several images at once, posted by Alejandro Gomez on Wed Mar 5 03:58:51 2014
|
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!! |
Re: How to upload several images at once, posted by Stefan Ritt on Wed Mar 5 07:53:01 2014
|
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 |
Google Places API AutoComplete, posted by Garret Delaronde on Fri Apr 26 19:00:07 2013
|
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? :) |
Re: Google Places API AutoComplete, posted by Stefan Ritt on Fri Feb 21 13:43:03 2014
|
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
|
|