Re: Columns numeric input are added/computed, posted by Stefan Ritt on Fri Oct 23 08:29:33 2015
|
No, formulas are not yet implemented. For such things I would use Google Spreadsheets in meantime.
Stefan
| Dawang wrote: |
|
Hi Stefan,
Good day. I'm thinking if this wishlist is already available in elog. The values in columns we're added or computed according to formula set in a single separate column.
Thanks,
Raymund
|
|
Sample of actual elog Config with URL in SSL, posted by Dawang on Mon Dec 14 04:42:04 2015
|
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund |
|
Re: Sample of actual elog Config with URL in SSL, posted by Andreas Luedeke on Wed Dec 16 09:56:09 2015
|
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
| Dawang wrote: |
|
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
Prefill attributes for new post, posted by Johan Forsberg on Tue Jan 12 11:35:55 2016
|
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 |
|
Re: Prefill attributes for new post, posted by Andreas Luedeke on Tue Jan 12 11:48:57 2016
|
Hi Johan,
yes, it is possible. And you were actually very close :-)
In order to pass preset-parameters within a URL, you just need to prefix the fieldname with a "p". In your example, you would write "...&pSubsystems=Vacuum".
Here is an example for the Linux Demo logbook:
https://midas.psi.ch/elogs/Linux+Demo/?cmd=New&pAuthor=Santa+Claus&pSubject=Christmas+Presents&pType=Problem+Fixed&pCategory=Hardware
This feature is even already documented: https://midas.psi.ch/elog/userguide.html#misc :-)
I wish you a Happy New Year!
Andreas
| Johan Forsberg wrote: |
|
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
|
|
|
Re: Prefill attributes for new post, posted by Stefan Ritt on Tue Jan 12 11:50:22 2016
|
Put a "p" in front of the attribute, like "&pSubsystem=Vacuum". This is kind of an undocumented feature just for the experts ;-)
| Johan Forsberg wrote: |
|
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
|
|
|
Re: Prefill attributes for new post, posted by Johan Forsberg on Tue Jan 12 14:05:55 2016
|
Wow, than you both for the quick response! I agree it's quite a hidden gem, but the most important thing is that it works, thanks!
| Stefan Ritt wrote: |
|
Put a "p" in front of the attribute, like "&pSubsystem=Vacuum". This is kind of an undocumented feature just for the experts ;-)
| Johan Forsberg wrote: |
|
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
|
|
|
How to enforce line breaks in plain text entries?, posted by Andreas Luedeke on Wed Apr 27 14:07:52 2016
|
We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
entries made during the shift and files the printouts. If one entry in the shift was plain text without
appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the width
of this line and either the printout is cut off at the right side, or the whole content is scaled down to very
tiny scale, which makes it unreadable.
Is there a way to enforce line breaks in plain text entries? |
|