Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 417 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 ... 416, 417, 418 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  2157   Tue Mar 6 16:59:13 2007 Disagree T. Ribbrockemgaron@gmx.netBug reportLinux2.6.4Upgrade to 2.6.4 broke quick search
Hi!

I just went from 2.6.1 to 2.6.4 and since the upgrade, the quick search drop-down menus no longer work. I can select an attribute, but when I do so, I only get an empty page with the following message:
Attachment #0 of entry #0 not found
Please use your browser's back button to go back

When I do go back, the attribute I selected is still selected, but all entries are listed. With 2.6.1, this worked like a charm.

Any idea?

Thanks in advance,

Thomas
  2158   Tue Mar 6 17:03:43 2007 Agree T. Ribbrockemgaron@gmx.netBug reportLinux2.6.4Re: Upgrade to 2.6.4 broke quick search

T. Ribbrock wrote:

[...]
I just went from 2.6.1 to 2.6.4 and since the upgrade, the quick search drop-down menus no longer work. I can select an attribute, but when I do so, I only get an empty page with the following message:
Attachment #0 of entry #0 not found
Please use your browser's back button to go back
[...]


Apparently, this must have been some session-oddity - I just logged out and got an error message about a bad URL. I then went to the base URL of the logbook (i.e. http://server:8080), chose the correct logbook and logged in again. Things work fine since. No idea what went wrong the first time round... Frown

Regards,

Thomas
  2171   Tue Mar 20 13:45:20 2007 Question Ben Shepherdbjs54'at'dl'dot'ac'dot'ukQuestionLinux2.6.2-1739Private logbook - no guest access?
Hi,

I want to set up a logbook which you have to be logged in to be able to read entries. I've already got three logbooks which can be viewed by anyone but only logged-in users can modify them. For the fourth one, I want to have a private logbook which can't be read by 'guest' users. Is this possible?

cheers

ben
  2172   Tue Mar 20 13:48:50 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.2-1739Re: Private logbook - no guest access?

Ben Shepherd wrote:
I want to set up a logbook which you have to be logged in to be able to read entries. I've already got three logbooks which can be viewed by anyone but only logged-in users can modify them. For the fourth one, I want to have a private logbook which can't be read by 'guest' users. Is this possible?


Per default, logbooks can only be read by logged in users if you use "password file = xxx". It is however possible to make these logbooks readable by 'guest' users if you use "Guest menu commands = xxx" and "Guest list menu commands = xxx". So just remove these two options from your fourth logbook and you get what you want.
  2173   Tue Mar 20 14:42:05 2007 Reply Ben Shepherdbjs54@dl.ac.ukQuestionLinux2.6.2-1739Re: Private logbook - no guest access?

Stefan Ritt wrote:

Ben Shepherd wrote:
I want to set up a logbook which you have to be logged in to be able to read entries. I've already got three logbooks which can be viewed by anyone but only logged-in users can modify them. For the fourth one, I want to have a private logbook which can't be read by 'guest' users. Is this possible?


Per default, logbooks can only be read by logged in users if you use "password file = xxx". It is however possible to make these logbooks readable by 'guest' users if you use "Guest menu commands = xxx" and "Guest list menu commands = xxx". So just remove these two options from your fourth logbook and you get what you want.


Thanks! I actually saw that in the config documentation, but I had assumed that it didn't work. Turns out I'd left those two options in my [global] section as well. Oops!
  2183   Tue Apr 3 13:17:27 2007 Idea Yoshio ImaiRequestLinux2.6.4-1795Multiple ideas for multiple logbooks
Hi!

After a long pause, here we are again with a bunch of new ideas (and problems ...;) )

1. Multiple login
Since we are using the elog system now for most aspects of our work, we are more and more often confronted with the need to work with different logbooks open in parallel (e.g. the shift logbook as well as the personal analysis logbook, via tabbed browsing). These logbooks do not always have the same users allowed to access them, so when having logged on to one logbook and then opening another one in a different browser tab, I have to log on as a different user, thereby losing the login on the first logbook. 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?

2. <Ctrl-T>
While using this logbook (and tabbed browsing), I noticed that the keyboard shortcut <Ctrl-T> now leads to the creation of a table (great thing, btw). However, many of our users are accustomed to this shortcut opening a new browser Tab. Is there any way to disable these elog shortcuts or otherwise disentangle these functions (by using <Alt> instead of <Ctrl> or something similar, since the functionality itself is very good)?

Thanks for any idea on these issues, and thanks for the great software!
  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.
Goto page Previous  1, 2, 3 ... 416, 417, 418 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6