Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 237 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  69347   Mon Apr 12 14:17:52 2021 Reply Gys Wuytsgys.wuyts@gmail.comQuestionWindows3.1.4 (latest)Re: auto pre-fill fields issue

Super, overlooked that one. Works now

 

g

Stefan Ritt wrote:

"Subst xxx" replaces after you submit an entry, while "Preset xxx" replaces before you create an entry. I believe you want the second one.

Stefan

Gys Wuyts wrote:

[global]

port = 8080

ssl = 0

Password file = passwords.txt

Admin user = user1

SMTP host = smtp. mail.com

SMTP port = 25

SMTP username = user1@mail.com

SMTP Password = GIwbx7UbmkWs5J0P8lVztX7Anje0/21BU/Tmk0aPm.

Logfile = ELog_log.txt

Logging level = 3

 

 

[Server]

Logbook dir = Server

Theme = default

Comment = Server Change Log

Attributes = Author, Email, Type, Category, Subject

Subst Author = $long_name from $remote_host

Subst Email = $user_email

Options Type = SRV 1, SRV 2, SRV Sup, BMS content, BMS setpoints, BMS new

Options Category = Config, User, Access, Connection, Change, New, Delete

Extendable Options =

Required Attributes = Author, Type

Page Title = ELOG - $subject

Reverse sort = 1

Quick filter = Date, Type

Andreas Luedeke wrote:

If you would post a minimal config file where the problem occurs, then we could look what the problem is.

Gys Wuyts wrote:

Thank you but that is already  in place. I have the same issue on both Windows 10 and Windows Server 2016 and 2019.

tnks

g

Stefan Ritt wrote:

You need user-level access control, using 

Password file = ...

Stefan

Gys Wuyts wrote:

Hello,

what are the pre-requisites to automatically fill the Author and Author Email fields. The documented method:

Subst Author = $long_name from $remote_host

Subst Email = $user_email

in the elogd.cfg file does not seem to work.

(I see it works here on this platform)

Tnks

 

G

 

 

 

 

 

 

  67252   Wed Apr 18 21:53:26 2012 Reply A. TuttleATuttle@UW.eduQuestionLinux2.9.1-2435Re: author field in reply
Look in https://midas.psi.ch/elog/config.html
--
Fun things to set are:
Preset on first reply <attribute> = <string>
and
Preset on reply <attribute> = <string>
  67288   Tue Jun 19 04:02:43 2012 Reply Ken Harveyrichard.harvey@l-3com.comQuestionLinux2.9.1-2435Re: author field in reply

A. Tuttle wrote:
Look in https://midas.psi.ch/elog/config.html
--
Fun things to set are:
Preset on first reply <attribute> = <string>
and
Preset on reply <attribute> = <string>


I am a newbie to being the administrator to ELog, but have used it for a while now. We just updated and have the same issue with the reply now. Unfortunatley I am not much of a programmer, yet, still learning. In our config file it has "Preset Name = $long_name", "Preset Author = $long_name", "Preset on reply Author = $long_name". By looking in the Syntax of elogd.cfg section, it seems to be correct, but I am not sure. Can you give me a suggestion on how it should look? Or tell me why it is not working and lead me in the right direction on how to correctly set it up? Thank you for your time.
  67290   Wed Jun 20 16:16:56 2012 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.1-2435Re: author field in reply

Ken Harvey wrote:

A. Tuttle wrote:
Look in https://midas.psi.ch/elog/config.html
--
Fun things to set are:
Preset on first reply <attribute> = <string>
and
Preset on reply <attribute> = <string>


I am a newbie to being the administrator to ELog, but have used it for a while now. We just updated and have the same issue with the reply now. Unfortunatley I am not much of a programmer, yet, still learning. In our config file it has "Preset Name = $long_name", "Preset Author = $long_name", "Preset on reply Author = $long_name". By looking in the Syntax of elogd.cfg section, it seems to be correct, but I am not sure. Can you give me a suggestion on how it should look? Or tell me why it is not working and lead me in the right direction on how to correctly set it up? Thank you for your time.


A common mistake is to think that "Author" is some kind of keyword: it is not.
You can use any defined attribute, if you want to use "Author" this attribute needs to be defined in the "Attributes=" command line.
Attributes = Author, ...
Then you can use the "Preset" command.
Preset Author = $long_name
Preset on reply Author = $long_name


I've just tested it with 2.9.0-2435 and it works fine.
If the following 4 line minimal logbook configuration does not work for 2.9.1, then please post again:
Attributes = Author
Preset Author = $long_name
Preset on reply Author = $long_name
Locked Attributes = Author

Cheers
Andreas
  67291   Thu Jun 21 05:29:59 2012 Reply Ken Harveyrichard.harvey@l-3com.comQuestionLinux2.9.1-2435Re: author field in reply

Andreas Luedeke wrote:

Ken Harvey wrote:

A. Tuttle wrote:
Look in https://midas.psi.ch/elog/config.html
--
Fun things to set are:
Preset on first reply <attribute> = <string>
and
Preset on reply <attribute> = <string>


I am a newbie to being the administrator to ELog, but have used it for a while now. We just updated and have the same issue with the reply now. Unfortunatley I am not much of a programmer, yet, still learning. In our config file it has "Preset Name = $long_name", "Preset Author = $long_name", "Preset on reply Author = $long_name". By looking in the Syntax of elogd.cfg section, it seems to be correct, but I am not sure. Can you give me a suggestion on how it should look? Or tell me why it is not working and lead me in the right direction on how to correctly set it up? Thank you for your time.


A common mistake is to think that "Author" is some kind of keyword: it is not.
You can use any defined attribute, if you want to use "Author" this attribute needs to be defined in the "Attributes=" command line.
Attributes = Author, ...
Then you can use the "Preset" command.
Preset Author = $long_name
Preset on reply Author = $long_name


I've just tested it with 2.9.0-2435 and it works fine.
If the following 4 line minimal logbook configuration does not work for 2.9.1, then please post again:
Attributes = Author
Preset Author = $long_name
Preset on reply Author = $long_name
Locked Attributes = Author

Cheers
Andreas


Thanks Andreas,

That cleared up a lot for me. With your information I was able to figure it out. I got rid of the Author and just went with Name, and now it all works good.

Again, thanks for your help,

Ken Harvey
  1352   Wed Jul 27 21:22:47 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.57-1Re: attribute of type "datetime" sorted incorrectly

Kees Bol wrote:
What goes wrong here?


The wrong sorting is a mystery to me. I redid what you have, and entered exactly the same entries, and got following:



As you can see, the sorting is quite different. What happens if you reload the page, what if you restart elogd?

As for the missing validity check for the date field, all what was missing was the year check. I added that.
  1357   Thu Jul 28 09:46:40 2005 Reply Kees Bolkees.bol@wur.nlQuestionLinux2.57-1Re: attribute of type "datetime" sorted incorrectly

Stefan Ritt wrote:

Kees Bol wrote:
What goes wrong here?


The wrong sorting is a mystery to me. I redid what you have, and entered exactly the same entries, and got following:



As you can see, the sorting is quite different. What happens if you reload the page, what if you restart elogd?

As for the missing validity check for the date field, all what was missing was the year check. I added that.


Stefan, I think it has something to do with version 2.57-1. Yesterday evening I installed V2.60 and there was a big difference. All entries of Logdate were changed in 1-jan-70 and when entering/editing an entry I now get the calendar and clock. So everything, including sorting, looks good now.

Thanks
  68246   Thu Jan 28 20:02:06 2016 Reply Devin Bougiedevin.bougie@cornell.eduBug reportLinux3.1.1Re: attachments created using "Image" button can not be clicked-on and do not appear in the attachment table.

As there appears to be some inconsistencies, I thought I'd document the behaviour of each of the attachment options.

------

1. Click on the "Image" button in the CKEditor, click on "Choose File" and browse to the file, click on "Send it to the Server", and click "OK".

  • The image appears inline at the configured "Thumbnail size", but it is not clickable and it does not appear in the attachment table when viewing the entry.

2. Drag and drop an image into the body of the message.

  • The image appears inline at the configured "Thumbnail size" and is clickable.  As with "1," however, it does not appear in the attachment table when viewing the entry.

3. Drag and drop an image into the "Drop attachments here ..." section.

  • The image appears in the attachment table at the configured Thumbnail Size, and is clickable.

4. From the attachment table, click on "Choose File" and then click on "Upload."

  • The image appears in the attachment table at the configured Thumbnail Size, and is clickable.

------

We need to make sure the images are always clickable so that you can always view the full-sized image.  Any suggestions for fixing this, short of reverting to v2.9.2, would be greatly appreciated.

Thanks again,

Devin

 

Devin Bougie wrote:

This has been confirmed usign the Demo forum on this server.  For example, please see https://midas.psi.ch/elogs/Linux+Demo/8

When an image is attached using the "Image" button in the CKEditor, that image does not appear in the attachment table for that entry.  In addition, the image can not be clicked on to view the full image.

This was not the case in v2.9.2, at least.

Is there some configuration option I could toggle to change this behaviour?  By default, we would like any attachment (whether it's made using drag and drop, the Image button, or the "Choose File" button) to appear in the attachment table *and* be clickable to view the full image.

Thanks,

Devin

 

ELOG V3.1.5-3fb85fa6