ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
2090
|
Fri Nov 24 14:40:42 2006 |
| Stephane LE | stephane.le@synchrotron-soleil.fr | Question | All | | Re: How to do a preset on MOptions attributes ? |
easy...
Preset MyAttribute = choice1 | choice2 | choice3 |
2089
|
Fri Nov 24 11:01:22 2006 |
| Stephane LE | stephane.le@synchrotron-soleil.fr | Question | All | | How to do a preset on MOptions attributes ? |
Hi,
I'm new to elog and I was wondering if it is possible to do some presets on MOptions attributes when displaying a new form ? I've read the elogd config page but couldn't find how to do it.
Thanks for your help,
stephane |
2088
|
Wed Nov 22 02:55:48 2006 |
| Rob Mahurin | rob@utk.edu | Comment | Linux | 2.5.7-1 | Re: Securing Elog with SSL and Apache |
Hi,
I am an apache ignoramus who has been trying to follow these instructions on a Debian 3.1 box. I got hung up for
the following reason. I had to explicitly enable some apache features, which was a simple matter of making the
following symlinks in /etc/apache2/mods-enabled:
proxy.conf -> ../mods-available/proxy.conf
proxy.load -> ../mods-available/proxy.load
rewrite.load -> ../mods-available/rewrite.load
headers.load -> ../mods-available/headers.load
ssl.conf -> ../mods-available/ssl.conf
ssl.load -> ../mods-available/ssl.load
Easy enough. The default proxy.conf has sensible-looking warnings about not running your server as an open proxy.
However, I wasn't able to tweak it to encrypted port forwarding from :443 to :8079.
What I've done that works is to add a local proxy section to the /etc/apache2/conf.d/elogredirect.conf by Damon
Nettles:
<VirtualHost *:443>
### ... everything else
<Proxy *>
Allow from all
</Proxy>
</VirtualHost>
I think, since this is in a subsection, that it only affects that virtual host. But it'd be nice if someone who
actually understands this language would reassure me that I'm not setting myself up for some security hole. At
any rate it took me long enough to figure this out that I thought I'd post a note in public, and this seems like
the forum to do so.
Thanks.
Rob |
2087
|
Tue Nov 21 11:14:48 2006 |
| Fergus Lynch | flynch@alternativenetworks.com | Question | Windows | 2.6.2-1734 | Re: Re: $long_name in Moptions |
Stefan Ritt wrote: |
Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
Hi Stefan, apologies if I am being a bit dense (!) When I download the latest windows binary it extracts to ELOG V2.6.2-1749. Where could I get revision 1758 >
Thanks in advance
Fergus |
2086
|
Tue Nov 21 09:44:30 2006 |
| Fergus Lynch | flynch@alternativenetworks.com | Question | Windows | 2.6.2-1734 | Re: Re: $long_name in Moptions |
Stefan Ritt wrote: |
Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
WowThat was quick, I'll implement this morning. Many thanks for introducing this, ELOG is such a good tool.
Many Thanks
Fergus |
2085
|
Mon Nov 20 22:20:22 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.2-1734 | Re: Re: $long_name in Moptions |
Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
2084
|
Mon Nov 20 16:23:37 2006 |
| Fergus Lynch | flynch@alternativenetworks.com | Question | Windows | 2.6.2-1734 | $long_name in Moptions |
Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list.
Thanks
Fergus |
2083
|
Sat Nov 18 17:13:22 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Attributes according to users |
ather khan wrote: | Hi,
Is it possible to have certain attributtes available to certain user in one log boolk.
We have log book where the supervisor assign jobs to employees and we want only supervisor to have assign to attributes available and others only to view it.
|
You cannot restrict the modification if certain attributes, but you can restrict edits in general with the command
Allow edit = <name of admin>
You can also restrict the New, Delete, etc. commands to be only executable by the supervisor. |