Things will get too complicated if void payments are applied ad hoc
to transactions. Staff should still use the existing void interface
so that void payments will get linked to individual billings. If not,
"unvoiding" a bill becomes nearly impossibl.
Signed-off-by: Jason Stephenson <jason@sigio.com>
<!ENTITY staff.patron.bills_overlay.patron_credit.label "Patron Credit">
<!ENTITY staff.patron.bills_overlay.word.label "Work">
<!ENTITY staff.patron.bills_overlay.forgive.label "Forgive">
-<!ENTITY staff.patron.bills_overlay.void.label "Void">
<!ENTITY staff.patron.bills_overlay.goods.label "Goods">
<!ENTITY staff.patron.bills_overlay.payment_received.value "Payment received">
<!ENTITY staff.patron.bills_overlay.payment_received.accesskey "a">
<menuitem id="payment_type_menuitem4" class="hide_patron_credit" label="&staff.patron.bills_overlay.patron_credit.label;" value="credit_payment" />
<menuitem id="payment_type_menuitem5" class="hide_patron_work" label="&staff.patron.bills_overlay.word.label;" value="work_payment"/>
<menuitem id="payment_type_menuitem6" class="hide_patron_forgive" label="&staff.patron.bills_overlay.forgive.label;" value="forgive_payment"/>
- <menuitem id="payment_type_menuitem7" class="hide_patron_void" label="&staff.patron.bills_overlay.void.label;" value="void_payment"/>
- <menuitem id="payment_type_menuitem8" class="hide_patron_goods" label="&staff.patron.bills_overlay.goods.label;" value="goods_payment"/>
+ <menuitem id="payment_type_menuitem7" class="hide_patron_goods" label="&staff.patron.bills_overlay.goods.label;" value="goods_payment"/>
</menupopup>
</menulist>
</row>