ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66167
|
Mon Jan 26 14:07:02 2009 |
| Robert-Jan Schrijvers | Robert-Jan.Schrijvers@isoft.nl | Question | Windows | V2.6.3 | Default value radio button |
hi there,
Is it possible to attach a default value for a radio button when submitting a new form/record, for example:
I now have an item "Confirmed" Yes/No, and I want the "no" option to be selected by default when a new form/record is created.
Does anyone know how to arrange this?
Thanks in advance!
RJ
|
66174
|
Tue Jan 27 08:06:54 2009 |
| Robert-Jan Schrijvers | Robert-Jan.Schrijvers@isoft.nl | Question | Windows | V2.6.3 | Re: Default value radio button |
Stefan Ritt wrote: |
Robert-Jan Schrijvers wrote: |
Is it possible to attach a default value for a radio button when submitting a new form/record, for example:
I now have an item "Confirmed" Yes/No, and I want the "no" option to be selected by default when a new form/record is created.
Does anyone know how to arrange this?
Thanks in advance!
|
You need something along these lines:
Attributes = ..., Confirmed
Options Confirmed = boolean
Preset Confirmed = 1
|
Good Morning Stefan,
This was very helpful, it works as aspected! Thank you :-)
With regards, Robert-Jan. |
66532
|
Tue Sep 8 10:46:22 2009 |
| Robert-Jan Schrijvers | Robert-Jan.Schrijvers@isoft.nl | Bug report | Windows | 2.3.9 | Use eLOG with Google Chrome |
Hi Stephan,
one of the eLOG users at our company, has problems using eLOG in combination with Google Chrome (version 2.0.172.43), log in gives no problem, when selecting the appropiate department, he get's the following error:
Technical Information (for support personnel)
- Error Code: 502 Proxy Error. The ISA Server denied the specified Uniform Resource Locator (URL). (12202)
- IP Address: 130.78.137.1
- Date: 8-9-2009 07:13:55 [GMT]
- Server: NLISA1.top.local
- Source: proxy
This problem does not appear with other browsers like IE7/8 and Firefox.
Do you have any clue?
Tnx in advance.
kind regards, RJ Schrijvers. |
66533
|
Tue Sep 8 10:46:46 2009 |
| Robert-Jan Schrijvers | Robert-Jan.Schrijvers@isoft.nl | Bug report | Windows | 2.3.9 | Use eLOG with Google Chrome |
Hi Stephan,
one of the eLOG users at our company, has problems using eLOG in combination with Google Chrome (version 2.0.172.43), log in gives no problem, when selecting the appropiate department, he get's the following error:
Technical Information (for support personnel)
- Error Code: 502 Proxy Error. The ISA Server denied the specified Uniform Resource Locator (URL). (12202)
- IP Address: 130.78.137.1
- Date: 8-9-2009 07:13:55 [GMT]
- Server: NLISA1.top.local
- Source: proxy
This problem does not appear with other browsers like IE7/8 and Firefox.
Do you have any clue?
Tnx in advance.
kind regards, RJ Schrijvers. |
66534
|
Tue Sep 8 10:47:08 2009 |
| Robert-Jan Schrijvers | Robert-Jan.Schrijvers@isoft.nl | Bug report | Windows | 2.6.3-1762 | Use eLOG with Google Chrome |
Hi Stefan,
one of the eLOG users at our company, has problems using eLOG in combination with Google Chrome (version 2.0.172.43), log in gives no problem, when selecting the appropiate department, he get's the following error:
Technical Information (for support personnel)
- Error Code: 502 Proxy Error. The ISA Server denied the specified Uniform Resource Locator (URL). (12202)
- IP Address: 130.78.137.1
- Date: 8-9-2009 07:13:55 [GMT]
- Server: NLISA1.top.local
- Source: proxy
This problem does not appear with other browsers like IE7/8 and Firefox.
Do you have any clue?
Tnx in advance.
kind regards, RJ Schrijvers.
sorry for the inconviniance, we have a later version of eLOG. |
67032
|
Wed Mar 23 10:01:01 2011 |
| Olivier Callot | Olivier.Callot@cern.ch | Bug report | Linux | 2.9.0 | Mail are no longer sent from the logged in user in 2.9.0 |
We upgraded to Elog 2.9.0-2402 and since then mails sent by Elog when posting an item are from the default account, not from the logged in user's mail address.
The configuration is, for the mail part :
Default Email From = Olivier.Callot@cern.ch
Use Email Subject = ELOG Computing Operations - $Subject ($Site - $System - $Production number)
Thanks for telling me which flag/option I have to set to restore the proper mail 'From:' field. |
67047
|
Wed Apr 13 10:51:34 2011 |
| Olivier Callot | Olivier.Callot@cern.ch | Bug report | All | 2.9.0 | Self Register = 3 doesn't work any longer |
With the recent Elog 2.9.0 rev 2412 the Self Register = 3 option doesn't work as expected: The user is immediately allowed to login. This is not what this option was doing, which is to wait for an approval by the administrator. Can this behaviour be restored, or should I change the value of the Self Register flag? Thanks |
67050
|
Fri Apr 15 11:49:43 2011 |
| Olivier Callot | Olivier.Callot@cern.ch | Bug report | All | 2.9.0 | Re: Self Register = 3 doesn't work any longer |
Stefan Ritt wrote: |
Olivier Callot wrote: |
With the recent Elog 2.9.0 rev 2412 the Self Register = 3 option doesn't work as expected: The user is immediately allowed to login. This is not what this option was doing, which is to wait for an approval by the administrator. Can this behaviour be restored, or should I change the value of the Self Register flag? Thanks
|
Are you sure about that (maybe used an older revision of elogd where this indeed was a problem?). The current V2.9.0-2412 gives me this:
If I then log in as the admin user, I see the configuration of the new user, but the account is not activated:
So the user cannot log in. The config file is:
[global]
port = 8080
password file = passwd
smtp host = mail.psi.ch
Self register = 3
Admin user = stefan
[demo1]
Attributes = Project, Category
Can you double check?
|
HI Stefan,
I tried again and confirm the version number. I never got this pannel saying that my request will be processed by an adminstrator. Maybe the installation was incomplete? Is this pannel outside the standard src files? I receive the mail as administrator, but the accout is already valid BEFORE I validate it.
This was working in previous versions, i.e. the entry was not created at all. And login wasn't possible.
We went back to 2.8.0 as the server is regularly crashing with 2.9.0 and we have to keep it alive for our running experiment. We are trying to isolate and reproduce the problem... |