Hi Stefan,

I'm having a problem with 'Preset Text' now behaving differently in the latest release (2.9.1)?
My config file for example has always had: 'Preset Text = This is a test.', previously 'This is a test' was put
verbatim into the text area, now it seems to think whatever follows 'Preset Text =' is always a file and I end
up with 'File <i> This is a test. <i> cannot be found'?

I did notice a 'Print warning if "preset text" file cannot be found' line in the latest release notes, does this
now mean wherever I have used the method above I will now need to make a text file to match?

I'm using them embedded in conditional attributes if that makes any difference?

Thanks for your help.

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

Title says all :)

Is it possible to preload Options or Moptions from a text file or CSV instead of being load from the elogd.conf ?

Thanks :)

Hi all,

I have a use case for ELOG where I need to be able to "prefill" some attributes in the "cmd=new" form, based on the URL.

To illustrate, imagine a link that takes the user directly to the form for creating a new post, with the "Subsystem" attribute already filled out to "Vacuum".

Is this possible already? I've tried naively using URL parameters (e.g. "&Subsystem=Vacuum") but that does not work. If it's not implemented, I think it would be a useful feature to have (and quite important for my particular use case). I could create a new post first using the "elog" tool, with the desired attributes set, but it makes more sense to defer the actual creation of the post to the user, i.e. he/she might change their mind before pressing "submit".

Thanks,

Johan Forsberg, MAX IV Laboratory, Sweden

Hi,

Is it possible to pre-populate a field based on the selection of another field. I like to have the Equipment Description field populated when the use makes a selection on the EQ# field.

Thank you,

Jimmy