Modified effective dates to be part of the ledger entry, not the transaction. This is the logically correct way, as a transaction is simply a collection of entries which might be anywhere from completely aligned to totally disjoint from one another (more likely the former). As a practical example, consider a move-in invoice, with security deposit (effective immediately with no end date), a prorated rent (effective move-in day through the end of the first month), and first full months rent (effective beginning of next month through the end of next month). There is certainly more work to be done on this, and testing was minimal. It does seem to be functioning though, so I'm checking in.

git-svn-id: file:///svn-source/pmgr/branches/invoice_receipt_20090629/site@256 97e9348a-65ac-dc4b-aefc-98561f571b83

controllers/ledger_entries_controller.php

@@ -298,9 +298,7 @@ class LedgerEntriesController extends AppController {
 				'Lease.id',
 				),
 
-	     'fields' => array('LedgerEntry.id',
-			       'LedgerEntry.amount',
-			       'LedgerEntry.comment'),
+	     'fields' => array('LedgerEntry.*'),
 
 	     'conditions' => array('LedgerEntry.id' => $id),
 	     ));