Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 542 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 541, 542, 543 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subject
  2194   Thu Apr 5 10:01:06 2007 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.4-1826Re: Multiple ideas for multiple logbooks

Yoshio Imai wrote:

Possible, but I think it worked also on our server until the number of logbooks in the top group got larger than one. Can you try to see if your code still works when there is more than one logbook defined?


I tried with following config file:
[global]
port = 8080
password file = passwd

{1}Preset text = Routine
{2}Preset text = Other

[demo]
Attributes = Author, Type
Options Type = Routine{1}, Other{2}

[demo2]
Attributes = Author, Type
Options Type = Routine{1}, Other{2}

and it worked fine as well. So take you (big) config file, strip one item by one, until you arrive at the simple config file above and tell me the minimal config file which produces this problem.
  2193   Wed Apr 4 14:20:41 2007 Reply Yoshio ImaiBug reportLinux2.6.4-1826Re: Multiple ideas for multiple logbooks

Stefan Ritt wrote:
Maybe some other problem?

Possible, but I think it worked also on our server until the number of logbooks in the top group got larger than one. Can you try to see if your code still works when there is more than one logbook defined?
  2192   Wed Apr 4 12:14:12 2007 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.4-1826Re: Multiple ideas for multiple logbooks

Yoshio Imai wrote:
- We have one logbook top group for the beamtimes. Under certain conditions, a preset text is to be displayed. 
{2&a} Preset Text = resource/text_1.txt
{2&b} Preset Text = resource/text_2.txt
However, the definitions of these conditions have to be repeated for every logbook in the group (putting it only under [global beamtimes] doesn't do it), otherwise they are ignored.

Any idea on these?


I tried to reproduce with this code:
[global]
port = 8080
password file = passwd
SMTP host = mail.psi.ch

{1}Preset text = Routine
{2}Preset text = Other

[demo]
Attributes = Author, Type
Options Type = Routine{1}, Other{2}

but it worked fine. Maybe some other problem?
  2191   Wed Apr 4 11:37:56 2007 Agree Yoshio ImaiRequestLinux2.6.4-1795Re: Multiple ideas for multiple logbooks

Stefan Ritt wrote:
Actually there is a way

... and it works! Thank you!


Stefan Ritt wrote:
I fixed that now in the updated elcode.js.

That works now, too!


Stefan Ritt wrote:
Your other problem of ignoring the control keys at all I could not reproduce. Try to reproduce it in a well-defined way and let me know.

I will try to do that (new beamtime, new occasions ... Wink).


Stefan Ritt wrote:
Maybe you used a userlist attribute for the author?

No, I didn't. I will try to investigate this further and let you know if I find anything.

So for the moment ... thanks for the help!
  2190   Wed Apr 4 08:38:30 2007 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.4-1795Re: Multiple ideas for multiple logbooks

Yoshio Imai wrote:
1. Multiple login
Is there any way to change the cookie structure so as to allow one (physical) user to be logged on as more than one elog user at a time?


Actually there is a way, but I completely forgot about that. The manual says:


ELOG manual wrote:

If any of the password statements are in the [global] area of the configuration files, they are used for all logbooks. If one logs in at one logbook, access is automaticlly granted to all logbooks. If the password statements are in the individual logbook sections, one has to log in to each logbook separately.


That should help. Just put the password file = ... into the individual logbook sections, and you should get what you want. You can check this by inspecting the cookies (first you have to delete all cookies in your browser). With passoword files for individual logbooks you should see an associated Path for each logbook, so the login cookie only gets submitted to that logbook, allowing differnt user names/passwords for different logbooks.
  2189   Tue Apr 3 22:10:56 2007 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.4-1826Re: Multiple ideas for multiple logbooks

Yoshio Imai wrote:
BTW, there are (of course Big grin) two other issues. They are still present in -1826
- one bug was reported by a logbook user: when using the "find" function in a logbook, and selecting one value from the "Author" drop-down list and another from the "Category" drop-down list, the elogd reports no entries found, but when specifying only the "Author" and leaving "Category" blank, many entries are found, including those with the "Category" being looked for. When specifying only the "Category" and leaving the "Author" blank, the elogd also reports no entries found. Has anyone reported a similar behaviour?


I tried to reproduce this, but without success. I made a very simple config file like:
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Quick filter = Type, Category

And produced some entries with various attribute values. But when selecting them from the quick filter, or selecting them from the find page, both gave correct results. Maybe you used a userlist attribute for the author?
  2188   Tue Apr 3 21:09:47 2007 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.4-1826Re: Multiple ideas for multiple logbooks

Yoshio Imai wrote:
When using the shortcuts and/or the ELCode buttons, sometimes the code is generated and the cursor in between the [XX] and [/XX] directive, but sometimes, the whole code directive is selected as if for editing


I found at least that problem. If you select one or more words and press CTRL-B for example, your selection is surrounded by the [B]...[/B] tags. If you double click with your mouse on a word, usually the space between this word and the next word is selected as well. I modified the code such that if there is a blank at the end of a selection, it gets stipped off before placing the tags. This had the side-effect that if there was no selection at all, you got the reported mis-behaviour if there was a blank at your cursor position. I fixed that now in the updated elcode.js.

Your other problem of ignoring the control keys at all I could not reproduce. Try to reproduce it in a well-defined way and let me know.
  2187   Tue Apr 3 17:55:21 2007 Smile Yoshio ImaiBug reportLinux2.6.4-1826Re: Multiple ideas for multiple logbooks

Stefan Ritt wrote:
Well, you didn't realize, but you were my beta-tester for the keyboard shortcuts Big grin . I didn't yet publish it, so you must have gotten this brand new feature from SVN.

You should really have told me Wink . Actually, I found out about the <Ctrl-C> issue while using this logbook.

Stefan Ritt wrote:
So get the SVN update, and let me know what you think

Did so, we are running now -1826. I think it is very usable, with maybe one exception (this might be a browser issue, however): When using the shortcuts and/or the ELCode buttons, sometimes the code is generated and the cursor in between the [XX] and [/XX] directive, but sometimes, the whole code directive is selected as if for editing

which prevents from immediately continuing to type (which, I guess, was the idea behind the shortcuts). The behaviour is not completely reproducible, and I have even seen it change during one and the same browser (=firefox) session while working on the same entry (*). I also had it once that the browser out of a sudden completely ignored the ELCode meaning, and instead used <Ctrl-I> for page info and <Ctrl-B> for the history.

(*) It just happened again!


BTW, there are (of course Big grin) two other issues. They are still present in -1826
- one bug was reported by a logbook user: when using the "find" function in a logbook, and selecting one value from the "Author" drop-down list and another from the "Category" drop-down list, the elogd reports no entries found, but when specifying only the "Author" and leaving "Category" blank, many entries are found, including those with the "Category" being looked for. When specifying only the "Category" and leaving the "Author" blank, the elogd also reports no entries found. Has anyone reported a similar behaviour?

- We have one logbook top group for the beamtimes. Under certain conditions, a preset text is to be displayed. 
{2&a} Preset Text = resource/text_1.txt
{2&b} Preset Text = resource/text_2.txt
However, the definitions of these conditions have to be repeated for every logbook in the group (putting it only under [global beamtimes] doesn't do it), otherwise they are ignored.

Any idea on these?
Goto page Previous  1, 2, 3 ... 541, 542, 543 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6