1 $Id: TODO,v 1.30 1999-04-14 13:14:54 ivan Exp $
3 If you are interested in helping with any of these, please join the mailing
4 list (send a blank message to ivan-freeside-subscribe@sisd.com) to avoid
9 default (and ordering) state/county/country config file
11 cust_main_county table to provide a preferred ordering, so the most common
12 entries would be at the top of the selection box. automatically, based on
15 hmm... maybe svc_acct__shell should check off the legal shells list if
16 applicable? yeah... cool.
18 payinfo field should me much larger than 16
21 [Mon Apr 12 20:31:21 1999] [error] [Mon Apr 12 20:31:21 1999] null: Error closing true: Broken pipe at /usr/local/lib/site_perl/FS/cust_main.pm line 615.
23 javascript (yuck!) "are you sure?" confirmation on cancelations, etc.
24 (view/cust_pkg and view/svc_*)
26 get rid of time2str("%D") which formats dates in a non-y2k-safe looking fashion
27 (all the actual date handling uses UNIX timestamps and is fine)
29 uncomment expire in view/cust_pkg.cgi and find the expire cron from fsold
32 one-time/per-customer/? changes in rates and descriptions ('remembered
33 invoices'): implement by creating a new package on the fly... but it isn't
34 associated with any agent types so it won't show up for other customers to buy.
35 (but also... make sure they go away when the customer does! - need this? :
36 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
37 with custnum and partpkg (like type_pkgs)
38 (what happens if you hit "custom pricing" but the pricing is already custom?)
40 Lay out any remaining ugly forms better.
42 remove "records identical" warning? gets in the way of more important stuff.
43 or fix logic which tries to update identical records??
44 1.2 should be quiet enough that the error log is useful, hopefully.
46 Postgres has a maximum column length of 31 characters (but see NAMEDATALEN in
47 postgres_ext.h). part_svc has columns like: svc_acct__radius_Attribute_flag
48 (22 characters!) It seems that stuff over the limit is silently ignored,
49 so we get 4 characters back. So, Radius_Attributes are max 13 characters with
50 stock Postgres. see rfc2138 for what's affected
51 What's a good fix? (besides recompiling postgres with NAMEDATALEN 64)
52 (mysql has a 64 character max column length. others?)
54 [Mon Mar 29 06:57:56 1999] -e: Use of uninitialized value at /usr/lib/perl5/Date/Format.pm line 333.
55 (when sending mail in cust_main.pm::bill or svc_domain.pm)
57 look at DBIx::Recordset! (and Tie::DBI, and...)
59 undefined conf/lpr gives this uninfomative error:
60 [Fri Feb 26 16:42:36 1999] bill.cgi: Can't do bidirectional pipe at
62 l5/site_perl/FS/cust_main.pm line 629.
63 [Fri Feb 26 16:42:38 1999] bill.cgi: Error closing : Broken pipe at
65 l5/site_perl/FS/cust_main.pm line 631.
66 So give a meaningful error!
68 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
70 i10n: Apache::Language
72 Apache::Session? Other useful Apache::* ?
74 email invoices are only sent for the BILL payby. If setup, should statements
75 (since they're not invoices) be sent for COMP and CARD as well?
77 $cgi->keywords is causing the (hard to trace) error:
78 Use of uninitialized value at (eval 5) line 5
80 edit/cust_main.cgi gives an uninformative error message:
81 > Can't call method "agentnum" without a package or object reference at
82 > /usr/local/apache-ssl/htdocs/freeside/edit/cust_main.cgi line 116.
83 if there are no agents.
85 (is this missing on any web screens? (easy with $cust_svc->label)
86 Add the ability for services to filter information up to the package level
87 for web screens, so you can select a particlar package based
88 on username or domain name, etc.
90 Allow a cancelled/suspended/active status from packages to bubble up to
91 the customer lists. Put active, then suspended, then cancelled accounts.
92 Similar ordering on the package listing inside a single customer.
94 false laziness: edit/cust_main.cgi got some parts copied from edit/svc_acct.cgi
95 the web interface in general needs to be redone in a more abstract way.
97 false laziness: some of search/svc_acct_sm.cgi was copied to search/svc_domain.cgi. but web interface in general needs to be rewritten in a mucho cleaner way.
99 Portability: in FS::Record, $sth->execute does not return a number of rows for all DBD's. see man DBI
101 subroutine the where clause (eventually all SQL) as OO perhaps (has anyone done this?)
103 add a select method to FS::Record?
105 one-time/per-customer/? changes in rates and descriptions ('remembered
106 invoices'): implement by creating a new package on the fly... but it isn't
107 associated with any agent types so it won't show up for other customers to buy.
108 (but also... make sure they go away when the customer does! - need this? :
109 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
110 with custnum and partpkg (like type_pkgs)
111 (what happens if you hit "custom pricing" but the pricing is already custom?)
113 You can't delete the stuff under administration yet. Add this,
114 _including_ making sure the thing you are deleting is not in use!
116 add links on view/cust_main.cgi to setup services, like view/cust_pkg.cgi
118 FS::cust_pkg _require_'s FS::$svc, but this won't work with %FS::UID::callback
119 loading of configuration. (pry need same idea, but will run immediately if
120 context allows). Looks like error is masked by 'use FS::cust_svc' which in
121 turn 'use's FS::{svc_acct, svc_acct_sm, svc_domain}' which is now explicit
124 Allow a cancelled/suspended/active status from packages to bubble up to
125 the customer lists. Put active, then suspended, then cancelled accounts.
126 Similar ordering on the package listing inside a single customer.
128 svc_domain.pm mail sending uses Date::Format which doesn't seem to pick up
131 view/svc_domain.cgi needs to know the domain might be unaudited (cosmetic)
133 remove whois_hack set to 1 for svc_domain.pm? add all known registries and
135 .us domains and others!
136 site_perl/svc_domain.cgi (hmm... or maybe should have a button? or maybe svc_domain.pm should handle this) should set $whois_hack for non-internic domains, so you can add them...
138 turn on the depriciation warnings for [e]idiot in FS::CGI. Stop using [e]idiot
139 the last places it is (htdocs/search/ htdocs/misc/ htdocs/misc/process)
141 (test cust_main.pm with cybercash v2 and v3, especially with the callback
142 stuff AND with mod_perl w/cybercash v2 kludge in package main)
143 (callback stuff should be eliminated by now)
145 bah, table/itable/*table in FS::CGI is silly.
147 doc Apache::AuthDBI as well
149 Provide sample httpd.conf files.
151 hey look: Tie::DBI! Check that out. Override its commit with something that
152 does perl-side caching for ? a performance improvement and as an emulation
153 layer to plug in f.ex mysql's atomic transactions
155 Record.pm uses does some non-portable DBI things. MySQL and Pg seem fine.
156 Fix it anyway unless we migrate to Tie::DBI.
160 cust_bill.pm uses '==' comparison on dates because they're currently ints
162 config file for allowed card types
164 write instructions for adding new services w/svc_Common.pm. Get rid of all
165 places where svc_* tables are hardcoded (rename svc_acct_pop to part_pop so
168 test and document libapache-dbi-logger (woo!)
170 radius logfile parsing and perl expression check.
172 Fix in cust_bill BUGS:
173 There is an off-by-one error in print_text which causes a visual error (Page 1
174 of 2 printed on some single-page invoices).
176 fields should be a method against a FS::Record or derived object, as well as
177 being something you can call as FS::Record::fields('tablename'). Might
178 even be able to handle both in the same routine (that would be neato).
180 Immediate removal of incorrectly entered check payments (can't take too
181 long to do this, or accounting is fubared).
183 Add code to move from one service to another (POP to SLIP/PPP, etc.).
184 This _should_ be possible by working off the rules in part_svc rather than
185 hardcoding anything in. The rules in part_svc may need some elaboration,
188 Use ut_ FS::Record methods in all derived classes (possibly some from dbdef?... eventually all from dbdef??? - but then `dbdef-create' would be impossible as there would be metadata we couldn't ask the backend for. hmm.)
190 (bring back from fsold, ) Generalize config-sending stuff and make more configurable.
191 Expand the HylaFAX interface (also possibly generalize for other fax
192 softwar ie .comfaxe); allow things like arbitrary faxes of sales
193 literature, specific troubleshooting documents and so on. Maybe even
194 allow users to do this (though that might not belong in Freeside).
196 misc/process/sendconfig.cgi
197 Configure fax recipients via a separate box rather than using the finger
198 name or first+last from cust_main.
200 move all phone number logic out of Freeside - let HylaFAX or whatever
203 soundex searches for customer name and company? where are free soundex tools? (standard Text::Soundex duh) - I could have sworn I saw Text::Soundex on CPAN?!
205 should be able to link on some field in email alias (right now you can link
206 on username or domain with a fallback to svcnum)
208 generalize and make configurable new invoice printing scheme in FS::cust_main::collect (past due)
210 deleting an svc_domain should delete all associated svc_acct_sm records.
211 same with a svc_acct.
213 periodic password encrypter
215 Automated, configurable notification, suspension and cancellation of
220 Allow for a future setup date on accounts.
222 sub AUTOLOAD in FS::Record should warn? die? if used with a non-existant column
225 edit (not just import, export and allow default/fixed) arbitrary radius stuff
227 edit/svc_acct.cgi and edit/process/svc_acct.cgi should deal with arbitrary radius stuff
229 radius import should take DEFAULT entry and put it in /var/spool/freeside/conf/radius-default ; svc_acct.export should use it (and doc)
231 in UI, s/State/State\/Provence/go and s/County/County\/Locality/go
233 what else (besides l10n) for i18n? (money!)
235 audit htdocs/* for things that should be libraried and things that should be
236 new methods on the objects (need to do this before implementing a new UI)
237 all the big things are done
239 some places we die() where we should &FS::CGI::idiot (and perhaps vice-versa).
240 Decide based on whether or not the "error" should show up in logs.
242 all .cgi's should use standard header/footer and idiot() subroutines. maybe HTML:: perl modules
243 for HTML creation. Maybe Embperl or something along those lines. ?
245 When running bin/bill, Fix this (Annoying but harmless):
246 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 99, <ADDRESS> chunk 4.
247 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 102, <ADDRESS> chunk 4.
248 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 105, <ADDRESS> chunk 4.
250 all cgi (but internal to the isp) places where package names are listed should also have
251 comment (like agent_type)
253 clean up $recref and other silliness and use -> calls where possible, or
254 one other alternative. clean up everything else.
255 should FS::Record use Tie::Hash? That would be very clean, but where do we
256 store the other information? Maybe you could ask any FS::Record object for a
259 change all file access from regular open(FILE,) stuff to OO, because of
260 problems scoping and passing filehandles like that.
262 the web interface should create a new object and use it instead of a blank
263 form for new records. the create method of svc_ objects should set defaults
266 sub check in man FS::table_name should be rewriteen. Get rid of $recref
267 stuff. Make sure all fields that refer to other database are checked.
269 Integration with signup disks (are there any free ones? Netscape?).
271 One-button cancel (+refund) for lusers who can't get online.
273 Keep information on virtual web servers (hostname, IP, host machine,
274 directory, etc.) and export this information for importation into the ISPs
277 Remove requirement that the first mail alias be the catchall? Still make
278 sure only one catchall per domain is defined in any case, of course.
280 Ability to move cust_pkg records from one customer to another? (proably
281 will need to cancel the old and create a new like when we move services
284 Auto-increment expired cards one year, and try again?
286 More non-US stuff - zip codes, country codes, foreign currencies, etc.
288 cust_refund.{cgi.pm} need to do cards xaxtions. (now we only have cust_credit)
290 Nicer set of integrated reporting possibilities, like weekly sales totals
291 by customer, package, agent, referral, etc., aging reports sorted by lots
292 of different things, and so on.
294 Client/server setup for users to modify their own passwords, shells, etc,
295 via passwd or secure web interface (prelminary passwd/chfn/chsh
296 replacement done). Complicated by the fact that we don't want to allow
297 incoming connections to the machine running Freeside, so we probably need
298 to have a daemon on each external shell or web machine that is contacted
299 by the Freeside machine. Be very very careful for both traditional
300 security issues and DoS problems.
302 An extension of the above to allow users to modify selected parts of their
303 own information, order and cancel services. A web interface for new
306 Expand domain name stuff to house all domain information. Export
307 named.boot/named.conf (primary and secondary) and named.{domain} files.
308 Add more registries (not just InterNIC's com org net edu)
310 Nice postscript paper invoices, rather than current ASCII invoices.
312 think about race-condititions in FS::Record and derived ->check ->insert
313 and so on, uid and username checks in svc_acct, etc.
315 Move to rsync over ssh file exportation rather than scp.
317 check 'n fix the proactive password checker. (cracklib?)
319 refunds of "BILL" payments: generate pseudo-check.
321 write batch senders and batch parsers for the different credit card processors
323 More CC processors/methods.
325 you should be able to fiddle the setup date in cust_pkg. (at least initially)
327 delete options in administration section
329 write a generic batch senders and batch parsers.
331 need a way to override svc_acct export on a per-machine basis; just use config files based on machine name i suppose; document that. (no, import desync_hosts
332 type stuff from cerkit)
334 add a table with column of export services (passwd, shadow, master.passwd, .qmail file update, dns update, etc.) and rows machine groups and whether or not to export that (and any necessary parameters). wasn't matt (vunderkid, not matt@michweb) working on this? find him? each machine goes in a group of its own as well as a group based on function. add a table with only svcpart and machine group. now, when you import from each machine, it can get its own accounts with one svcpart and universal accounts with another svcpart. (though that does make the username duplicate checking more interesting)
336 you should be able to get column types as a method against an FS::Record object
337 as well as dbdef->table($table)->column($column)->type
339 move to perl module for fuzzy and soundex searching.
341 package view needs to list extraneous services; we need to prevent the
342 creation of them so this never happens (and mark it as such in the source)
343 (the creation problem should be fixed - though they will still happen if people
344 fsck around in the data manually, so list them anyway)
346 add attribute dictionary to fs-setup as a menu, plus analyze users file to
349 Check for and report on duplicate billing accounts (cust_main, though many
350 will have a need for these so probably don't disable them outright.)
352 create a ->warn as well as a ->check method for all FS::table classes?
355 something to automate making a release and updating the web demo
357 export a debian-style (also redhat and?) /etc/group file aswell!
359 svc_acct_sm.import qmail import should pull in recipientmap people too.
361 .pm's like svc_acct.pm which need to do time-consuming things like ssh remotely
362 should fork and do them in a child.
364 i18n/l10n: take ALL messages and catalog them in english.txt or in database or something, so we can eventually go int'l. int'l currency support would be a help aswell.
366 get some of { city, county, state, zip } from the missing bits if
367 possible (where can i get the data to do this? usps.gov?)
369 additional interfaces (perltk? java?)
371 Put the GPL notice in all files.
373 integrate w/IDEA's signup server
375 $cust_bill->owed database field to be eliminated, replaced by a method call
376 that calculates on the fly. make sure to grep for ->(get|set)field('owed')
377 same for cust_credit->credited
379 Export quota information.
381 move all configuration to a central place. maybe in blob's in the
382 database. maybe even things like the code to execute when a username is
383 changed can be in there, so less of the distributed scripts change between
386 Implement setup and recurring fees as Safe perl expressions rather than
387 numbers, to allow for variable-rate services. Backwards compatibility is
388 obtained because { 43 } in perl is still 43. :) Define API to pass
389 starting and ending dates and any other necessary data to expression
390 (fees are currently evaluated as Safe expressions but more work needs to
391 be done to define an opmask for various needs, write examples
392 (usage-based billing, etc.) and so on).
394 Add the ability to modify the next billing date in cust_pkg, and take
395 appropriate action. This will allow the implementation of pro-rate/1st of
396 the month billing as well as the ability to manually fiddle with
397 anniversary dates in cust_pkg, so you can sync a customer's anniversary
398 date even if you're using anniversary billing (manually or automatically).
399 (now with above, we need to have a way to automatically pro-rate /^(\d+)$/
400 charges - anything more complicated should figure it out itself given
401 starting and ending dates [document that!])
403 Daily Radius log parsing into database; other logfile formats?
405 Callbacks to enforce hourly limits on accounts (suspend until the end of
406 the billing period?), for those who limit customers rather than tack on
409 Flag packages (part_pkg) as taxable or non/taxable as some ISPs (for
410 example) need to charge tax on equipment but not service (separate flags
411 for setup and recurring fee... or perhaps a setup_tax, setup_notax,
412 recur_tax and recur_notax fees, and possibly something more flexible if
415 Allow for a variable number of invoices for customers who need multiple
418 Add a mail alias service with table svc_acct (not domain mail aliasing
419 which is domain with svc_acct_sm)
421 (bring back from fsold) Change customer comment field from its current kludge to something more
424 Better work orders with more information. Should eventually open a ticket
425 when we have such a thing.
427 edit/process/svc_wo.cgi
428 Call tracking and trouble tickets.
430 More accoutability for complimentary accounts: approval, expiration, term
431 (no more than x months in advance) and notification.
432 Flag particular users (or all users, for that matter) as having their
433 passwords hidden and/or locked from users of Freeside (maybe need Freeside
434 security levels first?).
436 Better Freeside-level configurable access, for those ISP's who have
437 employees they can't trust. Right now you're "stuck" with setting up
438 .htaccess stuff yourself. This should really just be integrated.
440 configuration/setup should get web interface
442 /usr/local/etc/freeside should be configurable
444 (probably as part of some automated installation process?)
446 This requires some serious magic in FS::Record:
447 ok, if date_type in fs-setup is to be something besides int,
448 now we need to create wrappers
449 for them so they behave identically across RDBMS's, ie date pops out as as
450 UNIX timestamp (or an object of some sort? maybe even a blessed $obj which
451 is a string not a hashref for backwards compatibility?) and so on. (remember
452 to treat '0' as Not a Date instead of 1/1/70.
454 Add Freeside-level transactions for RDBMS's which don't support
455 transcations? (Currently we assume a minimal RDBMS which has no rollback,
456 transactions or atomic updates). Or just require a RDBMS that supports
457 rollback and/or atomic updates and get rid of the work-arounds? The /rdb
458 interface had this kludge on top of it but is a technical dead-end in most
459 other ways, unless it can gain an SQL parser and DBD interface.
461 if i'm really bored, find the /rdb interface in fsold and port it to NoSQL,
462 and while I'm add it add interfaces for AnyDBM_File tied hash.. hmm. Shouldn't
463 an FS::Record have something to do with a tied hash? But we don't want
464 performance to go gaga... maybe something with commit to help out here?
466 Ok: FS::Record gives you a tied hash, and you get methods for commit, etc.
468 Better automated comparison of our CC records with processors (CyberCash,
469 at least, has not always had 100% accuracy, though recent versions are
472 Expect or other pty based login check, where we actually connect to a
473 terminal server or shell machine and test logging in as the user (if we
474 are keeping a cleartext password for that user) (This is something tech
475 support often needs for new customers)
477 Use cust_main table for pre-sales tracking as well?
479 Automatic commision report and check generation via freq and prog (to
480 become a Safe perl expression) fields in agent table, and possibly others.
482 Database and add a mailed-out date and method for disk/CD mailing, so a
483 customer can call and you can say, "sent on xx/xx/xx via {US Mail, Fedex,
486 Inventory tracking for physical items such as routers (for sale or
487 lease... probably doesn't make a difference in the ordering... but if you
488 cancel a router lease the inventory should come back. hmm.)
490 -- Matt's wishlist ---
492 From matt@michweb.net Fri Feb 20 16:39:53 1998
493 Date: Thu, 19 Feb 1998 23:20:11 -0500
494 From: Matt Simerson <matt@michweb.net>
495 Reply-To: quadran-developer@netgoth.com
496 To: quadran-developer@netgoth.com
497 Subject: Re: Welcome to quadran-developer
499 >Whats it based on and what is it supposed to do? I'm interested, but
500 >unfortunatly, I don't have that much time to help on the project (I'm busily
501 >working on one of my own based around MySQL and Qt right now -- don't know
502 >if it will be GPL'ed or not yet -- we'll probably just use it in house since
503 >it is designed around our system)...
505 That's what I set out to find, but didn't find anything on the web site.
506 I'm looking for something that will do the following:
508 Single point of entry for users on a secure system:
509 Creates account on user (public) systems
510 update /etc/passwd/master.passwd file
511 update radius database (if necessary)
512 Set up up disk quotas (although I hacked adduser to do this)
513 Option for adding user to a mailing list(s)
514 Export of new user info to customizable report (for automated entry
516 accounting software, etc...)
519 Export credit card info for batch processing and have hooks built
520 in for other forms of electronic processing.
521 Batch-Payment (apply payments from formatted text file).
522 Customizable reports for manual entry/importing into Accounting
524 Email or laser print invoices
525 Sanity checks credit card numbers before processing (code available)
527 Simple method for disabling an account.
528 Arbitrary Expiration Dates (on a given day, in x days)
530 Changing password to '*'
531 Virtual customers disabling dns, http server, log processing, etc..
533 Billing for different account types:
534 Dialup monthly flat rate. Prorates for partial months.
535 Dialup monthly flat rate for x hours + hourly usage.
538 Virtual Web accounts - w/multiple mailboxes
540 Disk space used over quota.
541 Tech support minimum + hourly charges
542 Other for misc stuff (modem, RAM, etc...)
544 Per user definable RADIUS attributes (ties in with above)
547 IP filters (for dialup email only)
549 Keep logs of modem usage generated daily from radius accounting logs stored
550 on multiple radius servers.
552 Keep logs of disk usage generated from quota.
554 Method of adding virtual domains to your system:
555 Automatically grabs an IP address from a preassigned pool.
556 Creates a domain.com database file from database fields
557 Updates /etc/named.conf or /etc/named.boot and reloads named.
558 Add's virtual.com to /etc/sendmail.cw or qmail control files.
559 Edits your web servers httpd.conf file and restarts http server.
560 An optional section for adding vif's can be added if the users OS
561 supports adding them on the fly. Otherwise it's up to the end
562 user. Make a hook that can run a custom script that the user
563 tweaks for his system.
564 Update or create the config file your web stats analyzer needs. I've
565 done this for analog (free) and http-analyze. Probably
566 should only officially support analog and let users hack
567 it to their hearts desire.
568 I've already written scripts that do most of the virtual web stuff on my
569 system...in bash. Shouldn't be hard for a perlmeister to convert. In fact,
570 as long as all the info was stored in the database (username, domain name,
571 and ip pool) this could easily just be run as an external script that the
572 user tweaks to match his system.
574 We use a great accounting software (M.Y.O.B) that does all the AP, AR,
575 Payroll, Tax stuff, and most everything else we could need. It's already
576 set up for the type of checks we have, etc, etc... I just need something to
577 do the billing part. I can import/export sales and payments directly once
578 the billing part is done. You can't write accounting software as good as