ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66114
|
Sun Dec 14 17:04:24 2008 |
| mike cianci | mike2.cianci@comcast.net | Question | Windows | 2.7.5-2140 | Grouping Logbooks |
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
|
66113
|
Sat Dec 13 14:31:53 2008 |
| Stefan Kanitz | skmainz@web.de | Question | Windows | latest | Re: mysql in execute |
Stefan Ritt wrote: |
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.
|
Thanks!
|
66112
|
Sat Dec 13 02:13:51 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Bug report | Mac OSX | 2.7.5 | Re: Attribute value lost when adding to another extendable attribute |
Stefan Ritt wrote: |
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.
|
Excellent! Thank you. |
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. |
66110
|
Fri Dec 12 08:57:41 2008 |
| Stefan Kanitz | skmainz@web.de | Question | Windows | latest | mysql in execute | Hello all,
i have a question to mysql inexecute:
This works:
Execute new = mysql -h localhost -u root -D test1 -e "insert into `test1` (author, type) values ('$Author', '$Type')"
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' )"
db is okay, i have all checked this. My question is: can the execute-command take a multiline argument? Or perhaps does somebody see a mistake i have made in the execute-line?
Thanks!
Steve
|
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. |
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. |
66107
|
Thu Dec 11 17:50:35 2008 |
| Richard Stamper | r.stamper@rl.ac.uk | Request | Windows | 2.7.5-2140 | Conflict between Select-Edit and attribute types | 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? |
|