support "authentication = webserver, kerberos", posted by Devin Bougie on Wed May 18 16:19:07 2016
|
The elog client binary does not work with webserver authentication. One fix would be to support both webserver and kerberos authentication (authentication
= webserver, kerberos), similar to how you currently support
"authentication = kerberos, file".
|
elog client binary with webserver authentication, posted by Devin Bougie on Wed May 11 02:59:53 2016
|
Is it possible to submit entries using the elog client binary when the server is configured with webserver authentication (when the server requires the
X-Forwarded-User header)? One option would be if the server could support both webserver and kerberos (or even file) authentication, but neither
"Authentication = Webserver, Kerberos" nor "Authentication = Webserver, File" seem to work.
|
|
Merge duplicate types, posted by John Mund on Fri May 6 16:19:10 2016
|
Hello,
We have accumulated some duplicate 'types' in one of our logbooks. Is it possible to merge them?
Thanks, |
Re: Merge duplicate types, posted by Andreas Luedeke on Fri May 6 22:30:56 2016
|
I'm not sure I understand your question correctly.
If you want to remove options from an extendable option attribute, then you can just edit the logbook configuration file.
John |
|
Trouble with Find and Conditional attributes, posted by Adam Fairbrother on Thu Apr 28 22:38:00 2016
|
I seem to be having some trouble with Find when using conditional attributes.
when I change the primary attribute in the find field, the corrispnding secondary attribute dosn't refresh properly with the list of values.
I am able to use the conditional options as expected when creating a new logbook. |
|
Re: Trouble with Find and Conditional attributes, posted by Adam Fairbrother on Thu Apr 28 22:54:08 2016
|
This may be due to how I have my config file setup
Example:
Attributes = A, B |
|
Re: Trouble with Find and Conditional attributes, posted by Adam Fairbrother on Fri Apr 29 20:37:04 2016
|
Uppon closer inspection, removing the option to preset the secondary attribute as a Option list dosn't do anything for the find page.
This:
Attributes = A, B |
|
How to delete a logbook?, posted by steve bray on Thu Apr 28 16:45:41 2016
|
Hello,
What is the procedure to delete a logbook (incl. attachments)?
|
|
Re: How to delete a logbook?, posted by Stefan Ritt on Fri Apr 29 11:45:51 2016
|
Deleting a logbook in the config page (via "Delete this logbook") only removes the logbook defiition from the config file. To really erase
all information you have to go to the file system and delete the whole directory belonging to that logbook. You have one subdirectory per year, containing
all logobok entries and also attachments, so make sure you do a recursiver directory removal. |
|
Re: How to delete a logbook?, posted by steve bray on Fri Apr 29 13:36:49 2016
|
Stefan,
Thank you that is exactly what I needed to know.
Steve |
|
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
|
|
Re: How to enforce line breaks in plain text entries?, posted by Andreas Luedeke on Wed Apr 27 14:15:19 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
|
|
Re: How to enforce line breaks in plain text entries?, posted by Andreas Luedeke on Wed Apr 27 14:36:42 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
|
|
Re: How to enforce line breaks in plain text entries?, posted by Stefan Ritt on Wed Apr 27 14:39:28 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
|
|
How to login and export to CSV using wget?, posted by Alan Grant on Sun Apr 24 02:09:47 2016
|
Is it possible to use wget to log into elog and export all of a logbook's data into a CSV file?
I can accomplish this perfectly when authentication IS NOT required by using: wget --no-check-certificate -O e:\export.csv http://localhost:8080/demo/?mode=CSV1
However, I cannot accomplish it when authentication IS required by using: wget --no-check-certificate -O e:\export.csv "http://localhost:8080/demo/?mode=CSV1&uname=agrant&upassword=skipper" |
|
Re: How to login and export to CSV using wget?, posted by Alan Grant on Sun Apr 24 06:49:33 2016
|
UPDATE:
After days of head banging and trying different syntax combinations, I finally stumbled on my own answer. It involved some syntax adjustments,
and then splitting the task into these two consecutive operations: |
|
Send email based on lookup of an attribute, posted by Rudy Taraschi on Thu Mar 31 16:31:45 2016
|
I'm trying to send an email based on an attribute, in other words, a lookup and not $user_email of the author.
For instance, if I set a an attribute "Assignee" with a valid user full name (i.e. John Smith), I'd like to look up John Smith's
|
|
Re: Send email based on lookup of an attribute, posted by Stefan Ritt on Mon Apr 4 14:09:42 2016
|
> I'm trying to send an email based on an attribute, in other words, a lookup and not $user_email of the author.
>
> For instance, if I set a an attribute "Assignee" with a valid user full name (i.e. John Smith), I'd like to look up John Smith's
|