Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 672 of 807  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  67654   Thu Jan 16 19:11:58 2014 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.2-2455Re: Subject attribute in bold type - threaded display

Paolo wrote:
Hi all,
I am successfully using ELOG V2.9.2-2455 to manage several laboratory logs.
I am looking for a way, if possible, to format the subject attribute in bold type while in thread display.
I've used the following code
Display Subject = <b>$subject</b>
with no success, then I've tried
Subst Subject = <b>$subject</b>
again with no success. It seems that the <b> tag is not iterpreted.
Have you any suggestion about this?
Thank you in advance.
Paolo

 
English (auto-detected) » English
 
T
Hi Paolo,
you've made two little errors, one is partly driven by a bug in the documentation:

1st: If you want to use HTML tags in the display of attributes, you need to add "Allow HTML = 1" in the configuration.

2nd: The proper command is not "Display <attribute> = ..." but "Change <attribute> = ...". It is actually correct in the documentation (Change <attribute> = <string>), but the example is wrong (Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>)

Stefan should fix the example in https://midas.psi.ch/elog/config.html#attrib some day.

Cheers
Andreas

 

  67670   Mon Mar 3 15:42:29 2014 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows2.9.2-2475Re: 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.

  67675   Mon Mar 10 15:18:51 2014 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.2-2455Re: 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

  67687   Mon May 26 09:55:06 2014 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.8.1-2350Re: Passing html code for table using elog command

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.

  67693   Sat Aug 2 06:59:22 2014 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindowsElog V2.9.Re: Elog and Certs

Chuck Brost wrote:

Elog V2.9.1-2435 if it matters. 

It is time again to install the certs for SSL in Elog, and the standard openssl command line does not seem to produce the files that I need in order to get it working on my system.

I copied the file to my trusty linux server and ran the command "openssl pkcs12 -in cert.p12 -clcerts -out cert.pem " as I did last time, last time I got a nice little .crt and .key file.. this time.. no such luck.. I can get by with the guys just hitting the continue and go past the expired cert notice for a bit.. but if I cannot fix it reasonably soon.. well, it won't be pretty for me.. <grin>

Any ideas that anyone can give will be appreciated.. this is a bit outside my usual duties around here..

I'm not an expert in this field, but I think openssl is not meant to create a certificate for you, it is meant to create a certificate request form (CSR) and then you buy the certificate with that form from a vendor. Once you have the certificate then you just need to copy it to the right place for ELOG (or Apache) to use it, you don't need openssl for that.

 
English (auto-detected) » English
 

You can have a look at: http://www.rackspace.com/knowledge_center/article/generate-a-csr-with-openssl

Good luck!

 

PS: This is of course an openssl question: another forum could may be more helpful?

  67695   Sat Aug 9 06:40:35 2014 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.7.5-2185Re: Preset Text

mike cianci wrote:

Sorry for the novice question, but can anyone tell me where the ".txt" document is suppose to reside for the "Preset text" statement to find it? I have a "test.txt" document in the "Template" file but all "Preset text = test.txt" does is print "test.txt" in the comment section.

Thanks,  Mike

I always chose the safe solution: I provide the full path to the document. For example (under Linux):

Preset text = /usr/local/elog/logbooks/inc/test.txt

 
English (auto-detected) » English
 
 
English (auto-detected) » English
 
  67698   Sun Aug 24 15:06:37 2014 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows2.7.5 Re: Preset Text

mike cianci wrote:

I have stripped my config file down to one command:   "Preset text = \\ssoelog\elog\templates\test2.txt"

If I type the path "\\ssoelog\elog\templates\test2.txt" into my browser I see the contents of the file, which is the word  "YES"

But when I open a "New" page in ELOG the command returns:    " \\ssoelog\elog\templates\test2.txt"

Could it have anything to do with the fact that I am using Version 2.7.5

Well, I only know that the following config file works fine for me on Linux:

 
English (auto-detected) » English
 

[test]
Attributes = xx
Preset text = /tmp/xx

with the file /tmp/xx containing "test: ignore". When opening a new entry, then the text "test: ignore" is written in the editors text area.

I'm using Version 2.9.2

My suggestion: download the latest Windows Version and try again.

  67705   Wed Sep 17 17:45:18 2014 Idea Andreas Luedekeandreas.luedeke@psi.chInfoAll V2.9.2-24Re: Sort by date prior to 2002

Chris Jennings wrote:

Chris Jennings wrote:

I have an attribute formatted as a date (but not labeled as date) and is sorted as second priority. The sort works fine until I enter a date older than Jan 1st 2002. When I do this it is sorted as the latest. Is this a bug or simply not designed to use dates this old?

Thanks in advance,

Chris

 Sorry, my mistake. The cutoff date is anything before September 9th 2001 does not sort.

I think I remember that this has been discussed earlier: it is a little bug in elogd.
You can see where it comes from if you type in the little command 'date -d "9-Sep-2001 3:46:40" +%s'
Converted to "seconds of the epoche" (seconds since 1970-01-01 00:00:00 UTC) the date "9-Sep-2001 3:46:40" has one digit more than "9-Sep-2001 3:46:39".
Since elog makes a string comparison, suddenly 1'000'000'000 is less than 999'999'999; therefore the wrong sorting.

Workaround: you can modify your old entries and add a leading zero to all entries where your specific date field starts with a '9'.

Stefan: you should fix it at least well before 20-Nov-2286 18:46:40, when the same bug strikes again!
ELOG V3.1.5-3fb85fa6