ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 24 of 806

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6444 Entries

Goto page Previous 1, 2, 3 ... 23, 24, 25 ... 804, 805, 806 Next

Thu Sep 22 11:34:46 2005

Conditional hiding of attributes in list view

Hi!

All here are amazed by how quickly this software has evolved since we
took our first look into the world of electronic logbooks.

In order to use it as our shift logbook, however, we have one request
which is in principle the same as that of Juliana Peng
(http://midas.psi.ch/elogs/Forum/1280). We want to have the usual
maintenance/admin/problem report entries of the shift crew in the
same logbook as the automatic entries from our runcontrol software to
clearly see cause and effect when analyzing the beamtimes later. Of
course, the run entries have different attributes than the shift crew
entries. So, it would be nice to have the conditional "Show attributes"
function extended also to the list view.
I understand that the attributes layout might then change from line to
line, but since we have only two sets of attributes, that would not
matter (to us). Would you consider implementing this function (i.e.
evaluate the conditions and hide attributes also in list view),
if not by default, then maybe as an option of the config file?

Another nice feature (which we do not explicitly need, just a suggestion)
might be implementing a filter function in list view, such that only entries
with certain attribute values are displayed.

I have also found one possible problem, maybe it's already solved in the
newest version: We have set up the elog under an stunnel, but the elog
server also responds to the original port (i.e. 80), displaying the logbook
selection page and from there even the login screen. Only after logging in
the elog server redirects the client browser to the https-page defined with
the URL-statement of the config file. The whole thing seems like an unwanted
behaviour, but could you change it so that it either doesn't respond on the
wrong URL at all, or at least redirects to the secured URL before presenting
the login window, so that we transfer the passwords encrypted?

Cheers

Yoshio

1436

Sun Oct 9 20:49:41 2005

I find some new strings from the warnings like this:

Quote:

Language error: string "HelpELCode" not found for language "chinese"

I have added these new string to the languages files in Chinese. I think:
"Enter name of hypelink" should be "Enter name of hyperlink".

1442

Mon Oct 10 14:09:49 2005

Re: Some spell mistakes

Exaos Lee wrote:

I find some new strings from the warnings like this:

Quote:

Language error: string "HelpELCode" not found for language "chinese"

I have added these new string to the languages files in Chinese. I think:
"Enter name of hypelink" should be "Enter name of hyperlink".

Ok, fixed in the current subversion repository. Better write such things by personal mail to me, since it might not interest the elog community very much.

1445

Mon Oct 10 19:26:35 2005

Re: Some spell mistakes

Quote:

Ok, fixed in the current subversion repository. Better write such things by personal mail to me, since it might not interest the elog community very much.

Sorry.

I will mail you first next time.

1457

Thu Oct 13 14:47:06 2005

Yoshio Imai

imai@kph.uni-mainz.de

Request

Linux

2.6.0beta2

Re: Conditional hiding of attributes in list view

Stefan Ritt wrote:

Of course you can put a separate tile line each time you switch from "one" to "two", but that costs a lot of space. So how would you layout a listing where different attribute sets are mixed?

Well, in our case the changes would not be very frequent (if the beamtime goes smooth, we will have mainly
run-entries and few admin entries; if it is a hardware developement beamtime, we will have mainly admin
entries and fewer run entries). So, for us a layout with a new title line at the change between the two sets of attributes is ok.

Stefan Ritt wrote:

Well, the "theme" is a "resource". The manual says: Resource dir = <directory>: Specifies the root directory for ELOG resources like help files, themes, icons and user HTML files, so it's explicitly written there.

I see. I thought that the "hardcoded" default directory would still be searched -- my error.

Stefan Ritt wrote:

Which features do you mean? In your previous posting you mentioned a filter, but you found that already. So what else is left except the hiding of attributes?

Not much

. The only thing left was that the elogd redirects to the "URL="-address only after logging in, and not already after selecting a logbook in the selection page (i.e. before the password is transmitted), when a user calls directly the elogd port and not, say, the stunnel port defined to secure the connection. In our case this doesn't matter so much, but maybe to others it does ... ?

Thanks for the work

Yoshio

1497

Fri Oct 28 23:45:33 2005

Re: Conditional hiding of attributes in list view

Yoshio Imai wrote:

I have also found one possible problem, maybe it's already solved in the
newest version: We have set up the elog under an stunnel, but the elog
server also responds to the original port (i.e. 80), displaying the logbook
selection page and from there even the login screen. Only after logging in
the elog server redirects the client browser to the https-page defined with
the URL-statement of the config file. The whole thing seems like an unwanted
behaviour, but could you change it so that it either doesn't respond on the
wrong URL at all, or at least redirects to the secured URL before presenting
the login window, so that we transfer the passwords encrypted?

I implemented that in revision 1540. On the logbook selection page, the links to the individual logbooks honor the "URL = ..." statement from the config file, and thus you get redirected via "https://...". More is unfortunately not possible. If elogd gets contacted the first time, it is impossible to figure out by elogd under which URL it got contacted, and therefore it cannot distinguish between secure and insecure connections. The only way is to switch off port 80 by a firewall and only allow "https://..." connections from outside.

1498

Mon Oct 31 01:36:52 2005