Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
SELECT OPTIONs have explicitly specified VALUEs
|
|
|
|
information displays for any usage-capable export, add ability to edit uid/gid
|
|
|
|
|
|
|
|
|
|
|
|
really should have done that in the first place. JSON will wait until another day...
|
|
|
|
|
|
view package UI
|
|
|
|
|
|
|
|
redirect
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
username field (when usernamemax is not defined)
|
|
is not set)
|
|
is not set)
|
|
(package unprovisioning and cancellation, bunch of payment history stuff)
|
|
|
|
|
|
|
|
|
|
|
|
ban payinfo
|
|
|
|
|
|
selection with HTML::Widgets::SelectLayers, add Switch/Solo/Maestro support for start date & issue #. customer view: re-order fields for consistency. selfservice API: support paystart_month, paystart_year, payissue and payip in MyAccount::process_payment and ::edit_info and Signup::new_customer, FS::cust_main::realtime_bop: support paystart_month paystart_year payissue payip fields
|
|
|
|
|
|
|
|
|
|
|
|
|
|
payment_gateway_option and agent_payment_gateway tables, add paystart_month, paystart_year, payissue and payip fields to cust_main, add preliminary gateway and gateway override editing to web UI, use payment gateway override when processing payments (card type, not taxclass yet)
|
|
|
|
|
|
|