*** empty log message ***

1 files changed, 27 insertions, 26 deletions

diff --git a/TODO b/TODO
index 611f83e..7b1a514 100644
--- a/TODO
+++ b/TODO
@@ -1,41 +1,34 @@
-$Id: TODO,v 1.25 1999-02-23 08:09:18 ivan Exp $
+$Id: TODO,v 1.26 1999-04-08 13:03:02 ivan Exp $
 
 If you are interested in helping with any of these, please join the mailing
 list (send a blank message to ivan-freeside-subscribe@sisd.com) to avoid 
 duplication of effort.
 
--- before 1.2b1 --
+---
 
-TEST email invoices
+javascript (yuck!) "are you sure?" confirmation on cancelations, etc.
+(view/cust_pkg and view/svc_*)
 
-one-screen new customer entry
+get rid of time2str("%D") which formats dates in a non-y2k-safe looking fashion
+(all the actual date handling uses UNIX timestamps and is fine)
 
-clean up view/cust_pkg and view/svc_* yuck (popurl and visual)!
+uncomment expire in view/cust_pkg.cgi and find the expire cron from fsold
 
-Lay out the forms a bit better.
-
-libwww regression test - since it will create sample data, can also use this
-for the web demo
-make fs-setup option to add sample data so you can click on "New Customer" right away?  so people understand what this stuff is?
-(in sample data [ AND DOCUMENT! ] all svc_acct services should have a default
- or fixed shell )
-
-(Test this)
-one-time/per-customer/? changes in rates and descriptions ('remembered
-invoices'): implement by creating a new package on the fly... but it isn't 
-associated with any agent types so it won't show up for other customers to buy.
-(but also... make sure they go away when the customer does! - need this? :
- one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
- with custnum and partpkg (like type_pkgs)
-(what happens if you hit "custom pricing" but the pricing is already custom?)
-
-update site_perl/table_template* (pry out of date)
+Lay out any remaining ugly forms better.
 
 remove "records identical" warning?  gets in the way of more important stuff.
+or fix logic which tries to update identical records??
+1.2 should be quiet enough that the error log is useful, hopefully.
 
-update web demo
+Postgres has a maximum column length of 31 characters (but see NAMEDATALEN in
+postgres_ext.h).  part_svc has columns like: svc_acct__radius_Attribute_flag
+(22 characters!)  It seems that stuff over the limit is silently ignored,
+so we get 4 characters back.  So, Radius_Attributes are max 13 characters with
+stock Postgres.  see rfc2138 for what's affected
+What's a good fix?  (besides recompiling postgres with NAMEDATALEN 64)
+(mysql has a 64 character max column length.  others?)
 
--- release 1.2b1 ---
+look at DBIx::Recordset!  (and Tie::DBI, and...)
 
 password and slipip stuff in svc_acct.pm store need to be split into two fields or something, so the silliness in svc_acct.pm and svc_acct.export with looking at the data to decide what to do with it can be fixed
 
@@ -72,7 +65,15 @@ Portability: in FS::Record, $sth->execute does not return a number of rows for a
 
 subroutine the where clause (eventually all SQL) as OO perhaps (has anyone done this?)
 
-add a select method to ?
+add a select method to FS::Record?
+
+one-time/per-customer/? changes in rates and descriptions ('remembered
+invoices'): implement by creating a new package on the fly... but it isn't 
+associated with any agent types so it won't show up for other customers to buy.
+(but also... make sure they go away when the customer does! - need this? :
+ one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
+ with custnum and partpkg (like type_pkgs)
+(what happens if you hit "custom pricing" but the pricing is already custom?)
 
 You can't delete the stuff under administration yet.  Add this,
 _including_ making sure the thing you are deleting is not in use!