ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67443
|
Wed Feb 20 21:13:28 2013 |
| Chris Smith | crms57@yahoo.ca | Question | Windows | ELOG V2.7. | Multiple versions of elog on one server | Is there a way of having multiple copies of elog running on one windows 2003 server? different ports?
I need to access 2 different elogd.cfg files. |
67442
|
Wed Feb 20 09:32:52 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.9.2.2455 | Re: FCKEditor doesn't show up in Windows 8? |
John Haggerty wrote: |
After installing ELOG on a new Windows 8 machine, I found everything working fine... until I went to make a new entry. New entries work... but the FCKEditor toolbars do not show up. I tried a variety of things (start as a service, start not as a service, run as administrator), but nothing made the toolbar appear that I coumd find. The ELCode editor toolbar appears, but the nifty FCKEditor toobar never appears. I could not figure out how to debug FCKEditor. Any ideas?
|
Thanks for reporting that problem. Indeed the elog292-1.exe distribution has a bug in the directory structure. I fixed that in elog292-2.exe, which you can download from here:
http://midas.psi.ch/elog/download/windows/elog292-2.exe |
67441
|
Wed Feb 20 02:45:45 2013 |
| John Haggerty | haggerty@bnl.gov | Bug report | Windows | 2.9.2.2455 | FCKEditor doesn't show up in Windows 8? | After installing ELOG on a new Windows 8 machine, I found everything working fine... until I went to make a new entry. New entries work... but the FCKEditor toolbars do not show up. I tried a variety of things (start as a service, start not as a service, run as administrator), but nothing made the toolbar appear that I coumd find. The ELCode editor toolbar appears, but the nifty FCKEditor toobar never appears. I could not figure out how to debug FCKEditor. Any ideas? |
67440
|
Tue Feb 19 09:14:22 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.1-2435 | Re: Protect Selection page=1 |
Ocane wrote: |
Hi,
I have several top groups and each has several logbooks.
If I use the global option Protect Selection page=1 and Show top groups = 1, after an user logs in to the top group selection URL, the elog steers away from the top group selection page, and automatically brings him to the logbook selection page of the first top group. Is the elog programmed to exhibit this behavior?
What I would prefer is that, after an user logs in, the elog stays on the top group selection page, sine each user has his preferred destination, not always the logbooks in the first top group. Is there any setting I can use in the config file to do this?
(My users need to access different top groups and logbooks on regular basis).
Thank you and regards.
|
There is currently no way to change this in the config file. I will review the issue when I get some time and maybe come up with a fix. |
67439
|
Tue Feb 19 09:13:34 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.1-2435 | Re: Protect Selection page=1 |
Tom Langford wrote: |
Ocane wrote: |
Hi,
I have several top groups and each has several logbooks.
If I use the global option Protect Selection page=1 and Show top groups = 1, after an user logs in to the top group selection URL, the elog steers away from the top group selection page, and automatically brings him to the logbook selection page of the first top group. Is the elog programmed to exhibit this behavior?
What I would prefer is that, after an user logs in, the elog stays on the top group selection page, sine each user has his preferred destination, not always the logbooks in the first top group. Is there any setting I can use in the config file to do this?
(My users need to access different top groups and logbooks on regular basis).
Thank you and regards.
|
I am currently having a similar problem. I am migrating a few separate elogs to one new computer. I have three top groups set up with their own password files. If I log into top group A (TGA), and then try to go to top group B (TGB), I am presented with a "Create new user" screen for my login name for TGA. When I complete that form, I am taken to the user settings for top group A, rather than TGB. I can log out of TGA and then log into TGB fine, but if I try to switch between them without logging out, it freaks out.
There seems to be a problem with the cookies that keep me logged into the different top groups not recognizing that they are different entities. I'm running eLog 2.9.1 rev 436. Is it possible that this has been addressed in 2.9.2?
Thanks,
-t
|
Certainly 2.9.1 and 2.9.2 should behave similar in that respect. Have you tried to clear all cookies in your browser and try again?
/Stefan |
67438
|
Mon Feb 18 20:12:25 2013 |
| Tom Langford | tlangfor@umd.edu | Question | Linux | 2.9.1-2435 | Re: Protect Selection page=1 |
Ocane wrote: |
Hi,
I have several top groups and each has several logbooks.
If I use the global option Protect Selection page=1 and Show top groups = 1, after an user logs in to the top group selection URL, the elog steers away from the top group selection page, and automatically brings him to the logbook selection page of the first top group. Is the elog programmed to exhibit this behavior?
What I would prefer is that, after an user logs in, the elog stays on the top group selection page, sine each user has his preferred destination, not always the logbooks in the first top group. Is there any setting I can use in the config file to do this?
(My users need to access different top groups and logbooks on regular basis).
Thank you and regards.
|
I am currently having a similar problem. I am migrating a few separate elogs to one new computer. I have three top groups set up with their own password files. If I log into top group A (TGA), and then try to go to top group B (TGB), I am presented with a "Create new user" screen for my login name for TGA. When I complete that form, I am taken to the user settings for top group A, rather than TGB. I can log out of TGA and then log into TGB fine, but if I try to switch between them without logging out, it freaks out.
There seems to be a problem with the cookies that keep me logged into the different top groups not recognizing that they are different entities. I'm running eLog 2.9.1 rev 436. Is it possible that this has been addressed in 2.9.2?
Thanks,
-t |
67437
|
Wed Feb 13 16:59:06 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.9.1 | Re: Locking a Thread |
Hal Proctor wrote: |
Stefan Ritt wrote: |
Hal Proctor wrote: |
How can I set up the admins or manager group with the ability to Lock a Thread? I don't wish to keep two log books.
|
With
allow <command> = <user list>
deny <command> = <user list>
you can prevent certain users to use certain commands (like delete a message). If you only allow admins to issue the "edit" command, that would in principle do it, but then normal users cannot edit their entries any more. Unfortunately this command cannot be restricted to certain attributes, like the thread "status". So I guess what you want is not exactly possible with the current implementation.
|
Thanks for the reply. I was looking for a way to stop replies to a runaway thread. Was wondering why the elog system has a "Locked by" attribute, but no way to set it.
|
That's a different meaning. The "Locked by" flag gets set when one user edits an entry. During the editing the entry gets "locked", which means that no one else can change it during that time. This should prevent one person to overwrite the edits of another if they are editing the same entry at the same time. Your "locking" means the locking of threads, which elog doe not "understand", it's just your definition of an attribute in your logbook. |
67436
|
Wed Feb 13 16:56:40 2013 |
| Hal Proctor | hproctor2@gmail.com | Question | Windows | 2.9.1 | Re: Locking a Thread |
Stefan Ritt wrote: |
Hal Proctor wrote: |
How can I set up the admins or manager group with the ability to Lock a Thread? I don't wish to keep two log books.
|
With
allow <command> = <user list>
deny <command> = <user list>
you can prevent certain users to use certain commands (like delete a message). If you only allow admins to issue the "edit" command, that would in principle do it, but then normal users cannot edit their entries any more. Unfortunately this command cannot be restricted to certain attributes, like the thread "status". So I guess what you want is not exactly possible with the current implementation.
|
Thanks for the reply. I was looking for a way to stop replies to a runaway thread. Was wondering why the elog system has a "Locked by" attribute, but no way to set it. |
|