| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67680
|
Fri Mar 28 14:15:18 2014 |
 | David Pilgram | David.Pilgram@epost.org.uk | Comment | Linux | 2.9.2-a738 | Generation of .png files for attachments | Hi Stefan and Andreas,
With the latest incremental version of elog (a738232), I have noticed that when attaching a pdf file, the
.png thumbnail is not generated when the "upload" button is pressed - there is just the usual small line saying
what the latest attachment is. If this happens, a subsequent attachment will force the generation of the
thumbnail for the *previous* attachment, and again no thumbnail for the latest attachment.
Submitting the comment will also generate the thumbnail.
As of yet, I cannot find any consistent pattern to this. Also, it's hardly a disaster, but I have been fooled
when attaching a pdf file that subsequently turned out to be damaged and thus unreadable. |
|
67823
|
Sun Mar 15 16:41:49 2015 |
 | David Pilgram | David.Pilgram@epost.org.uk | Comment | All | - | Re: Configure default time range in 'Find' | Hi Stefan,
There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time". I archive many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results. And it gets annoying that the default default is "Day", the number of times I've forgotten...
I got around this by allowing a "Show last default = 0", modifying the relevent line in the block of code you modified when this was introduced to make this select "i==0", and that did the trick.
| Stefan Ritt wrote: |
|
I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT repository. If you cannot recompile the code yourself, you have to wait for the next release.
| David Pilgram wrote: |
|
By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly. I trust that is what you're after, Eoin. I'll keep my change to the coding, but that's personal choice.
|
|
|
|
67824
|
Sun Mar 15 17:53:44 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Comment | All | - | Re: Configure default time range in 'Find' | Law of unintended consequences came into play. If you use 0, then on the results page it says "Restricted search to last 0 Days". So that also needs tweeking, and that's really put my c coding (or lack of it) to the test. But I've changed that phrase to "Unrestricted search" followed by blank for when the parameter "last" is 0.
Oh, and a typo, "seach" instead of "search".
No doubt other features will show up...
| David Pilgram wrote: |
|
Hi Stefan,
There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time". I archive many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results. And it gets annoying that the default default is "Day", the number of times I've forgotten...
I got around this by allowing a "Show last default = 0", modifying the relevent line in the block of code you modified when this was introduced to make this select "i==0", and that did the trick.
| Stefan Ritt wrote: |
|
I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT repository. If you cannot recompile the code yourself, you have to wait for the next release.
| David Pilgram wrote: |
|
By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly. I trust that is what you're after, Eoin. I'll keep my change to the coding, but that's personal choice.
|
|
|
|
|
67825
|
Mon Mar 16 07:16:56 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Comment | All | - | Re: Configure default time range in 'Find' | Hi David,
isn't the empty string "" doing already exactly what you want to achieve with "Show last all time"?
It is at least in my logbook.
Cheers
Andreas
| David Pilgram wrote: |
|
Hi Stefan,
There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time". I archive many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results. And it gets annoying that the default default is "Day", the number of times I've forgotten...
I got around this by allowing a "Show last default = 0", modifying the relevent line in the block of code you modified when this was introduced to make this select "i==0", and that did the trick.
| Stefan Ritt wrote: |
|
I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT repository. If you cannot recompile the code yourself, you have to wait for the next release.
| David Pilgram wrote: |
|
By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly. I trust that is what you're after, Eoin. I'll keep my change to the coding, but that's personal choice.
|
|
|
|
|
67826
|
Mon Mar 16 13:51:11 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Comment | All | - | Re: Configure default time range in 'Find' | Hi Andreas,
Yes, the empty string does exactly that, in the drop down menu, but before my changes, I could not set it to be the default setting in the configuration file. In an archived logbook, it's perfectly possible for "all time" to be the only sensible value. I tried "Show last default = " and various other variants, with no success in getting what I actually required. Also, in the documentation, there was no mention of a way to set the default as "all time", just a list of number of days (week (7), month (31), year (364) etc), which also led me to believe that it was not possible with the existing code.
I've sent an email to Stefan giving my coding changes for information.
| Andreas Luedeke wrote: |
|
Hi David,
isn't the empty string "" doing already exactly what you want to achieve with "Show last all time"?
It is at least in my logbook.
Cheers
Andreas
| David Pilgram wrote: |
|
Hi Stefan,
There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time". I archive many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results. And it gets annoying that the default default is "Day", the number of times I've forgotten...
I got around this by allowing a "Show last default = 0", modifying the relevent line in the block of code you modified when this was introduced to make this select "i==0", and that did the trick.
| Stefan Ritt wrote: |
|
I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT repository. If you cannot recompile the code yourself, you have to wait for the next release.
| David Pilgram wrote: |
|
By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly. I trust that is what you're after, Eoin. I'll keep my change to the coding, but that's personal choice.
|
|
|
|
|
|
67827
|
Tue Mar 17 07:04:44 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Comment | All | - | Re: Configure default time range in 'Find' | Hi David,
I was confused because one normally does not need to include a line in the configuration to set a default value. A default is exactly what you get if you don't specify anything in the configuration  But I think I've figured it out: you were overriding the default in the global section for all logbooks and wanted to get back to the default for a particular logbook.
Then another simple solution would have been to remove the line in the global section and add it just in those logbook configurations, where you actually need it.
Anyway, it is good that one can now set the default in the configuration; I agree that this should always be possible.
Cheers
Andreas
| David Pilgram wrote: |
|
Hi Andreas,
Yes, the empty string does exactly that, in the drop down menu, but before my changes, I could not set it to be the default setting in the configuration file. In an archived logbook, it's perfectly possible for "all time" to be the only sensible value. I tried "Show last default = " and various other variants, with no success in getting what I actually required. Also, in the documentation, there was no mention of a way to set the default as "all time", just a list of number of days (week (7), month (31), year (364) etc), which also led me to believe that it was not possible with the existing code.
I've sent an email to Stefan giving my coding changes for information.
| Andreas Luedeke wrote: |
|
Hi David,
isn't the empty string "" doing already exactly what you want to achieve with "Show last all time"?
It is at least in my logbook.
Cheers
Andreas
| David Pilgram wrote: |
|
Hi Stefan,
There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time". I archive many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results. And it gets annoying that the default default is "Day", the number of times I've forgotten...
I got around this by allowing a "Show last default = 0", modifying the relevent line in the block of code you modified when this was introduced to make this select "i==0", and that did the trick.
| Stefan Ritt wrote: |
|
I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT repository. If you cannot recompile the code yourself, you have to wait for the next release.
| David Pilgram wrote: |
|
By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly. I trust that is what you're after, Eoin. I'll keep my change to the coding, but that's personal choice.
|
|
|
|
|
|
|
67835
|
Tue Mar 24 15:49:28 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Comment | All | - | Re: Configure default time range in 'Find' | Show last default = 0
always worked, even in my original code. It was just not documented. I added that.
| Andreas Luedeke wrote: |
|
Hi David,
I was confused because one normally does not need to include a line in the configuration to set a default value. A default is exactly what you get if you don't specify anything in the configuration But I think I've figured it out: you were overriding the default in the global section for all logbooks and wanted to get back to the default for a particular logbook.
Then another simple solution would have been to remove the line in the global section and add it just in those logbook configurations, where you actually need it.
Anyway, it is good that one can now set the default in the configuration; I agree that this should always be possible.
Cheers
Andreas
| David Pilgram wrote: |
|
Hi Andreas,
Yes, the empty string does exactly that, in the drop down menu, but before my changes, I could not set it to be the default setting in the configuration file. In an archived logbook, it's perfectly possible for "all time" to be the only sensible value. I tried "Show last default = " and various other variants, with no success in getting what I actually required. Also, in the documentation, there was no mention of a way to set the default as "all time", just a list of number of days (week (7), month (31), year (364) etc), which also led me to believe that it was not possible with the existing code.
I've sent an email to Stefan giving my coding changes for information.
|
|
|
|
67883
|
Wed May 6 12:31:04 2015 |
 | Christof Hanke | hanke@rzg.mpg.de | Comment | All | 3.1.0 | Documentation of the webserver authentication | Hi Stefan,
here is a draft of how you could describe the webserver authentication in your docs.
T/Christof |
| Attachment 1: webserver_auth_doc.patch
|
diff --git a/doc/adminguide.html b/doc/adminguide.html
index da25388..0568ae3 100755
--- a/doc/adminguide.html
+++ b/doc/adminguide.html
@@ -243,6 +243,37 @@ URL = http://your.proxy.host/subdir/
into elogd.cfg.<p>
+<h3><hr><i>Using apache authentication:</i></h3>
+It is also possible to login via an apache-auth module.
+In elogd.cfg you should use the keyword "Webserver" for Authentication:
+
+<ul><pre>
+Authentication = Webserver
+</pre></ul>
+This triggers elogd to use the environment variable "X-Forwarded-User" as the logged in user.
+A simple example of a apache configuration (including the proxy) is :
+<ul><pre>
+# this required to pass on the generated env-variable X-Forwarded-User to the proxy
+ProxyPassInterpolateEnv On
+
+ProxyPass /elog/ http://your.host.domain:8080/
+
+<Location "/elog">
+ Order allow,deny
+ Allow from all
+ AuthType Basic
+ AuthName "elog-server"
+ AuthUserFile "/opt/elog/htpasswd"
+ require valid-user
+ RequestHeader unset Authorization
+ RequestHeader add X-Forwarded-User %{REMOTE_USER}s
+ # elog doesn't like the '@', so we need to cut it
+ RequestHeader edit X-Forwarded-User "@(.*)$" ""
+</Location>
+</pre></ul>
+
+
+
<hr><a name="imagemagick"> <div class=section> Installing ImageMagick </div> <p>
When images are attached to ELOG entries, thumbnails can be created for quick preview.
This works also for PDF and PostScript files. ELOG forwards any image operation
diff --git a/doc/config.html b/doc/config.html
index 9848f58..9e98855 100755
--- a/doc/config.html
+++ b/doc/config.html
@@ -2207,6 +2207,22 @@ Options Location = Main Building{a}, New Building{b}, Old Building{c}
you have to change your password by other means (such as via the Windows
login if you use a Windows Domain).
</p>
+ <p>
+ Beside the Kerberos authentication, elogd version 3.0 and higher can be configured to accept a authentication done
+ by the webserver.
+ <ul>
+ <li>
+ <b><code>Authentication = Webserver</code></b>
+ </li>
+ </ul>
+ </p>
+ <p>
+ You can also combine it with other authentication methods as shown for Kerberos.
+ </p>
+ <p>
+ Elogd is then accepting the username set in the Request-Header "X-Forwarded-User" as already logged in.<br/>
+ To make this work, you need to configure the webserver correctly, as describe in the adminguide.
+ </p>
<p>
<a name="email" id="email"></a>
|
|