ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
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. |
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. |
66108
|
Fri Dec 12 07:45:14 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 2.7.5-2140 | Re: Conflict between Select-Edit and attribute types |
Richard Stamper wrote: |
When doing a Select->Edit operation, if an attribute has a type of "numeric" and the records selected already have (some) values for that attribute, then the "- keep original values -" message that is inserted to indicate that the values should be preserved causes the type check to fail.
Would it be possible to modify the Javascript that carries out the type check to treat the "- keep original values -" message as an exception?
|
Thanks for reporting this. It has been fixed in SVN revision 2155. The fix will be contained in the next release. |
66109
|
Fri Dec 12 08:07:59 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Mac OSX | 2.7.5 | Re: Attribute value lost when adding to another extendable attribute |
Dennis Seitz wrote: |
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.
|
Thanks for reporting that problem. It has been fixed in SVN revision 2156. |
66111
|
Fri Dec 12 09:16:19 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | latest | Re: mysql in execute |
Stefan Kanitz wrote: |
This doesn't work:
Execute new = mysql -h localhost -u root -D test1 -e "insert into `test2` (Autor, Adressat, Teil1, Teil2, Teil3,
Teil4, Teil5, Teil6, Teil7, Teil8 ) values ('$Autor', '$Adressat' , '$Teil1', '$Teil2', '$Teil3', '$Teil4', '$Teil5',
'$Teil6', '$Teil7', '$Teil8' )"
|
In the elogd.cfg file, you cannot have multi-line options. Either you put everything on a single line (I guess there is also some limit at a few hundred characters) or you call a batch file which then calls the mysql command. |
66115
|
Mon Dec 15 09:01:35 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2140 | Re: Grouping Logbooks |
mike cianci wrote: |
I really appreciate your help and I hope that my questions warrant your time.
What I am trying to accomplish is two totally separate groups of logbooks that share a common logbook.
Three logbooks
Logbook A
Logbook B
Logbook C (just informational, write protected)
Two Groups
Top Group 1 = Logbook A, Logbook C
Top Group 2 = Logbook B, Logbook C
What is happening is everything looks good until you try to enter Logbook C from Group 1. You end up in Logbook C (the right logbook) but you are now in Group 2.
Actual Code:
;Groupings
Top Group Central = Centaur, On-LineHelps
Top Group Good Sam = GSH, On-LineHelps
|
You cannot put the same logbook into two groups. All you can do is to define two logbooks C1 and C2, and force their data directories to be the same (via the "Subdir = ..." directive), so they will actually look at the same data. |
66118
|
Thu Dec 18 10:39:57 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.3 | Re: deadc0de |
Eoin Butler wrote: |
I'm also having this problem.
It's reproducible, It happens if I try to view a certain entry (or the main list page when that entry is near the top), but goes away when I remove the datafile for that entry.
The file is quite large, since it contains several long entries in HTML encoding with some tables and stuff.
|
The problem is related to the long entries. It has already been fixed in revision 2141 last month. So please upgrade to the current version. |
66120
|
Thu Dec 18 11:51:07 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.3 | Re: deadc0de |
Eoin Butler wrote: |
Stefan Ritt wrote: |
Eoin Butler wrote: |
I'm also having this problem.
It's reproducible, It happens if I try to view a certain entry (or the main list page when that entry is near the top), but goes away when I remove the datafile for that entry.
The file is quite large, since it contains several long entries in HTML encoding with some tables and stuff.
|
The problem is related to the long entries. It has already been fixed in revision 2141 last month. So please upgrade to the current version.
|
I already tried this. I'm using 2156 (latest from SVN) and no joy.
|
Well, then I need yoru data file to reproduce the problem here. |
|