1 $Id: TODO,v 1.53 2000-12-03 20:25:20 ivan Exp $
3 If you are interested in helping with any of these, please join the
4 *development* mailing list (send a blank message to
5 ivan-freeside-devel-subscribe@sisd.com) to avoid duplication of effort.
9 first package select field in edit/cust_main.cgi isn't sticky on errors, yuck
11 > 1. A Web Form to the user get his account added automatically . The
12 > /etc/raddb/users and /etc/passwd would be updated automatically (these
13 > file are on the same machine Freeside is). I guess the the Add
15 > page with some customization could be the work.
16 > 2. A Canceling Account Web Form available to user cancel his account
19 > 3. A Password Changing Web Form where the user could change your
20 > password by sending your username, old and new password.
21 > 4. Additional POP Accounts Creation where the user supply only his
23 > username/password (probably provided from a PPP Account already
25 > and his POP username/password for this specific account.
26 (actually need something more general i guess - probably need some way to say
27 which accounts (svc_acct) can log in and make changes per customer (cust_main) )
29 this is awfully vauge, perhaps email for more info? don't want to alientate
30 someone with accounting experience, but i just don't have time right now.
34 Thanks for the information. It took me a little while to figure it out, but I
36 able to create an invoice. As a lamer and an accountant, may I make a few
39 On the Customer view page:
40 1) Layout the information in the manner the invoicing process is conducted.
41 a) Customer information
43 c) Add a "Create & Edit Invoice" section - this allows auditing of the
44 invoice before it is processed.
45 d) then put the billing section to actually process the invoice
46 e) then put payment history information
49 Mark Roberts <mroberts@iopenenterprises.com>
52 new overdue code might be overzealous. test carefully.
54 Port Freeside to use the modules that were abstracted from it:
55 Net::SSH, Net::SCP, DBIx::DataSource and DBIx::DBSchema, at least.
57 "first package" and email invoice (?) not sticky on errors in new/edit customer
60 http://www.ipmeter.com/ integration would be useful
62 http://tangram.sourceforge.net/
65 mmm, http://pootpoot.com/~dlowe/DBIx-Table/
67 The cybercash links in htdocs/docs/config.html are b0rken.
69 Yes. Which is what I've been trying to tell you. (destination user,
70 destination domainname) would be represented by the svcnum of a record in
71 svc_acct. (In retrospect, using the uid instead of the svcnum was a bad
72 choice). (domuser, domain name) would be part of the svc_acct_sm record,
73 as domuser and domsvc.
75 Upon further consideration, I'll probably eliminate the svc_acct_sm table
76 completely, and just add a field for the svcnum of a domain and the svcnum
77 of a destination mailbox to svc_acct (or perhaps a one-to-many
78 relationship - multiple svcnum(s) for multiple destination mailboxes.
81 > > > > Longer-term, I need to do something about the length of the
82 > > > > column names -
83 > > > > The SQL1992 standard defines 18 character column names,
84 > > > > which would be a
85 > > > > reasonable goal.
87 > > > Maybe the thing to do would be to separate these out to separate
89 > > > then we could simply use something like id, attrib_name,
92 > > > store all of the radius values.
94 > > Hmm, no, that's not quite right. You don't want to store the actual
95 > > strings in the records for each account. Probably need a table that
96 > > corresponds to the RADIUS dictionary file, with a list of
98 > > attribute id's, then reference the attribute by id and not name.
100 > > The more difficult bit is handling the service definitions
102 > > part_svc and it's effects.
104 > Yes that could be a bit tricky. Perhaps just one "radius" field in
105 > part_svc that held a list of id's from the radius table that applied
106 > that particular service?
108 No, that wouldn't let you set defaults or fixed values for each attribute,
109 like part_svc currently does.
113 hmm - if you delete an account in svc_acct somehow that a mail alias points to,
114 svc_acct_sm.export will fail. make sure this can't be done using
117 Bug: during the linking process apparantly you can link too many services to
120 zip code i18n is not very good :( but at least US, CA, HU, ?
122 ut_phonen doesn't check data length. several
123 orthogonal cleanup projects here. *sigh*
125 update the cybercash links in config.html and in the homepage. add more explicit support for other payment types. etc.
127 From "Tim Jung" <tjung@igateway.net>
129 Automatic CC Decline Notices via email
130 Block Time billing for prepaid internet cards (400 hours or whatever block
132 Trouble Ticket System with simple search function for Knowledge Base feature
134 Credit Card System support for Red Hat's CCVS, and other Linux credit card
136 Contact Manager/Lead Tracking
138 Cisco NetFlow Account for IP traffic billing
139 VoIP and FoIP billing
140 Roaming per minute billing based on Radius Proxy support or number they
141 dialed into from Radius logs (800# etc)
142 Support for OpenSRS Domain Registration
143 Support for TUCOWS signup CDs
146 dbdef-create for postgres
148 pro-rating, fiddling dates
150 It looks like svc_acct.import doesn't deal well with comments and
151 multi-attribute lines.
153 ivan@rootwood:~/freeside_current$ rgrep -r domuid * | cut -d: -f1 | sort |
158 bin/svc_acct_sm.export
159 bin/svc_acct_sm.import
160 htdocs/docs/man/svc_acct_sm.txt
161 htdocs/docs/schema.html
162 htdocs/edit/CVS/Base/part_svc.cgi
163 htdocs/edit/part_svc.cgi
164 htdocs/edit/process/svc_acct_sm.cgi
165 htdocs/edit/svc_acct_sm.cgi
166 htdocs/search/svc_acct_sm.cgi
167 htdocs/view/svc_acct_sm.cgi
168 site_perl/svc_acct_sm.pm
170 rootwood:COMPLETEHOST/TODO
172 Currently, you set a value in the %FS::UID::callback hash with a coderef
173 of the code you want to execute, but this was bad design and will shortly
174 be changed to a subroutine to which you pass your coderef to register it.
176 This is not a bug, it is how the system is currently designed. After
177 defining a new package, you need to specifically allow agent types to
178 purchase packages. You can do this from the edit screen of the new agent
181 It wouldn't be a bad idea to add a configuration value that makes new
182 packages available for all currently existing agent types automatically.
184 On Fri, Apr 07, 2000 at 10:50:35AM -0500, David Morton wrote:
185 > For some reason, the type_pkgs table didn't get updated when I tried to
186 > create a domain service and package... insert into type_pkgs values
187 > (4,1); fixed it up so that I could actually order the package.
190 From: Chuck Cochems <zaphod@tdl.com>
192 1) automated generating of late notices. So far the only way I know to
193 generate one is to re-invoice manually.
195 2) smart credit card rejection handling. It should e-mail a note at
196 least, explainig that it did't go through, and why.
198 3)coment field in the main customer record.
200 4) streamlined payment entry feature. the current scheme has it fairly
203 5) queries to show al customers who owe money,and such stuff as that.
206 credits aren't counted against past invoices? hmm. something needs to be
207 done to "apply payment" genericly. and zero out invoices etc.
209 more email which should make it into a more organized TODO list:
211 I would also love to see Freeside support bandwidth billing by reading the
212 Cisco NetFlow Accounting data so we and other ISP's could automatically bill
213 co-located servers and even potentially other virtually hosted sites like
214 MUD, Palace Chat, IRC Chat, etc based on the bandwidth they use or average
215 sustained rates or whatever. I'm not much of a programmer so I don't know
216 what all this entails but I did download a NetFlow client agent/whatever for
219 It would also be nice to see Freeside be able to read Apache log files and
220 bill customers for web traffic that way as an option also. Plus an option to
221 bill for excessive disk usage without having to use quotas if you didn't
222 want to, would be a nice feature as well. So you could monitor with a script
223 or something to see how much disk space a user was using then get some
224 average and charge a certain amount for anything above some preset limit for
225 that account type. I might be able to hack something like this up, but I'm
226 not 100% sure where to start or if there is something out there that could
229 Do you think that you will ever support the HKS CCVS (Hell's Kitchen
230 Software Credit Card Verification Software) since Red Hat bought them out
231 and is going to be including that for credit card processing when you buy
232 the professional version? What about possibly supporting the OpenCCVS which
233 is a GNU/GPL version of a credit card program? I haven't had time to comb
234 through the Freeside code to see how hard it would be to add support for
235 these as externally called programs.
237 Also any thoughts on help desk, and knowledge base stuff? Any thoughts on
238 this stuff, and how possible and what kinds of work or time frame would be
243 Internet Gateway Inc.
248 CVS via SSH (Score:1)
249 by platinum (jedgar at fxp dot org) on Thursday September 30, @07:13PM EDT (#4)
250 (User Info) http://www.fxp.org/~jedgar
251 The links above are your best bet for basic cvs server configuration. Once you have a pserver set up, you
252 may consider using cvs via ssh. All you need to do is the following:
254 1) Have ssh and sshd set up on the client and server machines
255 2) Set CVSROOT="joe@example.com:/home/ncvs"
256 3) Set CVS_RSH="/usr/local/bin/ssh"
258 (Obviously, insert the proper host/paths above)
260 You can also set up cvs/ssh to not need a password every time (similiar to an initial 'cvs login'):
262 1) run ssh-keygen on client machine using no passphrase.
263 2) copy/add ~/.ssh/identity.pub on the client to ~/.ssh/authorized_keys on the server
264 (man ssh for more details)
266 The main reason I mentio
267 CVS via SSH (Score:1)
268 by platinum (jedgar at fxp dot org) on Thursday September 30, @07:13PM EDT (#4)
269 (User Info) http://www.fxp.org/~jedgar
272 There's no way to do this currently, though it would be pretty
273 straightforward to modify the source - specifically, the _collect_
274 subroutine in FS::cust_main.
276 On Mon, Dec 13, 1999 at 04:05:32PM -0700, Jeff Garner wrote:
277 > Freeside will e-mail my users when they are billed if they are setup as
280 > When setup by credit card it does not e-mail them. Is there a way to
281 > turn on e-mail invoices for those who are billed via credit card? Kind
282 > of like a recipt of billing....
285 doc: http://www.softagency.co.jp/mysql/qmail.en.html
287 sql1992.txt standard is 18 character column names. shoot for that, not just
288 32 (postgresql default)
290 Also note that (AFAIK) Freeside won't display any package that has more
291 than one service on the "Add Customer" page. The reason for this is
292 because there's no way to dynamically alter the displayed html form
293 based on which package is selected. One possible solution would be to
294 make an additional page that's used in the signup process that would
295 display the form for each package, like a MS-style "Wizard". The first
296 page lets you select the package, then the second page has the custom
297 form with fields for each service in that package and a save button. Of
298 course, that would require a little perl work.
301 Scott Cruzen <sic@boernenet.com>
304 Your suggested script with back up /usr/local/etc/freeside, but will miss
305 any database not named `freeside'. Both of our scripts are specific to
306 MySQL. If you're interested in contributing to Freeside, maybe you could
307 work on a script which: reads the mapsecrets configuration file and then
308 each secrets file to find out what specific database engine(s) (MySQL,
309 PostgreSQL, etc.) and database(s) need to be backed up, then does so,
310 serializing backups of the same engine, i.e. stop mysql, do all the mysql
311 backups, start mysql, stop postgresql, do all the postgresql backups,
312 start postgresql, etc.
315 > mysqldump -t freeside > fs-backup.sql
317 > tar -Pzcvf fs-backup-`date +%y%m%d%H%M%S`.tgz fs-backup.sql /usr/local/etc/freeside/
320 I chose to use counters in the filesystem because there is no standard way
321 to get the value of an auto-incrementing keyfield which is common across
322 all databases (as seen through DBI/DBD).
324 It certainly wouldn't be a bad idea to use the database-specific methods,
327 htdocs/edit/svc_acct.cgi:
328 (Does the `*HIDDEN*' show up when you are adding a new account, and
329 specify the password, then receive an error and are returned to the form?)
332 Thought some of you might be interested in this:
334 <ftp://ftp.minivend.com/pub> has CyberCash compatibility modules for
335 Paymentnet <http://www.paymentnet.com> and Authorizenet
336 <http://www.authorizenet.com> which should allow you process transactions
337 using those services as well as CyberCash.
339 The files are named CCLib.pm.paymentnet and CCLib.pm_authorizenet,
340 respectively, and are installed by renaming to CCLib.pm and moving to your
341 site_perl directory. Otherwise, follow the directions for Cybercash v2 in
342 htdocs/docs/config.html
345 fs_passwd/ is a client-server replacement for the `passwd', `chfn' and
346 `chsh' commands that updates the Freeside database. (so for that to be
347 useful, you'd have to be exporting that data periodically)
349 fs_radlog/ is a client-server RADIUS log parser that stuffs the data into
350 SQL. It isn't finished, and probably won't be unless someone who I can't
351 convince to use one of the RADIUS daemons that logs to SQL directly pays
352 me money or something.
354 fs_signup/ is a client-server signup server. i'm just finishing it up
355 now; probably isn't on your machine yet.
358 http://www.sisd.com/freeside/list-archive/msg00812.html
360 package definitions should be implicit allow wrt agent types, not implicit deny
361 (with the old behavior possible via a config file)
363 > So is there anyway it could be setup to allow you to select a "primary
364 > service" from each package? This service would be the one you were prompted
365 > for. Could the signup server then be expanded to allow users to go into
366 > their package and "turn-on" the remaining non-primary services(using the
369 take the GPL'ed whois proxy stuff at www.geektools.com and turn it into
370 intelligence for Net::Whois.
372 A web version of the fs_passwd stuff would be nifty.
374 If you have Cistron authenticating directly from MySQL, you can replicate
375 in real-time instead of exporting periodically. See
376 <http://www.mysql.com/Manual_chapter/manual_Common_problems.html#Replication>.
379 <http://www.sisd.com/freeside/list-archive/msg00541.html> (was 546), and
381 and http://www.sisd.com/freeside/list-archive/msg00421.html (was 423)
383 > > 5: Is there anyway to get freeside to send a sysadmin a warning when a
384 > > credit card has expired?
385 No, but there should be.
387 Put this in the doc (quoting Mark Wells <mark@pc-intouch.com>):
388 >Of course, thanks to the sheer coolness of SQL and MyODBC, you can do
389 >whatever reports you want in basically whatever application you want.
390 >There's no need for Freeside itself to do any reports at all.
392 middle names and titles
394 On Wed, Jul 07, 1999 at 01:11:40PM -0400, Frank Nazario wrote:
395 > Playing and entering information to Freeside i encountered the following
398 > View Customers by Agent
400 > View Pending Invoices
403 grep 'uncomment this to encrypt password immediately' site_perl/svc_acct.pm
404 Not to say that it shouldn't be a configurable option.
406 in site_perl/cust_main_invoice.pm (elsewhere?), error out if mydomain config file is gone
407 (at least until the idea of a default domain goes away)
409 FS::Record::qsearch does an eval every loop iteration (which is itself not
410 guaranteed to work across all DBD's and should be fixed). This has got to be
411 slow. Fix it. (I think recent Perls might have a way to accept a variable
412 there, no eval needed?)
414 Could you have added /bin/sync, /sbin/shutdown, and /bin/halt to the
415 `shells' configuration file before importing, and removed them afterwords?
416 (even better if svc_acct.import did that automatically - it could just
417 munge and restore @FS::svc_acct::shells... hmm.)
419 > BTW, Ivan, I am trying to verify in an additional database table that a
420 > particular user doesn't exist. This database is used to store email aliases a$
421 > additional POP boxes for our customers (kinda like AOL allows). I have toyed
422 > with the idea of just writing the aliases to an email only svc_acct that
423 > doesn't write to the password file, but that isn't really how I want to do it.
425 Actually, I think that's a pretty good way to do it. Cerkit contributed
426 support a little while back for svc_acct.pm and svc_acct.export for
427 multiple export targets. It needs to be cleaned up and documented, which
428 I'll try to get to soon. For this to work correctly, the svc_acct_sm
429 table should go away, along with the concept of a "default" domain.
431 default setting for new packages should allow all agents to purchase them...
432 with a config file for the old behaviour
434 fix or replace Term::Query (Quiz::Question doesn't do what i need)
436 Check config file reading stuff from CPAN
438 Authorizenet module from CPAN!
440 <http://www.math.fu-berlin.de/~leitner/mutt/faq.html> has a good y2k complience
443 I'm hoping Freeside can support arbitrailly complex pricing plans
444 because of a simple concept: all prices are perl expressions. So if
445 you use `19.95' for example, perl evalates that to be `19.95'. But if
446 you need to do a complex pricing scheme, you just need to write an
447 appropriate perl expression, which will most likely pull data from the
448 database to return pricing. Some things will already log to SQL; for
449 example most RADIUS servers can or have a patch available. Getting
450 Freeside to bill based on any sort of data then becomes a matter of
451 importing the data into the database.
453 There are some issues involved with pro-rating, partial month charges,
454 that sort of thing. Expressions will need a standard way to have the
455 applicable time/data ranges passed to them. Also the expressions are
456 currently running under the Safe perl module, and the opmask might not
457 be right in all situations. I'll try to spend some time working on
458 this if you are using it.
460 > 2. can customers view their bills on-line.
462 Not yet; it needs to be proxied from Freeside to a customer web server in
463 a secure way using something not completely unlike the fs_passwd,
464 fs_passwdd, fs_passwd_server trio.
467 > Lastly, if someone over pays on an invoice, the credit part does not flow
468 > over to other invoices..
470 The total balance flows over correctly, but individual payments don't.
471 The code you're looking for is in FS::cust_pay::insert
473 The question of what to do with overpayments that don't have another
474 invoice to flow into (yet.. or possibly not) is still an open one. The
475 legacy system Freeside replaced long ago had a separate place for this
476 (payments waiting for an invoice) for each customer, and it gave our
480 option to relax username uniqueness in favor of username+domain or mail/shell
481 vs. radius to ease import for isp's with namespace problems or who buy others.
483 do i have to store anything for radius realms besides regular radius attributes
484 (which are handled fine now)?
486 warn or complain or something when invoice_from is empty (and we use it)
488 Right now Freeside uses the `freq' field of a package definition as a
489 number of months. The specific section of code you're looking for is in
492 #change this bit to use Date::Manip?
493 #$sdate=$cust_pkg->bill || time;
494 #$sdate=$cust_pkg->bill || $time;
495 $sdate = $cust_pkg->bill || $cust_pkg->setup || $time;
496 my ($sec,$min,$hour,$mday,$mon,$year) =
497 (localtime($sdate) )[0,1,2,3,4,5];
498 $mon += $part_pkg->getfield('freq');
499 until ( $mon < 12 ) { $mon -= 12; $year++; }
500 $cust_pkg->setfield('bill',
501 timelocal($sec,$min,$hour,$mday,$mon,$year));
502 $cust_pkg_mod_flag = 1;
504 ..and when I went poking for this, looks like it tells us just what needs
505 to be done! Hehehe...
507 Date::Manip can handle cool things like "+ 1 month" (actually the current
508 case of /^(\d+)$/ would have to be added as a special case of "+ $1
509 month") and "+ 30 days" (what you need) and even "+ 5 business days" !
512 On Wed, Apr 28, 1999 at 08:38:16PM +0000, Kristian Hoffmann wrote:
513 > I can't quite seem to figure out how this exporting works. From what I
514 > understand, when you run svc_acct.export, it rewrites the /etc/passwd,
515 > /etc/shadow, etc. files. Is this only for initial setups with the
516 > export hooks being in the pm's?
518 You can use both, or just one method. The configuration files control
519 this. One of the things in the TODO is to take out the last few things
520 that aren't customizable wrt this and put them in config files.
522 http://www.daemonnews.org/199905/user-mgmt.html
524 Term::Query doesn't install out of the box from CPAN. Fix it (and get it
525 submitted upstream!), or remove requirement from bin/svc_acct.import and
526 bin/svc_acct_sm.import and take it out of the install instructions.
528 use this cool link to explain the Freeside API
529 ftp://cpan.nas.nasa.gov/pub/perl/CPAN/doc/FMTEYEWTK/easy_objects.html
531 Multiple tax rates by geographic region (county, state, and county) are
532 supported; just choose View/Edit tax rates from the main menu.
534 Multiple tax rates by package are not (yet) supported.
536 On Wed, Jul 07, 1999 at 12:13:36PM -0400, Shaun Batterton wrote:
537 > How would you handle something like multiple tax rates and multiple
538 > states? For example in Connecticut, they just changed computer and/or
539 > data processing services to 3% (whatever that is), and everything else
543 > Second, when trying to add a new user I get two types of errors; first one
544 > is when I place an e-mail address and select the "submit," Freeside
545 > complains with "Error: Unknown local account (specified literally)"
547 You probably put a (local) email address in for email invoices. Freeside
548 stores these as references to the database records, so (for example) they
549 follow username changes.
551 I'm guessing you put in the email address that you were creating, and got
552 that error because it didn't exist yet. Sounds like a buglet to me. I'll
553 try to fix that soon; in the meantime you can add the invoicing email
556 (workaround for postgres before 6.5) (unlikely to ever be implemented)
557 In the mean-time, this could probably be fixed with the reverse of
558 the kludge in FS::Record::new. This removes `$' and `,' from money fields
559 coming out of the database. Something which fixed up the data so Postgres
560 was happy with it could go in FS::Record::_quote, for data going into the
563 our data display problem might be a Freeside problem wrt not using
564 Oracle-compatible DBI syntax (fixed using the return value from $sth->execute
565 as a number of rows - something else?).
567 hooks for arbitrary commands out of configuration files
568 svc_acct.pm svc_acct_sm.pm etc.
570 Add this to a FAQ, along with doing it for middle names:
573 > What I'm finding difficult is how to easily
574 > customize fields. For example, I am trying to add a "middle name" field
575 > to the Customer Edit, view, etc. If I'm going about it right, it appears
576 > I have to edit the cust_main.cgi under edit and edit/process and the
577 > site_perl/cust_main.pm, as well as other things. Perhaps you could shed
578 > some light on the best way of doing this.
580 You have the basic idea. To implement that completely, I would:
581 - Add the new field to bin/fs-setup for new users
582 - Document the field in htdocs/docs/schema.html
583 - Document the change in a new file, htdocs/docs/upgrade4.html
584 * Run bin/dbdef-create
585 * Add the new field to edit/cust_main.cgi and edit/process/cust_main.cgi
587 For bonus points, I'd grep around for the various bits which use "$first
588 $last" or "$last, $first" and replace them with a method call in cust_main.pm,
589 , like search/cust_main.cgi
591 document security model:
592 Don't forget about Apache usernames - since, via the mapsecrets file, each
593 user can login to the SQL database with a different username and
594 password, you can utitilize the security model of the SQL database as
595 well. Also, each username here can point to a different configuration
596 directory where you could store user-specific configuration info. Then
597 you could link each username to one-to-many agents.
598 (The web demo works using a trivial version of this.)
600 Yes, queue processing or the equivalent via checkpoint fields on various
601 talbes (which you pick up via a pretty simple SELECT) would be really
604 default (and ordering) state/county/country config file
606 cust_main_county table to provide a preferred ordering, so the most common
607 entries would be at the top of the selection box. automatically, based on
610 hmm... maybe svc_acct__shell should check off the legal shells list if
611 applicable? yeah... cool.
613 payinfo field should me much larger than 16
616 [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.
618 javascript (yuck!) "are you sure?" confirmation on cancelations, etc.
619 (view/cust_pkg and view/svc_*)
621 get rid of time2str("%D") which formats dates in a non-y2k-safe looking fashion
622 (all the actual date handling uses UNIX timestamps and is fine)
624 uncomment expire in view/cust_pkg.cgi and find the expire cron from fsold
627 one-time/per-customer/? changes in rates and descriptions ('remembered
628 invoices'): implement by creating a new package on the fly... but it isn't
629 associated with any agent types so it won't show up for other customers to buy.
630 (but also... make sure they go away when the customer does! - need this? :
631 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
632 with custnum and partpkg (like type_pkgs)
633 (what happens if you hit "custom pricing" but the pricing is already custom?)
635 Lay out any remaining ugly forms better.
637 remove "records identical" warning? gets in the way of more important stuff.
638 or fix logic which tries to update identical records??
639 1.2 should be quiet enough that the error log is useful, hopefully.
641 Postgres has a maximum column length of 31 characters (but see NAMEDATALEN in
642 postgres_ext.h). part_svc has columns like: svc_acct__radius_Attribute_flag
643 (22 characters!) It seems that stuff over the limit is silently ignored,
644 so we get 4 characters back. So, Radius_Attributes are max 13 characters with
645 stock Postgres. see rfc2138 for what's affected
646 What's a good fix? (besides recompiling postgres with NAMEDATALEN 64)
647 (mysql has a 64 character max column length. others?)
649 [Mon Mar 29 06:57:56 1999] -e: Use of uninitialized value at /usr/lib/perl5/Date/Format.pm line 333.
650 (when sending mail in cust_main.pm::bill or svc_domain.pm)
652 look at DBIx::Recordset! (and Tie::DBI, and...)
654 undefined conf/lpr gives this uninfomative error:
655 [Fri Feb 26 16:42:36 1999] bill.cgi: Can't do bidirectional pipe at
657 l5/site_perl/FS/cust_main.pm line 629.
658 [Fri Feb 26 16:42:38 1999] bill.cgi: Error closing : Broken pipe at
660 l5/site_perl/FS/cust_main.pm line 631.
661 So give a meaningful error!
663 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
665 i10n: Apache::Language
667 Apache::Session? Other useful Apache::* ?
669 email invoices are only sent for the BILL payby. If setup, should statements
670 (since they're not invoices) be sent for COMP and CARD as well?
672 $cgi->keywords is causing the (hard to trace) error:
673 Use of uninitialized value at (eval 5) line 5
675 edit/cust_main.cgi gives an uninformative error message:
676 > Can't call method "agentnum" without a package or object reference at
677 > /usr/local/apache-ssl/htdocs/freeside/edit/cust_main.cgi line 116.
678 if there are no agents.
680 (is this missing on any web screens? (easy with $cust_svc->label)
681 Add the ability for services to filter information up to the package level
682 for web screens, so you can select a particlar package based
683 on username or domain name, etc.
685 Allow a cancelled/suspended/active status from packages to bubble up to
686 the customer lists. Put active, then suspended, then cancelled accounts.
687 Similar ordering on the package listing inside a single customer.
689 false laziness: edit/cust_main.cgi got some parts copied from edit/svc_acct.cgi
690 the web interface in general needs to be redone in a more abstract way.
692 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.
694 subroutine the where clause (eventually all SQL) as OO perhaps (has anyone done this?)
696 add a select method to FS::Record?
698 one-time/per-customer/? changes in rates and descriptions ('remembered
699 invoices'): implement by creating a new package on the fly... but it isn't
700 associated with any agent types so it won't show up for other customers to buy.
701 (but also... make sure they go away when the customer does! - need this? :
702 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
703 with custnum and partpkg (like type_pkgs)
704 (what happens if you hit "custom pricing" but the pricing is already custom?)
706 You can't delete the stuff under administration yet. Add this,
707 _including_ making sure the thing you are deleting is not in use!
709 add links on view/cust_main.cgi to setup services, like view/cust_pkg.cgi
711 FS::cust_pkg _require_'s FS::$svc, but this won't work with %FS::UID::callback
712 loading of configuration. (pry need same idea, but will run immediately if
713 context allows). Looks like error is masked by 'use FS::cust_svc' which in
714 turn 'use's FS::{svc_acct, svc_acct_sm, svc_domain}' which is now explicit
717 Allow a cancelled/suspended/active status from packages to bubble up to
718 the customer lists. Put active, then suspended, then cancelled accounts.
719 Similar ordering on the package listing inside a single customer.
721 svc_domain.pm mail sending uses Date::Format which doesn't seem to pick up
724 view/svc_domain.cgi needs to know the domain might be unaudited (cosmetic)
726 remove whois_hack set to 1 for svc_domain.pm? add all known registries and
728 .us domains and others!
729 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...
731 turn on the depriciation warnings for [e]idiot in FS::CGI. Stop using [e]idiot
732 the last places it is (htdocs/search/ htdocs/misc/ htdocs/misc/process)
734 (test cust_main.pm with cybercash v2 and v3, especially with the callback
735 stuff AND with mod_perl w/cybercash v2 kludge in package main)
736 (callback stuff should be eliminated by now)
738 bah, table/itable/*table in FS::CGI is silly.
740 doc Apache::AuthDBI as well
742 Provide sample httpd.conf files.
744 hey look: Tie::DBI! Check that out. Override its commit with something that
745 does perl-side caching for ? a performance improvement and as an emulation
746 layer to plug in f.ex mysql's atomic transactions
748 Record.pm uses does some non-portable DBI things. MySQL and Pg seem fine.
749 Fix it anyway unless we migrate to Tie::DBI.
753 cust_bill.pm uses '==' comparison on dates because they're currently ints
755 config file for allowed card types
757 write instructions for adding new services w/svc_Common.pm. Get rid of all
758 places where svc_* tables are hardcoded (rename svc_acct_pop to part_pop so
761 test and document libapache-dbi-logger (woo!)
763 radius logfile parsing and perl expression check.
765 Fix in cust_bill BUGS:
766 There is an off-by-one error in print_text which causes a visual error (Page 1
767 of 2 printed on some single-page invoices).
769 fields should be a method against a FS::Record or derived object, as well as
770 being something you can call as FS::Record::fields('tablename'). Might
771 even be able to handle both in the same routine (that would be neato).
773 Immediate removal of incorrectly entered check payments (can't take too
774 long to do this, or accounting is fubared).
776 Add code to move from one service to another (POP to SLIP/PPP, etc.).
777 This _should_ be possible by working off the rules in part_svc rather than
778 hardcoding anything in. The rules in part_svc may need some elaboration,
781 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.)
783 (bring back from fsold, ) Generalize config-sending stuff and make more configurable.
784 Expand the HylaFAX interface (also possibly generalize for other fax
785 softwar ie .comfaxe); allow things like arbitrary faxes of sales
786 literature, specific troubleshooting documents and so on. Maybe even
787 allow users to do this (though that might not belong in Freeside).
789 misc/process/sendconfig.cgi
790 Configure fax recipients via a separate box rather than using the finger
791 name or first+last from cust_main.
793 move all phone number logic out of Freeside - let HylaFAX or whatever
796 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?!
798 should be able to link on some field in email alias (right now you can link
799 on username or domain with a fallback to svcnum)
801 generalize and make configurable new invoice printing scheme in FS::cust_main::collect (past due)
803 deleting an svc_domain should delete all associated svc_acct_sm records.
804 same with a svc_acct.
806 periodic password encrypter
808 Automated, configurable notification, suspension and cancellation of
813 Allow for a future setup date on accounts.
815 sub AUTOLOAD in FS::Record should warn? die? if used with a non-existant column
818 edit (not just import, export and allow default/fixed) arbitrary radius stuff
820 edit/svc_acct.cgi and edit/process/svc_acct.cgi should deal with arbitrary radius stuff
822 radius import should take DEFAULT entry and put it in /var/spool/freeside/conf/radius-default ; svc_acct.export should use it (and doc)
824 in UI, s/State/State\/Provence/go and s/County/County\/Locality/go
826 what else (besides l10n) for i18n? (money!)
828 audit htdocs/* for things that should be libraried and things that should be
829 new methods on the objects (need to do this before implementing a new UI)
830 all the big things are done
832 some places we die() where we should &FS::CGI::idiot (and perhaps vice-versa).
833 Decide based on whether or not the "error" should show up in logs.
835 all .cgi's should use standard header/footer and idiot() subroutines. maybe HTML:: perl modules
836 for HTML creation. Maybe Embperl or something along those lines. ?
838 When running bin/bill, Fix this (Annoying but harmless):
839 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 99, <ADDRESS> chunk 4.
840 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 102, <ADDRESS> chunk 4.
841 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 105, <ADDRESS> chunk 4.
843 all cgi (but internal to the isp) places where package names are listed should also have
844 comment (like agent_type)
846 clean up $recref and other silliness and use -> calls where possible, or
847 one other alternative. clean up everything else.
848 should FS::Record use Tie::Hash? That would be very clean, but where do we
849 store the other information? Maybe you could ask any FS::Record object for a
852 change all file access from regular open(FILE,) stuff to OO, because of
853 problems scoping and passing filehandles like that.
855 the web interface should create a new object and use it instead of a blank
856 form for new records. the create method of svc_ objects should set defaults
859 sub check in man FS::table_name should be rewriteen. Get rid of $recref
860 stuff. Make sure all fields that refer to other database are checked.
862 Integration with signup disks (are there any free ones? Netscape?).
864 One-button cancel (+refund) for lusers who can't get online.
866 Keep information on virtual web servers (hostname, IP, host machine,
867 directory, etc.) and export this information for importation into the ISPs
870 Remove requirement that the first mail alias be the catchall? Still make
871 sure only one catchall per domain is defined in any case, of course.
873 Ability to move cust_pkg records from one customer to another? (proably
874 will need to cancel the old and create a new like when we move services
877 Auto-increment expired cards one year, and try again?
879 More non-US stuff - zip codes, country codes, foreign currencies, etc.
881 cust_refund.{cgi.pm} need to do cards xaxtions. (now we only have cust_credit)
883 Nicer set of integrated reporting possibilities, like weekly sales totals
884 by customer, package, agent, referral, etc., aging reports sorted by lots
885 of different things, and so on.
887 Client/server setup for users to modify their own passwords, shells, etc,
888 via passwd or secure web interface (prelminary passwd/chfn/chsh
889 replacement done). Complicated by the fact that we don't want to allow
890 incoming connections to the machine running Freeside, so we probably need
891 to have a daemon on each external shell or web machine that is contacted
892 by the Freeside machine. Be very very careful for both traditional
893 security issues and DoS problems.
895 An extension of the above to allow users to modify selected parts of their
896 own information, order and cancel services. A web interface for new
899 Expand domain name stuff to house all domain information. Export
900 named.boot/named.conf (primary and secondary) and named.{domain} files.
901 Add more registries (not just InterNIC's com org net edu)
903 Nice postscript paper invoices, rather than current ASCII invoices.
905 think about race-condititions in FS::Record and derived ->check ->insert
906 and so on, uid and username checks in svc_acct, etc.
908 Move to rsync over ssh file exportation rather than scp.
910 check 'n fix the proactive password checker. (cracklib?)
912 refunds of "BILL" payments: generate pseudo-check.
914 write batch senders and batch parsers for the different credit card processors
916 More CC processors/methods.
918 you should be able to fiddle the setup date in cust_pkg. (at least initially)
920 delete options in administration section
922 write a generic batch senders and batch parsers.
924 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
925 type stuff from cerkit)
927 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)
929 you should be able to get column types as a method against an FS::Record object
930 as well as dbdef->table($table)->column($column)->type
932 move to perl module for fuzzy and soundex searching.
934 package view needs to list extraneous services; we need to prevent the
935 creation of them so this never happens (and mark it as such in the source)
936 (the creation problem should be fixed - though they will still happen if people
937 fsck around in the data manually, so list them anyway)
939 add attribute dictionary to fs-setup as a menu, plus analyze users file to
942 Check for and report on duplicate billing accounts (cust_main, though many
943 will have a need for these so probably don't disable them outright.)
945 create a ->warn as well as a ->check method for all FS::table classes?
948 something to automate making a release and updating the web demo
950 export a debian-style (also redhat and?) /etc/group file aswell!
952 svc_acct_sm.import qmail import should pull in recipientmap people too.
954 .pm's like svc_acct.pm which need to do time-consuming things like ssh remotely
955 should fork and do them in a child.
957 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.
959 get some of { city, county, state, zip } from the missing bits if
960 possible (where can i get the data to do this? usps.gov?)
962 additional interfaces (perltk? java?)
964 Put the GPL notice in all files.
966 integrate w/IDEA's signup server
968 $cust_bill->owed database field to be eliminated, replaced by a method call
969 that calculates on the fly. make sure to grep for ->(get|set)field('owed')
970 same for cust_credit->credited
972 Export quota information.
974 move all configuration to a central place. maybe in blob's in the
975 database. maybe even things like the code to execute when a username is
976 changed can be in there, so less of the distributed scripts change between
979 Implement setup and recurring fees as Safe perl expressions rather than
980 numbers, to allow for variable-rate services. Backwards compatibility is
981 obtained because { 43 } in perl is still 43. :) Define API to pass
982 starting and ending dates and any other necessary data to expression
983 (fees are currently evaluated as Safe expressions but more work needs to
984 be done to define an opmask for various needs, write examples
985 (usage-based billing, etc.) and so on).
987 Add the ability to modify the next billing date in cust_pkg, and take
988 appropriate action. This will allow the implementation of pro-rate/1st of
989 the month billing as well as the ability to manually fiddle with
990 anniversary dates in cust_pkg, so you can sync a customer's anniversary
991 date even if you're using anniversary billing (manually or automatically).
992 (now with above, we need to have a way to automatically pro-rate /^(\d+)$/
993 charges - anything more complicated should figure it out itself given
994 starting and ending dates [document that!])
996 Daily Radius log parsing into database; other logfile formats?
998 Callbacks to enforce hourly limits on accounts (suspend until the end of
999 the billing period?), for those who limit customers rather than tack on
1002 Flag packages (part_pkg) as taxable or non/taxable as some ISPs (for
1003 example) need to charge tax on equipment but not service (separate flags
1004 for setup and recurring fee... or perhaps a setup_tax, setup_notax,
1005 recur_tax and recur_notax fees, and possibly something more flexible if
1008 Allow for a variable number of invoices for customers who need multiple
1011 Add a mail alias service with table svc_acct (not domain mail aliasing
1012 which is domain with svc_acct_sm)
1014 (bring back from fsold) Change customer comment field from its current kludge to something more
1017 Better work orders with more information. Should eventually open a ticket
1018 when we have such a thing.
1020 edit/process/svc_wo.cgi
1021 Call tracking and trouble tickets.
1023 More accoutability for complimentary accounts: approval, expiration, term
1024 (no more than x months in advance) and notification.
1025 Flag particular users (or all users, for that matter) as having their
1026 passwords hidden and/or locked from users of Freeside (maybe need Freeside
1027 security levels first?).
1029 Better Freeside-level configurable access, for those ISP's who have
1030 employees they can't trust. Right now you're "stuck" with setting up
1031 .htaccess stuff yourself. This should really just be integrated.
1033 configuration/setup should get web interface
1035 /usr/local/etc/freeside should be configurable
1037 (probably as part of some automated installation process?)
1039 This requires some serious magic in FS::Record:
1040 ok, if date_type in fs-setup is to be something besides int,
1041 now we need to create wrappers
1042 for them so they behave identically across RDBMS's, ie date pops out as as
1043 UNIX timestamp (or an object of some sort? maybe even a blessed $obj which
1044 is a string not a hashref for backwards compatibility?) and so on. (remember
1045 to treat '0' as Not a Date instead of 1/1/70.
1047 Add Freeside-level transactions for RDBMS's which don't support
1048 transcations? (Currently we assume a minimal RDBMS which has no rollback,
1049 transactions or atomic updates). Or just require a RDBMS that supports
1050 rollback and/or atomic updates and get rid of the work-arounds? The /rdb
1051 interface had this kludge on top of it but is a technical dead-end in most
1052 other ways, unless it can gain an SQL parser and DBD interface.
1054 if i'm really bored, find the /rdb interface in fsold and port it to NoSQL,
1055 and while I'm add it add interfaces for AnyDBM_File tied hash.. hmm. Shouldn't
1056 an FS::Record have something to do with a tied hash? But we don't want
1057 performance to go gaga... maybe something with commit to help out here?
1059 Ok: FS::Record gives you a tied hash, and you get methods for commit, etc.
1061 Better automated comparison of our CC records with processors (CyberCash,
1062 at least, has not always had 100% accuracy, though recent versions are
1065 Expect or other pty based login check, where we actually connect to a
1066 terminal server or shell machine and test logging in as the user (if we
1067 are keeping a cleartext password for that user) (This is something tech
1068 support often needs for new customers)
1070 Use cust_main table for pre-sales tracking as well?
1072 Automatic commision report and check generation via freq and prog (to
1073 become a Safe perl expression) fields in agent table, and possibly others.
1075 Database and add a mailed-out date and method for disk/CD mailing, so a
1076 customer can call and you can say, "sent on xx/xx/xx via {US Mail, Fedex,
1079 Inventory tracking for physical items such as routers (for sale or
1080 lease... probably doesn't make a difference in the ordering... but if you
1081 cancel a router lease the inventory should come back. hmm.)
1083 -- Matt's wishlist ---
1085 From matt@michweb.net Fri Feb 20 16:39:53 1998
1086 Date: Thu, 19 Feb 1998 23:20:11 -0500
1087 From: Matt Simerson <matt@michweb.net>
1088 Reply-To: quadran-developer@netgoth.com
1089 To: quadran-developer@netgoth.com
1090 Subject: Re: Welcome to quadran-developer
1092 >Whats it based on and what is it supposed to do? I'm interested, but
1093 >unfortunatly, I don't have that much time to help on the project (I'm busily
1094 >working on one of my own based around MySQL and Qt right now -- don't know
1095 >if it will be GPL'ed or not yet -- we'll probably just use it in house since
1096 >it is designed around our system)...
1098 That's what I set out to find, but didn't find anything on the web site.
1099 I'm looking for something that will do the following:
1101 Single point of entry for users on a secure system:
1102 Creates account on user (public) systems
1103 update /etc/passwd/master.passwd file
1104 update radius database (if necessary)
1105 Set up up disk quotas (although I hacked adduser to do this)
1106 Option for adding user to a mailing list(s)
1107 Export of new user info to customizable report (for automated entry
1109 accounting software, etc...)
1112 Export credit card info for batch processing and have hooks built
1113 in for other forms of electronic processing.
1114 Batch-Payment (apply payments from formatted text file).
1115 Customizable reports for manual entry/importing into Accounting
1117 Email or laser print invoices
1118 Sanity checks credit card numbers before processing (code available)
1120 Simple method for disabling an account.
1121 Arbitrary Expiration Dates (on a given day, in x days)
1123 Changing password to '*'
1124 Virtual customers disabling dns, http server, log processing, etc..
1126 Billing for different account types:
1127 Dialup monthly flat rate. Prorates for partial months.
1128 Dialup monthly flat rate for x hours + hourly usage.
1131 Virtual Web accounts - w/multiple mailboxes
1132 Leased line accounts
1133 Disk space used over quota.
1134 Tech support minimum + hourly charges
1135 Other for misc stuff (modem, RAM, etc...)
1137 Per user definable RADIUS attributes (ties in with above)
1140 IP filters (for dialup email only)
1142 Keep logs of modem usage generated daily from radius accounting logs stored
1143 on multiple radius servers.
1145 Keep logs of disk usage generated from quota.
1147 Method of adding virtual domains to your system:
1148 Automatically grabs an IP address from a preassigned pool.
1149 Creates a domain.com database file from database fields
1150 Updates /etc/named.conf or /etc/named.boot and reloads named.
1151 Add's virtual.com to /etc/sendmail.cw or qmail control files.
1152 Edits your web servers httpd.conf file and restarts http server.
1153 An optional section for adding vif's can be added if the users OS
1154 supports adding them on the fly. Otherwise it's up to the end
1155 user. Make a hook that can run a custom script that the user
1156 tweaks for his system.
1157 Update or create the config file your web stats analyzer needs. I've
1158 done this for analog (free) and http-analyze. Probably
1159 should only officially support analog and let users hack
1160 it to their hearts desire.
1161 I've already written scripts that do most of the virtual web stuff on my
1162 system...in bash. Shouldn't be hard for a perlmeister to convert. In fact,
1163 as long as all the info was stored in the database (username, domain name,
1164 and ip pool) this could easily just be run as an external script that the
1165 user tweaks to match his system.
1167 We use a great accounting software (M.Y.O.B) that does all the AP, AR,
1168 Payroll, Tax stuff, and most everything else we could need. It's already
1169 set up for the type of checks we have, etc, etc... I just need something to
1170 do the billing part. I can import/export sales and payments directly once
1171 the billing part is done. You can't write accounting software as good as