| Stefan Ritt wrote: |
| Ben Shepherd wrote: | Hi,
and it does exactly what you want. |
cool! thanks. |
Re: Re: $long_name in Moptions, posted by Stefan Ritt on Mon Nov 20 22:20:22 2006
|
| 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. |
|
Re: Re: $long_name in Moptions, posted by Fergus Lynch on Tue Nov 21 09:44:30 2006
|
| 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 |
|
Re: Re: $long_name in Moptions, posted by Fergus Lynch on Tue Nov 21 11:14:48 2006
|
| 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 |
Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug?, posted by Dennis Seitz on Fri Nov 21 18:21:36 2008
|
| Dennis Seitz wrote: |
| Stefan Ritt wrote: |
| Dennis Seitz wrote: | | Do you mean '$entry time', or did you create a new parameter? (I don't see $entry date in the elogd.cfg reference) |
Yes, of course I mean '$entry time', sorry for the misspelling. |
Well, we really appreciate the way you keep adding features and making improvements. I thought you might have slipped a new one in! |
FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit
I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.
I found that using this instead works:
Preset Last Edit =$entry time
which seems contradictory since
Subst on edit Last Edit = $date
works fine. |
Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug?, posted by Stefan Ritt on Mon Nov 24 20:00:05 2008 
|
| Dennis Seitz wrote: | FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit
I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.
I found that using this instead works:
Preset Last Edit =$entry time
which seems contradictory since
Subst on edit Last Edit = $date
works fine. |
Do you have an old version of elog? Using the current version with a configuration file:
Attributes = Author, Type, Last Edit
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Start page = ?rsort=Last Edit
I get the correct behavior:
 |
|
Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug?, posted by Dennis Seitz on Tue Nov 25 17:01:55 2008
|
| Stefan Ritt wrote: |
| Dennis Seitz wrote: | FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit
I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.
I found that using this instead works:
Preset Last Edit =$entry time
which seems contradictory since
Subst on edit Last Edit = $date
works fine. |
Do you have an old version of elog? Using the current version with a configuration file:
Attributes = Author, Type, Last Edit
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Start page = ?rsort=Last Edit
I get the correct behavior:
|
Yes, I'm using 2.7.3 - I'll try upgrading, sorry. I'll reply with the outcome. |
|
Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug?, posted by Dennis Seitz on Tue Dec 9 00:22:41 2008
|
| Dennis Seitz wrote: |
| Stefan Ritt wrote: |
| Dennis Seitz wrote: | FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit
I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.
I found that using this instead works:
Preset Last Edit =$entry time
which seems contradictory since
Subst on edit Last Edit = $date
works fine. |
Do you have an old version of elog? Using the current version with a configuration file:
Attributes = Author, Type, Last Edit
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Start page = ?rsort=Last Edit
I get the correct behavior:
|
Yes, I'm using 2.7.3 - I'll try upgrading, sorry. I'll reply with the outcome. |
Everything works fine with 2.7.5, thanks! |