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

[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.

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

 for what it is worth, if anyone else is doing this.. try

openssl pkcs12 -in file.pkx -nodes -out file.pem

I have what I need and all is well!

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

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'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.

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?

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..