| 2011-12-07 19:23:57 |
James Fournie |
bug |
|
|
added bug |
| 2011-12-07 19:24:09 |
James Fournie |
tags |
|
acq invoicing |
|
| 2011-12-07 19:30:22 |
James Fournie |
tags |
acq invoicing |
acq invoicing pullrequest |
|
| 2011-12-07 19:30:52 |
James Fournie |
description |
Sometimes invoices will hang when you attempt to save them.
To recreate this problem, you can do something like the following:
1. Add a prorateable charge to an invoice
2. Save invoice and reopen
3. Add another prorateable charge and delete the first one, then click Save again
This or similar actions can cause the system to hang.
This appears to be caused when there are invoice charges that are deleted but aren't attached to any fund_debit. This is expected for a prorateable charge as the charge will be prorated to multiple funds.
When deleting a charge, the system expects a fund_debit to be assigned so that it can delete the debit, however in this case there is no debit, and the system returns an (unhandled in Javascript) error. Instead, we should check for a fund_debit value -- if none is found then we can generally assume that we don't need to remove any debits. |
Sometimes invoices will hang when you attempt to save them.
To recreate this problem, you can do something like the following:
1. Add a prorateable charge to an invoice
2. Save invoice and reopen
3. Add another prorateable charge and delete the first one, then click Save again
This or similar actions can cause the "Save" action to hang (actually it is returning an error but this is unhandled and the user gets a perpetual progress dialog)
This appears to be caused when there are invoice charges that are deleted but aren't attached to any fund_debit. This is expected for a prorateable charge as the charge will be prorated to multiple funds.
When deleting a charge, the system expects a fund_debit to be assigned so that it can delete the debit, however in this case there is no debit, and the system returns an (unhandled in Javascript) error. Instead, we should check for a fund_debit value -- if none is found then we can generally assume that we don't need to remove any debits. |
|
| 2011-12-21 22:56:36 |
James Fournie |
nominated for series |
|
evergreen/2.0 |
|
| 2011-12-21 22:56:36 |
James Fournie |
nominated for series |
|
evergreen/2.1 |
|
| 2011-12-21 22:56:36 |
James Fournie |
nominated for series |
|
evergreen/2.2 |
|
| 2011-12-21 22:56:36 |
James Fournie |
nominated for series |
|
evergreen/master |
|
| 2011-12-22 17:02:51 |
James Fournie |
description |
Sometimes invoices will hang when you attempt to save them.
To recreate this problem, you can do something like the following:
1. Add a prorateable charge to an invoice
2. Save invoice and reopen
3. Add another prorateable charge and delete the first one, then click Save again
This or similar actions can cause the "Save" action to hang (actually it is returning an error but this is unhandled and the user gets a perpetual progress dialog)
This appears to be caused when there are invoice charges that are deleted but aren't attached to any fund_debit. This is expected for a prorateable charge as the charge will be prorated to multiple funds.
When deleting a charge, the system expects a fund_debit to be assigned so that it can delete the debit, however in this case there is no debit, and the system returns an (unhandled in Javascript) error. Instead, we should check for a fund_debit value -- if none is found then we can generally assume that we don't need to remove any debits. |
Sometimes invoices will hang when you attempt to save them.
To recreate this problem, you can do something like the following:
1. Add a prorateable charge to an invoice
2. Save invoice and reopen
3. Add another prorateable charge and delete the first one, then click Save again
This or similar actions can cause the "Save" action to hang (actually it is returning an error but this is unhandled and the user gets a perpetual progress dialog)
This appears to be caused when there are invoice charges that are deleted but aren't attached to any fund_debit. This is expected for a prorateable charge as the charge will be prorated to multiple funds.
When deleting a charge, the system expects a fund_debit to be assigned so that it can delete the debit, however in this case there is no debit, and the system returns an (unhandled in Javascript) error. Instead, we should check for a fund_debit value -- if none is found then we can generally assume that we don't need to remove any debits.
I should add that this bug was reported initially in 2.0.5 on Ubuntu with PG 8.4 but I'm fairly certain I've found this to be the problem and the problem code persists through to master. |
|
| 2012-01-20 20:54:52 |
Bill Erickson |
evergreen: assignee |
|
Bill Erickson (erickson-esilibrary) |
|
| 2012-01-20 20:54:54 |
Bill Erickson |
evergreen: status |
New |
In Progress |
|
| 2012-01-20 21:01:40 |
Bill Erickson |
bug task added |
|
evergreen/2.0 |
|
| 2012-01-20 21:01:47 |
Bill Erickson |
bug task added |
|
evergreen/2.1 |
|
| 2012-01-20 21:01:55 |
Bill Erickson |
bug task added |
|
evergreen/master |
|
| 2012-01-20 21:02:02 |
Bill Erickson |
bug task added |
|
evergreen/2.2 |
|
| 2012-01-20 21:02:11 |
Bill Erickson |
evergreen/2.0: status |
New |
Fix Committed |
|
| 2012-01-20 21:02:14 |
Bill Erickson |
evergreen/2.1: status |
New |
Fix Committed |
|
| 2012-01-20 21:02:16 |
Bill Erickson |
evergreen/2.2: status |
New |
Fix Committed |
|
| 2012-01-20 21:02:19 |
Bill Erickson |
evergreen/master: status |
In Progress |
Fix Committed |
|
| 2012-01-20 21:02:22 |
Bill Erickson |
evergreen/master: milestone |
|
2.2.0alpha2 |
|
| 2012-01-20 21:02:28 |
Bill Erickson |
evergreen/2.2: milestone |
|
2.2.0alpha2 |
|
| 2012-01-20 21:02:33 |
Bill Erickson |
evergreen/2.1: milestone |
|
2.1.2 |
|
| 2012-01-20 21:02:39 |
Bill Erickson |
evergreen/2.0: milestone |
|
2.0.12 |
|
| 2012-03-08 22:18:17 |
Jason Stephenson |
bug task deleted |
evergreen/2.2 |
|
|
| 2012-03-08 22:18:28 |
Jason Stephenson |
evergreen/master: status |
Fix Committed |
Fix Released |
|
| 2012-04-28 18:21:55 |
Jason Stephenson |
evergreen/2.0: milestone |
2.0.12 |
2.0.11 |
|
| 2012-05-14 19:33:57 |
Jason Stephenson |
evergreen/2.0: status |
Fix Committed |
Fix Released |
|
| 2012-06-21 16:59:00 |
Jason Stephenson |
evergreen/2.1: status |
Fix Committed |
Fix Released |
|
