Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 189 of 806  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  2176   Mon Mar 26 13:03:05 2007 Reply Stefan Rittstefan.ritt@psi.chRequestWindowsELOG V2.6.Re: Global "MOptions"

Fergus Lynch wrote:
Would it be an option to have Global "MOptions" - perhaps configured in the 'global options' file - which can be called up and referenced in all logbooks?


Sure, that's possible alreay with the current version. Just put your MOptions statement under [global] and it will be used in all logbooks. If a specific logbook uses different MOptions, put the a second MOptions list under that logbook's section and it will overwrite the global setting.
  2180   Fri Mar 30 06:38:28 2007 Reply Stefan Rittstefan.ritt@psi.chBug reportAll | Other2.6.2-1739Re: "Guest menu commands" not changing the menu line

Steve Jones wrote:
Am I doing something wrong or was this a problem in the past?


I can't remember any problem of that type.


Steve Jones wrote:
Suggestions on where to look? Start from scratch?


Might not be a bad idea. Use the little config file from the distribution, then just add the guest menu lines, and try it. If it works, modify it gradually until it equals to your full config file, to see where the problem is. Stupid quiestion: After you added your guest menu, did you log out to become a "guest"? If you are logged in with your user name (stored in a cookie), you never will see the guest menu.
  2184   Tue Apr 3 14:26:09 2007 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.4-1795Re: Multiple ideas for multiple logbooks

Yoshio Imai wrote:
1. Multiple login


Well, restructuring the cookies would be rather work intensive. Right now we have one user name cookie unm
used for all logbooks. To distinguish betwen logbooks, one would need cookies in the form <logbook name>_unm and <logbook name>_upwd. Let me think about.


Yoshio Imai wrote:
2. <Ctrl-T>


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. I'm still fine-tuning shortcuts. I realized that CTRL-C which I used for CODE is normally used for Copy/Paste, so I changed that already to CTRL-O to free up CTRL-C. Since tables are not so often used, I removed it now completely. There is also CTRL-P for Preview and CTRL-ENTER for Submit. While this works now nice on Mozilla based browsers, I cannot intercept CTRL keys on IE. I know you and I don't care, but many people unfortunately do. So get the SVN update, and let me know what you think, if there is still something to be modified before I make the official release.
  2185   Tue Apr 3 15:19:00 2007 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.4-1795Re: Multiple ideas for multiple logbooks

Stefan Ritt wrote:
To distinguish betwen logbooks, one would need cookies in the form <logbook name>_unm and <logbook name>_upwd.


Actually this is not a good idea. Most people I know have several logbooks, but a common password file. Access control is then fine-tuned via 'Login user = ...'. Now if I implement a per-logbook cookie, these people would have to log in once for each logbook. If the go to a new browser which does not contain their old cookies, or if the cookies expire, they would have to log in again once for each logbook. On installations with 20 and more logbooks this can be cumbersome. So all these people would complain.
  2186   Tue Apr 3 17:16:23 2007 Reply Stefan Rittstefan.ritt@psi.chBug reportAll | Other2.6.2-1739Re: "Guest menu commands" not changing the menu line

Steve Jones wrote:
BTW, WebSVN no longer provides a means of downloading a tar of your code trunk. I had to go to http://midas.psi.ch/elog/download/tar/ in order to get your 2.6.4-1 revision.


That should be fixed now.


Steve Jones wrote:
Ok, here is what I found. Apparently in the past there was a "Find Menu Commands = " option? Because I had this in my config and elog was not barfing on it being there. So, I changed the word "Find" with "List" and things seems to now work. Stefan, was there an old command called "Find Menu Commands"?


Yes. Indeed this was changes some time ago. Have a look at elog:880. Unfortunately I did not announce this change clearly.
  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.
  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?
  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.
ELOG V3.1.5-3fb85fa6