Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 195 of 801  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6404 Entries 
Goto page Previous  1, 2, 3 ... 194, 195, 196 ... 799, 800, 801   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subject
  68219   Tue Jan 12 17:38:52 2016 Question Devin Bougiedevin.bougie@cornell.eduBug reportLinux3.1.1drag and drop attachments not working with web server authentication
Hello, The "Drop attachments here..." section does not work when using Webserver authentication. Both elog 3.1.1 (the binary RPM) and apache are running on EL6.6 and are configured according to the docs. Authentication works fine and the normal "Choose File - Upload" attachment table works fine. However, when dragging an attachment to the "Drop attachments here..." section the dashes on the border turn green but when dropping the attachment nothing happens. If we revert to File authentication, everything works fine. I don't see any errors in our elog or apache log files. Any suggestions would be greatly appreciated. Many thanks, Devin
  68218   Tue Jan 12 16:10:34 2016 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxELOG V3.1.0-241Re: Monitoring a logbook for changes

Use automatic email notifications or RSS feeds. Read the manual for that.

Stefan

Johan Forsberg wrote:

Hi again!

I've another need that you probably already thought of :)

I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).

Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.

Cheers,

Johan

 

  68217   Tue Jan 12 15:06:42 2016 Idea Johan Forsbergjohan.forsberg@maxlab.lu.seQuestionLinuxELOG V3.1.0-241Monitoring a logbook for changes

Hi again!

I've another need that you probably already thought of :)

I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).

Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.

Cheers,

Johan

  68216   Tue Jan 12 14:05:55 2016 Reply Johan Forsbergjohan.forsberg@maxlab.lu.seRequestLinuxV3.1.0-2411f95Re: Prefill attributes for new post

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

 

 

  68215   Tue Jan 12 11:50:22 2016 Reply Stefan Rittstefan.ritt@psi.chRequestLinuxV3.1.0-2411f95Re: Prefill attributes for new post

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

 

  68214   Tue Jan 12 11:48:57 2016 Idea Andreas Luedekeandreas.luedeke@psi.chRequestLinuxV3.1.0-2411f95Re: Prefill attributes for new post
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

 

  68213   Tue Jan 12 11:35:55 2016 Idea Johan Forsbergjohan.forsberg@maxlab.lu.seRequestLinuxV3.1.0-2411f95Prefill attributes for new post

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

  68211   Wed Dec 16 09:56:09 2015 Reply Andreas Luedekeandreas.luedeke@psi.chRequestWindowsLatestRe: Sample of actual elog Config with URL in SSL

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

 

Goto page Previous  1, 2, 3 ... 194, 195, 196 ... 799, 800, 801   Next  
ELOG V3.1.5-3fb85fa6