Re: MOptions problem ?, posted by Alex H on Tue Feb 28 11:26:22 2006
|
> Hi Holger,
>
> > Which ELOG version do you use?
> I'am using the version V2.6.1-1653 of Elog
>
> > From which logbook are the screenshots? (I assume it's Liste - right?)
> Right :)!
>
> I've just seen that Stefan has build a V2.6.1-1663 version of ELOG.
> I try to install this new version and gave you answer as soon as possible :)!
Now I'am using the Elog V2.6.1-1668 and same probleme.
I think it's a data problem. I have edited my logbooks\Liste\050302a.log with an Hexadecimal editor and found one
carruage return juste before the |
[SOLVED] Re: MOptions problem ?, posted by Alex H on Tue Feb 28 12:08:42 2006
|
Yop,
I think I found the solution! I was in fact a conditions conflict!
See the attached picture for easiest comprehension.
My list box type's conditions (FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}) conflict with my Equipment's conditions. It seems that the condition ID must be unique across the whole elogd.cfg.
So I have replaced my "Options Type = FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}"
by : "Options Type = FWL1{101}, FWL2{102}, FWL4{103}, VPN1{104}, VPN2{105}, CLIVPN-PROC"
and it works well ! |
[SOLVED] Re: MOptions problem ?, posted by Stefan Ritt on Wed Mar 1 07:48:11 2006
|
Alex H wrote: | It seems that the condition ID must be unique across the whole elogd.cfg. |
Right. Here is a quote from the Manual:
ELOG Manual wrote: | The only requiremnt is that conditions are unique, meaning that a condition in one option list cannot be used in another list. |
So just read the manual  |
Re: list view mode remembert - Bug?, posted by Stefan Ritt on Wed Mar 1 07:55:42 2006
|
> As default http://<hostname>/<LOGBOOK> shows the Summary View.
> Clicking in "Full" changes the URL to http://<hostname>/<LOGBOOK>/?mode=full.
> But now the URL http://<hostname>/<LOGBOOK> show the Full view as default.
> I think the URL without ?mode=... should show every time the same result,
> regardless the view used before. Or maybe I can configure, which view I want to
> see if I use the URL w/o ?mode=... The option to hide/show attachments is affected too.
Sure, that's a feature :D
It was requested by several people that the view mode is stored in a cookie. So if you switch modes, it should be
persistent. If I now add additional default flags, people will have hard time to understand what this is all
about, since there might then be conflicting settings between the flags and the cookies. So for what exact purpose
do you want what you requested? Why does it bother you that you have to click "Summary" again to get the summary
view? Of course you can delete the local cookies and get the default behaviour (they are named [b]elmode[/b] and
[b]elattach[/b]), but that might be a bit cumbersome. |
Re: How to setup Change attributes in detail view/edit mode ?, posted by Stefan Ritt on Wed Mar 1 10:30:51 2006
|
I implemented a "Hide attributes = ..." option, with which you can do what you requested, but unfortunately I'm
sitting here in Siberia and have only limited internet access, so I can only submit the modification next weekend.
- Stefan |
[SOLVED] Re: list view mode remembert - Bug?, posted by Holger Mundhahs on Wed Mar 1 12:27:36 2006
|
> > As default http://<hostname>/<LOGBOOK> shows the Summary View.
> > Clicking in "Full" changes the URL to http://<hostname>/<LOGBOOK>/?mode=full.
> > But now the URL http://<hostname>/<LOGBOOK> show the Full view as default.
> > I think the URL without ?mode=... should show every time the same result,
> > regardless the view used before. Or maybe I can configure, which view I want to
> > see if I use the URL w/o ?mode=... The option to hide/show attachments is affected too.
>
> Sure, that's a feature :D
>
> It was requested by several people that the view mode is stored in a cookie. So if you switch modes, it should be
> persistent. If I now add additional default flags, people will have hard time to understand what this is all
> about, since there might then be conflicting settings between the flags and the cookies. So for what exact purpose
> do you want what you requested? Why does it bother you that you have to click "Summary" again to get the summary
> view? Of course you can delete the local cookies and get the default behaviour (they are named [b]elmode[/b] and
> [b]elattach[/b]), but that might be a bit cumbersome.
Thank you for your explanation. My situation was, that I've played around with "Mode commands = 0". In normal case I
use the Summary view, but on one logbook I've changed it to Full before, and after setting the parameter I can't
revert it to Summary. But now I know how it works and can use it like intended.
Regards
Holger |
Change in encoding close entry, posted by Holger Mundhahs on Mon Apr 3 10:32:45 2006
|
Maybe it is a wrong configuration, because in this forum it works well.
If I change the encoding in the logbook entry I get "Submit modified ELOG entry?",
and after clicking OK the entry is closed. Because this behavior is on all loggbooks
it must be a global config entry, but I dont know, which.
Here is the GLOBAL section:
Expand Selection page = 1
URL = http://sapelogs/
Date Format = %d.%m.%Y
Time Format = %d.%m.%Y %H:%M
Reverse Sort = 1
Menu commands = New, Edit, Delete, Reply, Download, Find, Last day, Last 10, Select, Copy to, Config, Admin,
Login, Logout, Help
Find Menu commands = New, Edit, Delete, Reply, Download, Find, Last day, Last 10, Select, Config, Admin, Login,
Logout
Password file = passwords.txt
Login expiration = 2
Admin user = ME
Suppress Email to users = 1
Self register = 0
Logout to main = 1
admin textarea = 150,45
Entries per page = 100
Mode commands = 1
Use Lock = 1
Supress Email on edit = 1
Supress default = 1
Summary lines = 1
Icon comment log.gif = Allg. Log
.....
Group SAP = ..... |
Re: Change in encoding close entry, posted by Stefan Ritt on Mon Apr 3 10:35:37 2006
|
> Maybe it is a wrong configuration, because in this forum it works well.
> If I change the encoding in the logbook entry I get "Submit modified ELOG entry?",
> and after clicking OK the entry is closed. Because this behavior is on all loggbooks
> it must be a global config entry, but I dont know, which.
>
> ...
> Use Lock = 1
> ...
I comes from using the lock. If you remove that, you won't get this dialog box any more. |
|