| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66106
|
Thu Dec 11 03:13:31 2008 |
 | Dennis Seitz | dseitz@berkeley.edu | Bug report | Mac OSX | 2.7.5 | Attribute value lost when adding to another extendable attribute |
Here is an excerpt from my config file:
Type Last Edit = datetime
Preset Last Edit =$entry time
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Preset on Duplicate Last Edit = $date
I have another attribute called Part that I've made extendable.
When I duplicate an entry, Last Edit is updated with the current date correctly. However, as soon as I click the Add Part button next to my extendable Part attribute, and the page reloads to show the entry box for the Part field, the Last Entry field is replaced with a "-".
I have to submit and then re-edit the entry to get Last Edit to have a valid value again.
*EDIT*:
I noticed that any time the page reloads while in the entry screen this happens, e.g. by selecting plain instead of html format.
|
|
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. |
|
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. |
|
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 |
|
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! |
|
66101
|
Mon Dec 8 13:13:13 2008 |
| Steve Williamson | StephenWilliamson@Barnsley.gov.uk | Bug report | Linux | 2.7.5 | Re: Auto-increment attributes |
| Stefan Ritt wrote: |
|
I finally found some time to address this problem. It is indeed related to the fact that the new number gets assigned when you click on 'New'. So if two people edit the new entries at the same time, they get assigned the same number. To fix this problem, I made the tag generation work with the 'Subst' command, which is evaluated at the entry submission, and not when you click on 'New'. So to make this work, you need to upgrade to SVN revision 2152 and then put into your configuration file:
Attributes = Author, RFC, Subject
Preset RFC = <will be assigned when you submit>
Preset on duplicate RFC = <will be assigned when you submit>
Locked attributes = RFC Subst RFC = RFC-######
I also changed the documentation accordingly.
|
Stefan
Thanks for fix - I've just tested it and it works beautifully.
regards
Steve
|
|
66100
|
Mon Dec 8 10:09:14 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.5 | Re: Auto-increment attributes |
I finally found some time to address this problem. It is indeed related to the fact that the new number gets assigned when you click on 'New'. So if two people edit the new entries at the same time, they get assigned the same number. To fix this problem, I made the tag generation work with the 'Subst' command, which is evaluated at the entry submission, and not when you click on 'New'. So to make this work, you need to upgrade to SVN revision 2152 and then put into your configuration file:
Attributes = Author, RFC, Subject
Preset RFC = <will be assigned when you submit>
Preset on duplicate RFC = <will be assigned when you submit>
Locked attributes = RFC Subst RFC = RFC-######
I also changed the documentation accordingly. |
|
66099
|
Mon Dec 8 08:59:56 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Other | 2.7.5-2143 | Re: Change background color |
| mike cianci wrote: |
|
I copied the following line from the ELOG documentation file to my config file (with the appropriate changes to the attribute and value fields) and nothing happens. Am I missing something?
Style importance severe = background-color:red
Thanks for all your help.
|
Just the "usual candidates":
- Any typo?
- Edited the wrong file?
- Must send a HUP signal to elogd if running under linux
- Note that the style changes only in the list display
I just tried with a minimal configuration file:
[demo]
Attributes = Author, Importance, Subject
Options Importance = normal, severe
Style Importance severe = background-color:red
and it just worked fine:
|