ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 268 of 807

Not logged in

Find | Login | Help

New entries since:

Thu Jan 1 01:00:00 1970

Full | Summary | Threaded | Hide attachments

6451 Entries

Goto page Previous 1, 2, 3 ... 267, 268, 269 ... 805, 806, 807 Next

Mon Mar 10 12:15:07 2014

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

Re: How to upload several images at once

Alejandro Gomez wrote:

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

How to upload several images at once

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

Andreas Luedeke wrote:

Donald wrote:

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

Donald wrote:

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:

Hi Donald,

yes, the import function gave me some headache in the past, too.

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

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:

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

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

67667

Fri Feb 21 13:25:55 2014

Re: Export entries to XLS or CSV?

Andreas Luedeke wrote:

Jim Tinlin wrote:

Stefan Ritt wrote:

Andreas Luedeke wrote:

Yes, you're right: the text field is only exported in XML and Raw mode.

It is questionable how EXCEL should cope with HTML or ELCode output from the text fields.

But I admit that this would be a useful feature for logbooks that only use plain text entries. And it is simple to implement.

I've attached a patch to elogd.c from elog-2.9.2-2081 that adds a third CVS mode 'CSV (";" separated) + Text'.

(This string has not yet been added to the localization.)

As far as I've tested it works fine to import the text to OpenOffice and EXCEL, even with multiple text lines and HTML code in the text.

Of course the spreadsheet programs just display the HTML source.

Stefan, do you think this should be added to the official branch?

⇄

Detect language » English

⇄

Detect language » English

Hi Jim, can you confirm that this works for you? If so, I'm willing to incorporate the patch into the distribution.

Has this been added yet?

I don't have the means to create an executable for Windows, if someone does I can give it a try...it sounds/looks like it will work.

Thanks!

Hi Jim, I've incorporated the patch to our production server about a week ago.

I've agreed with Stefan that he'll add it, when it proved to run stable for a while.

Until now it appears to work fine. I think Stefan will add it to the distribution soon.

But I won't touch any Windows systems, you'll need to wait for someone else to compile it for you.

Maybe some skilled Windows user want to give it a try: i've attached the changes in the elogd.c file from v2.9.2-2481,

the modified file can be currently downloaded from http://people.web.psi.ch/luedeke/public/tmp/elogd.c

⇄

Detect language » English

Andreas

⇄

Detect language » English

⇄

Detect language » English

⇄

Detect language » English

This patch is now officially in the GIT repository.

Goto page Previous 1, 2, 3 ... 267, 268, 269 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6