HOW TO delete or edit the Accelerator config file? i can still edit my demo config file., posted by marion on Tue Apr 10 04:15:22 2007
|
hi again folks
QUESTION
HOW do i delete or edit the Accelerator config file?
i can still edit my demo config file. |
Re: HOW TO delete or edit the Accelerator config file? i can still edit my demo config file., posted by Stefan Ritt on Tue Apr 10 10:14:39 2007
|
| marion wrote: | hi again folks
QUESTION
HOW do i delete or edit the Accelerator config file?
i can still edit my demo config file. |
Edit elogd.cfg with notepad.exe directly. |
Multiple ideas for multiple logbooks, posted by Yoshio Imai on Tue Apr 3 13:17:27 2007
|
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! |
|
Re: Multiple ideas for multiple logbooks, posted by Stefan Ritt on Tue Apr 3 14:26:09 2007
|
| 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  . 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. |
|
Re: Multiple ideas for multiple logbooks, posted by Stefan Ritt on Tue Apr 3 15:19:00 2007
|
| 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. |
Re: Multiple ideas for multiple logbooks, posted by Yoshio Imai on Tue Apr 3 17:55:21 2007 
|
| Stefan Ritt wrote: | | Well, you didn't realize, but you were my beta-tester for the keyboard shortcuts . I didn't yet publish it, so you must have gotten this brand new feature from SVN. |
You should really have told me  . 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 ) 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? |
|
Re: Multiple ideas for multiple logbooks, posted by Stefan Ritt on Tue Apr 3 21:09:47 2007
|
| 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. |
|
Re: Multiple ideas for multiple logbooks, posted by Stefan Ritt on Tue Apr 3 22:10:56 2007
|
| Yoshio Imai wrote: | BTW, there are (of course ) 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? |
|
Re: Multiple ideas for multiple logbooks, posted by Stefan Ritt on Wed Apr 4 12:14:12 2007
|
| 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? |
|
Re: Multiple ideas for multiple logbooks, posted by Yoshio Imai on Wed Apr 4 14:20:41 2007
|
| 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? |
|
Re: Multiple ideas for multiple logbooks, posted by Stefan Ritt on Thu Apr 5 10:01:06 2007
|
| 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. |
|
Re: Multiple ideas for multiple logbooks, posted by Stefan Ritt on Wed Apr 4 08:38:30 2007
|
| 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. |
Re: Multiple ideas for multiple logbooks, posted by Yoshio Imai on Wed Apr 4 11:37:56 2007
|
| 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 ... ).
| 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! |
|
Global "MOptions", posted by Fergus Lynch on Mon Mar 26 11:45:07 2007
|
Hi,
We have ELOG configured for virtually every conceivable use in our IT Operation dept and it is fantastically useful and easy to use. One result of this - naturally! - is that we have quiet a few logbooks.
Many of these logbooks share the same attributes - especially Moptions for equipment lists - which is fine but requires manually copying and pasting Moption lists into multiple logbooks to keep everything synchronized.
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?
Just an idea -
Cheers
Fergus |
|
Re: Global "MOptions", posted by Stefan Ritt on Mon Mar 26 13:03:05 2007
|
| 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. |
|
Re: Global "MOptions", posted by Fergus Lynch on Tue Mar 27 13:57:44 2007
|
| Stefan Ritt wrote: |
| 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 already 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. |
Perfect! Works a treat (I promise to read the manual next time!)
Cheers
Fergus |
|
Private logbook - no guest access?, posted by Ben Shepherd on Tue Mar 20 13:45:20 2007
|
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 |
|
Re: Private logbook - no guest access?, posted by Stefan Ritt on Tue Mar 20 13:48:50 2007
|
| 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. |
|
Re: Private logbook - no guest access?, posted by Ben Shepherd on Tue Mar 20 14:42:05 2007
|
| 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! |
|
submit modified elog entry, posted by deletoille on Wed Mar 14 11:31:35 2007
|
hello, I have small a bug,
when I create an entry. Per moment the program requires of me: "Submit modified Elog entry"
if I answer yes, Eog create 2 entry identical.
If I answer not it create only one.
I don't wait that elog asks me a confirmation
Any Ideas,
Thanks in advance |
|
Re: submit modified elog entry, posted by Stefan Ritt on Mon Mar 19 19:51:26 2007
|
| deletoille wrote: | hello, I have small a bug,
when I create an entry. Per moment the program requires of me: "Submit modified Elog entry"
if I answer yes, Eog create 2 entry identical.
If I answer not it create only one.
I don't wait that elog asks me a confirmation
|
Are you sure about that? Can you reproduce it? I tried to reproduce it with the simple example logbook from the distribution, by adding the Use lock = 1 option to the configuration, but without success. I got only a single entry or no entry. You can of course remove the Use lock option, if you don't need locking. |
Addition of a "Restrict edit attribute" option?, posted by Justin Ellison on Tue Mar 13 17:27:49 2007
|
It would be a nice addition to have a config file option named "Restrict edit attribute".
Basically, I would like to have an attribute that was either:
a) An Option Attribute named Status with options of "Open" or "Closed"
b) An Option Attribute named Closed that was boolean.
Then, we could leave the item as editable until either choice "a" above was set to closed or choice "b" was true, at which point only admins could edit the item.
Sound plausible?
Justin |
|
Re: Addition of a "Restrict edit attribute" option?, posted by Stefan Ritt on Tue Mar 13 20:58:07 2007
|
| Justin Ellison wrote: | It would be a nice addition to have a config file option named "Restrict edit attribute".
Basically, I would like to have an attribute that was either:
a) An Option Attribute named Status with options of "Open" or "Closed"
b) An Option Attribute named Closed that was boolean.
Then, we could leave the item as editable until either choice "a" above was set to closed or choice "b" was true, at which point only admins could edit the item.
|
Conditional attributes? Like:
Attributes = ..., Status
Options Status = Open{1}, Closed{2}
{2}Locked attributes = Status
Unfortunately once it's locked, the admin has to change the config file to unlock it. |
|
Re: Addition of a "Restrict edit attribute" option?, posted by Justin Ellison on Wed Mar 14 15:03:41 2007
|
Sorry, I didn't explain it enough.
This feature is like "Restrict edit time", but instead of setting an entire entry as read only after n hours, we set it read only if attribute y is true. Admin would be able to go in and reset that attribute to false to unlock the entry for editing, but no one else would be able to.
That make more sense?
Justin |
|
Re: Addition of a "Restrict edit attribute" option?, posted by Stefan Ritt on Wed Mar 14 15:06:27 2007
|
| Justin Ellison wrote: | Sorry, I didn't explain it enough.
This feature is like "Restrict edit time", but instead of setting an entire entry as read only after n hours, we set it read only if attribute y is true. Admin would be able to go in and reset that attribute to false to unlock the entry for editing, but no one else would be able to. |
I understand what you want. The conditional attributes I showed you give you that functionality, except that unlocking is a bit painful for the admin (has to edit the config file each time). Sorry, but that's all I can give you. |
|
Re: Addition of a "Restrict edit attribute" option?, posted by Justin Ellison on Wed Mar 14 15:43:51 2007
|
| Stefan Ritt wrote: |
I understand what you want. The conditional attributes I showed you give you that functionality, except that unlocking is a bit painful for the admin (has to edit the config file each time). Sorry, but that's all I can give you. |
Now I understand what you were getting at. Sorry for the confusion. That should work fine for us - unlocking is something that shouldn't ever happen.
Thanks for the quick response!
Justin |
|
Hiding attributes in Detail view?, posted by Justin Ellison on Fri Mar 2 16:39:22 2007
|
First off, thanks so much for this product. It works excellent for us as a server activity log. I have a question, which depending on the answer, might be a feature request
As I mentioned, we use elog as a serverlog. Sometimes, but not always, we will have a Bugzilla bug # that is associated with the log entry. We then take that bug #, and build a link to our bugzilla server displaying the bug. Here's the relevant config entries:
Attributes = Author, Classification, Subject, Bug Number, Environment, Server, Bugzilla
...
#Make the list table narrow enough to fit in the browser
List display = ID, Date, Author, Subject, Server, Bugzilla
...
#We take in a Bug Number from the user, then calculate a Bugzilla link from that
Change Bugzilla = <a href="http://bugz:4545/bugzilla/show_bug.cgi?id=$Bug Number">$Bug Number</a>
List Change Bugzilla = <a href="http://bugz:4545/bugzilla/show_bug.cgi?id=$Bug Number">$Bug Number</a>
Hidden Attributes = Bugzilla
So, on new entry, the user has the option to enter a Bug Number. Bugzilla is not displayed because it is derived. In list view, Bug Number is not displayed, but Bugzilla is, providing a handy link to the bug on a different server.
The only thing that isn't working as I'd like is when someone views a log entry. Both Bug Number and Bugzilla show up in the attributes. This isn't a huge deal, it's just showing redundant data.
Is there a way to hide Bug Number on the view page? |
|
Re: Hiding attributes in Detail view?, posted by Justin Ellison on Fri Mar 9 22:14:57 2007
|
| Any takers? |
|
Re: Hiding attributes in Detail view?, posted by Stefan Ritt on Mon Mar 12 20:35:17 2007
|
| Justin Ellison wrote: | The only thing that isn't working as I'd like is when someone views a log entry. Both Bug Number and Bugzilla show up in the attributes. This isn't a huge deal, it's just showing redundant data.
Is there a way to hide Bug Number on the view page? |
In revision 1809 I implemented the options
Show attributes = ...
Show attributed edit = ...
The first one is for the log entry page, the second for the entry form. This way you can distinguish between the bug number and the link. The old option Hidden attributes has been dropped, since it has the same effect now as Show attributes edit. |
|
Search all logbooks as default, posted by An Thai on Mon Mar 5 14:41:20 2007
|
Hello all,
do you know how I can default set the option "Search all logbooks" in the Find page selected/checked?
Best regards,
An |
|
Re: Search all logbooks as default, posted by Stefan Ritt on Thu Mar 8 08:08:42 2007
|
| An Thai wrote: | | do you know how I can default set the option "Search all logbooks" in the Find page selected/checked? |
I added the option
Search all logbooks = 2
which lets you do that. It's in the SVN version and will be contained in the next release. |