| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66069
|
Fri Nov 21 18:21:36 2008 |
 | Dennis Seitz | dseitz@berkeley.edu | Question | All | latest | Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug? |
| 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. |
|
66079
|
Mon Nov 24 20:00:05 2008 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | All | latest | Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug? |
| 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:
 |
|
66080
|
Tue Nov 25 17:01:55 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Question | All | 2.7.3 | Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug? |
| 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. |
|
66102
|
Tue Dec 9 00:22:41 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Question | All | 2.7.5 | Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug? |
| 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! |
|
66103
|
Tue Dec 9 00:25:52 2008 |
 | Dennis Seitz | dseitz@berkeley.edu | Request | All | 2.7.5 | Please add Subst on Duplicate |
I would like to be able to substitute some attribute values when an entry is duplicated. I don't see Subst on Duplicate available in the cfg file syntax. Can you add that?
Thanks |
|
66104
|
Tue Dec 9 08:04:00 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.7.5 | Re: Please add Subst on Duplicate |
| Dennis Seitz wrote: |
|
I would like to be able to substitute some attribute values when an entry is duplicated. I don't see Subst on Duplicate available in the cfg file syntax. Can you add that?
|
Subst on Duplicate does not make sense. Subst always works after you submit an entry, while Preset works before you enter the entry. When you Duplicate an entry, it looks like a new one, just with attributes and text from another entry. So when you submit that one, the system cannot distinguish if you entered a new one by yourself or if this is based on a copy of another entry. So what you probably need is Preset on duplicate. |
|
66105
|
Wed Dec 10 03:11:01 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Request | All | 2.7.5 | Re: Please add Subst on Duplicate |
| Stefan Ritt wrote: |
|
| Dennis Seitz wrote: |
|
I would like to be able to substitute some attribute values when an entry is duplicated. I don't see Subst on Duplicate available in the cfg file syntax. Can you add that?
|
Subst on Duplicate does not make sense. Subst always works after you submit an entry, while Preset works before you enter the entry. When you Duplicate an entry, it looks like a new one, just with attributes and text from another entry. So when you submit that one, the system cannot distinguish if you entered a new one by yourself or if this is based on a copy of another entry. So what you probably need is Preset on duplicate.
|
Thanks for explaining.
I thought Preset would work with Duplicate since Duplicate creates a new entry, but it didn't. Then I tried Subst because Duplicating an entry opens it in Edit mode, so you are in effect Duplicating, and then Editing the entry. It just didn't occur to me to look for Preset on Duplicate. |
|
66151
|
Wed Jan 14 19:52:04 2009 |
| Yoichi Aso | asoy01@gmail.com | Question | All | 2.7.5 | Multiple keyword search |
Hi,
I have a question regarding how to perform a multiple-keyword search.
For example, when I want to find entries which contain two keywords "abc" and "def" in the body text but in an unknown order,
one way I came up with was to use a regular expression like this.
(abc|def).*(abc|def)
But this will also match entries containing two "abc" or two "def".
The following one will eliminate this problem.
(abc.*def)|(def.*abc)
But when I use more than two keywords, this type of regular expressions becomes very long (because I have to list all the permutations of the keywords) and it may not fit in the search text field (there seems to be a limit on the length of the search text).
Is there any way to allow multiple-keyword search easily ?
It would be nice if I can just enter two or more keywords separated by white spaces and elog finds entries containing all the keywords.
Thanks,
Yoichi |