ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
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 |
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. |
1723
|
Thu Feb 23 15:50:20 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.1 | Re: Protect Selection page |
Hagelstein, Kay wrote: | I have a problem with the Option “Protect Selection page = 1” it doesn’t word in my Configuration. Is This a bug or a Problem with the Configuration? |
Thanks for reporting this. I could reproduce the prolem thanks to the config file you supplied. I fixed the problem and made a new release 2.6.1-3. |
1724
|
Thu Feb 23 16:36:42 2006 |
| Hagelstein, Kay | k.hagelstein@stadt.wede.de | Question | Windows | 2.6.1 | Re: Protect Selection page |
Stefan Ritt wrote: |
Hagelstein, Kay wrote: | I have a problem with the Option “Protect Selection page = 1” it doesn’t word in my Configuration. Is This a bug or a Problem with the Configuration? |
Thanks for reporting this. I could reproduce the prolem thanks to the config file you supplied. I fixed the problem and made a new release 2.6.1-3. |
It works now fine.
Thanks & Regards
Kay |
66610
|
Fri Nov 13 15:54:21 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Windows | 2.7.7 | Re: Problems zooming elog pages in Internet Explorer - a possible fix |
Richard Stamper wrote: |
Internet Explorer fails to display correctly some aspects of pages generated by elog when the zoom functionality is used (Ctrl + and Ctrl -). This is really a bug in the IE renderer rather than elog, but since IE can be persuaded to do better relatively easily it might be worth making some minor changes to make elog more robust when used with the buggy Microsoft browser.
The problem I encountered was initially with the multiple checkboxes for an Moptions attribute, but I noticed later it also affects the logbook tabs at the top of the screen. If you start creating a submission to this forum in IE (7 or earlier, at least) you can see the problem; when zooming, the text labels and the checkboxes do not scale together so start overlapping, and the same happens with the logbook tabs and the text links on them. The problem is apparently to do with a proprietary IE concept called "layout" - see http://www.satzansatz.de/cssd/onhavinglayout.html for details - and IE struggles when some elements do not have the hasLayout property set to "true".
The fix is to coerce elements to have the hasLayout element set to "true" by giving them some benign CSS property. The best I can find is to set "display: inline-block" for some of the key elements, and this can be done by modifying default.css rather than the elogd.c code.
Adding
span {
display: inline-block;
}
to default.css (e.g. just after the default style definition for the "td" element) and adding
display: inline-block;
to the style sets for the .sltab and .ltab classes (generic, not those specific to the "a" element) seems to prevent IE doing bad things with the display when zooming without messing up the display in Firefox. I have not tested this comprehensively or in any other browsers, but I thought it might be worth passing on.
Cheers,
Richard Stamper
|
I just tried with IE8 (don't have IE7 installed any more), and it looked to me like this has been fixed there. So this will get less a problem in the future. If people are stuck to IE7, they can made your modification themselves in the CSS file, so I guess I won't change the distribution for the moment.
|
68678
|
Wed Aug 23 15:11:32 2017 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | 3.1.3-aded4ae | Re: Problems with german_UTF8 language |
Just an update: I've re-compiled, reinstalled and restarted elogd for other reasons and now the corrupted strings are all gone. Everthing looks fine now.
But I never worry when a problem goes away before I could understand it: I'm confident that I will have plenty of time later, when the problem magically re-appears - likely I'll be called on a Friday night :-)
Andreas Luedeke wrote: |
Hi Stefan,
since recently (a few weeks) ELOG confuses the language translations.
Individual language strings are translated into garbage; most other strings are fine.
Currently I see the string "please select" translated into "ressed" (see attached picture), instead of what's written correctly in the language file "bitte auswählen".
But with every restart the corrupted strings vary: other strings are affected and other garbage strings are shown - some of them unreadable binary code (see Attachment 2).
I have the same version running in English: I see no problems there.
Kind regards
Andreas
|
|
66126
|
Tue Dec 23 11:34:25 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2140 | Re: Problems with execute delete |
Stefan Kanitz wrote: |
i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?
|
Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix. |
66127
|
Tue Dec 23 12:17:06 2008 |
| Stefan Kanitz | skmainz@web.de | Question | Windows | 2.7.5-2140 | Re: Problems with execute delete |
Stefan Ritt wrote: |
Stefan Kanitz wrote: |
i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?
|
Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix.
|
This sounds very good! Thank you very much (Could you please add this functionality for execute edit too? Please :-))
Steve
|