1 $Id: TODO,v 1.41 2000-01-30 06:11:09 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
11 by platinum (jedgar at fxp dot org) on Thursday September 30, @07:13PM EDT (#4)
12 (User Info) http://www.fxp.org/~jedgar
13 The links above are your best bet for basic cvs server configuration. Once you have a pserver set up, you
14 may consider using cvs via ssh. All you need to do is the following:
16 1) Have ssh and sshd set up on the client and server machines
17 2) Set CVSROOT="joe@example.com:/home/ncvs"
18 3) Set CVS_RSH="/usr/local/bin/ssh"
20 (Obviously, insert the proper host/paths above)
22 You can also set up cvs/ssh to not need a password every time (similiar to an initial 'cvs login'):
24 1) run ssh-keygen on client machine using no passphrase.
25 2) copy/add ~/.ssh/identity.pub on the client to ~/.ssh/authorized_keys on the server
26 (man ssh for more details)
28 The main reason I mentio
30 by platinum (jedgar at fxp dot org) on Thursday September 30, @07:13PM EDT (#4)
31 (User Info) http://www.fxp.org/~jedgar
34 There's no way to do this currently, though it would be pretty
35 straightforward to modify the source - specifically, the _collect_
36 subroutine in FS::cust_main.
38 On Mon, Dec 13, 1999 at 04:05:32PM -0700, Jeff Garner wrote:
39 > Freeside will e-mail my users when they are billed if they are setup as
42 > When setup by credit card it does not e-mail them. Is there a way to
43 > turn on e-mail invoices for those who are billed via credit card? Kind
44 > of like a recipt of billing....
47 doc: http://www.softagency.co.jp/mysql/qmail.en.html
49 sql1992.txt standard is 18 character column names. shoot for that, not just
50 32 (postgresql default)
52 Also note that (AFAIK) Freeside won't display any package that has more
53 than one service on the "Add Customer" page. The reason for this is
54 because there's no way to dynamically alter the displayed html form
55 based on which package is selected. One possible solution would be to
56 make an additional page that's used in the signup process that would
57 display the form for each package, like a MS-style "Wizard". The first
58 page lets you select the package, then the second page has the custom
59 form with fields for each service in that package and a save button. Of
60 course, that would require a little perl work.
63 Scott Cruzen <sic@boernenet.com>
66 Your suggested script with back up /usr/local/etc/freeside, but will miss
67 any database not named `freeside'. Both of our scripts are specific to
68 MySQL. If you're interested in contributing to Freeside, maybe you could
69 work on a script which: reads the mapsecrets configuration file and then
70 each secrets file to find out what specific database engine(s) (MySQL,
71 PostgreSQL, etc.) and database(s) need to be backed up, then does so,
72 serializing backups of the same engine, i.e. stop mysql, do all the mysql
73 backups, start mysql, stop postgresql, do all the postgresql backups,
74 start postgresql, etc.
77 > mysqldump -t freeside > fs-backup.sql
79 > tar -Pzcvf fs-backup-`date +%y%m%d%H%M%S`.tgz fs-backup.sql /usr/local/etc/freeside/
82 I chose to use counters in the filesystem because there is no standard way
83 to get the value of an auto-incrementing keyfield which is common across
84 all databases (as seen through DBI/DBD).
86 It certainly wouldn't be a bad idea to use the database-specific methods,
89 htdocs/edit/svc_acct.cgi:
90 (Does the `*HIDDEN*' show up when you are adding a new account, and
91 specify the password, then receive an error and are returned to the form?)
94 Thought some of you might be interested in this:
96 <ftp://ftp.minivend.com/pub> has CyberCash compatibility modules for
97 Paymentnet <http://www.paymentnet.com> and Authorizenet
98 <http://www.authorizenet.com> which should allow you process transactions
99 using those services as well as CyberCash.
101 The files are named CCLib.pm.paymentnet and CCLib.pm_authorizenet,
102 respectively, and are installed by renaming to CCLib.pm and moving to your
103 site_perl directory. Otherwise, follow the directions for Cybercash v2 in
104 htdocs/docs/config.html
107 fs_passwd/ is a client-server replacement for the `passwd', `chfn' and
108 `chsh' commands that updates the Freeside database. (so for that to be
109 useful, you'd have to be exporting that data periodically)
111 fs_radlog/ is a client-server RADIUS log parser that stuffs the data into
112 SQL. It isn't finished, and probably won't be unless someone who I can't
113 convince to use one of the RADIUS daemons that logs to SQL directly pays
114 me money or something.
116 fs_signup/ is a client-server signup server. i'm just finishing it up
117 now; probably isn't on your machine yet.
120 http://www.sisd.com/freeside/list-archive/msg00812.html
122 package definitions should be implicit allow wrt agent types, not implicit deny
123 (with the old behavior possible via a config file)
125 > So is there anyway it could be setup to allow you to select a "primary
126 > service" from each package? This service would be the one you were prompted
127 > for. Could the signup server then be expanded to allow users to go into
128 > their package and "turn-on" the remaining non-primary services(using the
131 take the GPL'ed whois proxy stuff at www.geektools.com and turn it into
132 intelligence for Net::Whois.
134 A web version of the fs_passwd stuff would be nifty.
136 If you have Cistron authenticating directly from MySQL, you can replicate
137 in real-time instead of exporting periodically. See
138 <http://www.mysql.com/Manual_chapter/manual_Common_problems.html#Replication>.
141 <http://www.sisd.com/freeside/list-archive/msg00546.html>, and
142 <http://www.sisd.com/freeside/list-archive/msg00554.html>
144 and http://www.sisd.com/freeside/list-archive/msg00423.html
146 > > 5: Is there anyway to get freeside to send a sysadmin a warning when a
147 > > credit card has expired?
148 No, but there should be.
150 Put this in the doc (quoting Mark Wells <mark@pc-intouch.com>):
151 >Of course, thanks to the sheer coolness of SQL and MyODBC, you can do
152 >whatever reports you want in basically whatever application you want.
153 >There's no need for Freeside itself to do any reports at all.
155 middle names and titles
157 On Wed, Jul 07, 1999 at 01:11:40PM -0400, Frank Nazario wrote:
158 > Playing and entering information to Freeside i encountered the following
161 > View Customers by Agent
163 > View Pending Invoices
166 grep 'uncomment this to encrypt password immediately' site_perl/svc_acct.pm
167 Not to say that it shouldn't be a configurable option.
169 in site_perl/cust_main_invoice.pm (elsewhere?), error out if mydomain config file is gone
170 (at least until the idea of a default domain goes away)
172 FS::Record::qsearch does an eval every loop iteration (which is itself not
173 guaranteed to work across all DBD's and should be fixed). This has got to be
174 slow. Fix it. (I think recent Perls might have a way to accept a variable
175 there, no eval needed?)
177 Could you have added /bin/sync, /sbin/shutdown, and /bin/halt to the
178 `shells' configuration file before importing, and removed them afterwords?
179 (even better if svc_acct.import did that automatically - it could just
180 munge and restore @FS::svc_acct::shells... hmm.)
182 > BTW, Ivan, I am trying to verify in an additional database table that a
183 > particular user doesn't exist. This database is used to store email aliases a$
184 > additional POP boxes for our customers (kinda like AOL allows). I have toyed
185 > with the idea of just writing the aliases to an email only svc_acct that
186 > doesn't write to the password file, but that isn't really how I want to do it.
188 Actually, I think that's a pretty good way to do it. Cerkit contributed
189 support a little while back for svc_acct.pm and svc_acct.export for
190 multiple export targets. It needs to be cleaned up and documented, which
191 I'll try to get to soon. For this to work correctly, the svc_acct_sm
192 table should go away, along with the concept of a "default" domain.
194 default setting for new packages should allow all agents to purchase them...
195 with a config file for the old behaviour
197 fix or replace Term::Query (Quiz::Question doesn't do what i need)
199 Check config file reading stuff from CPAN
201 Authorizenet module from CPAN!
203 <http://www.math.fu-berlin.de/~leitner/mutt/faq.html> has a good y2k complience
206 I'm hoping Freeside can support arbitrailly complex pricing plans
207 because of a simple concept: all prices are perl expressions. So if
208 you use `19.95' for example, perl evalates that to be `19.95'. But if
209 you need to do a complex pricing scheme, you just need to write an
210 appropriate perl expression, which will most likely pull data from the
211 database to return pricing. Some things will already log to SQL; for
212 example most RADIUS servers can or have a patch available. Getting
213 Freeside to bill based on any sort of data then becomes a matter of
214 importing the data into the database.
216 There are some issues involved with pro-rating, partial month charges,
217 that sort of thing. Expressions will need a standard way to have the
218 applicable time/data ranges passed to them. Also the expressions are
219 currently running under the Safe perl module, and the opmask might not
220 be right in all situations. I'll try to spend some time working on
221 this if you are using it.
223 > 2. can customers view their bills on-line.
225 Not yet; it needs to be proxied from Freeside to a customer web server in
226 a secure way using something not completely unlike the fs_passwd,
227 fs_passwdd, fs_passwd_server trio.
230 > Lastly, if someone over pays on an invoice, the credit part does not flow
231 > over to other invoices..
233 The total balance flows over correctly, but individual payments don't.
234 The code you're looking for is in FS::cust_pay::insert
236 The question of what to do with overpayments that don't have another
237 invoice to flow into (yet.. or possibly not) is still an open one. The
238 legacy system Freeside replaced long ago had a separate place for this
239 (payments waiting for an invoice) for each customer, and it gave our
243 option to relax username uniqueness in favor of username+domain or mail/shell
244 vs. radius to ease import for isp's with namespace problems or who buy others.
246 do i have to store anything for radius realms besides regular radius attributes
247 (which are handled fine now)?
249 warn or complain or something when invoice_from is empty (and we use it)
251 Right now Freeside uses the `freq' field of a package definition as a
252 number of months. The specific section of code you're looking for is in
255 #change this bit to use Date::Manip?
256 #$sdate=$cust_pkg->bill || time;
257 #$sdate=$cust_pkg->bill || $time;
258 $sdate = $cust_pkg->bill || $cust_pkg->setup || $time;
259 my ($sec,$min,$hour,$mday,$mon,$year) =
260 (localtime($sdate) )[0,1,2,3,4,5];
261 $mon += $part_pkg->getfield('freq');
262 until ( $mon < 12 ) { $mon -= 12; $year++; }
263 $cust_pkg->setfield('bill',
264 timelocal($sec,$min,$hour,$mday,$mon,$year));
265 $cust_pkg_mod_flag = 1;
267 ..and when I went poking for this, looks like it tells us just what needs
268 to be done! Hehehe...
270 Date::Manip can handle cool things like "+ 1 month" (actually the current
271 case of /^(\d+)$/ would have to be added as a special case of "+ $1
272 month") and "+ 30 days" (what you need) and even "+ 5 business days" !
275 On Wed, Apr 28, 1999 at 08:38:16PM +0000, Kristian Hoffmann wrote:
276 > I can't quite seem to figure out how this exporting works. From what I
277 > understand, when you run svc_acct.export, it rewrites the /etc/passwd,
278 > /etc/shadow, etc. files. Is this only for initial setups with the
279 > export hooks being in the pm's?
281 You can use both, or just one method. The configuration files control
282 this. One of the things in the TODO is to take out the last few things
283 that aren't customizable wrt this and put them in config files.
285 http://www.daemonnews.org/199905/user-mgmt.html
287 Term::Query doesn't install out of the box from CPAN. Fix it (and get it
288 submitted upstream!), or remove requirement from bin/svc_acct.import and
289 bin/svc_acct_sm.import and take it out of the install instructions.
291 use this cool link to explain the Freeside API
292 ftp://cpan.nas.nasa.gov/pub/perl/CPAN/doc/FMTEYEWTK/easy_objects.html
294 Multiple tax rates by geographic region (county, state, and county) are
295 supported; just choose View/Edit tax rates from the main menu.
297 Multiple tax rates by package are not (yet) supported.
299 On Wed, Jul 07, 1999 at 12:13:36PM -0400, Shaun Batterton wrote:
300 > How would you handle something like multiple tax rates and multiple
301 > states? For example in Connecticut, they just changed computer and/or
302 > data processing services to 3% (whatever that is), and everything else
306 > Second, when trying to add a new user I get two types of errors; first one
307 > is when I place an e-mail address and select the "submit," Freeside
308 > complains with "Error: Unknown local account (specified literally)"
310 You probably put a (local) email address in for email invoices. Freeside
311 stores these as references to the database records, so (for example) they
312 follow username changes.
314 I'm guessing you put in the email address that you were creating, and got
315 that error because it didn't exist yet. Sounds like a buglet to me. I'll
316 try to fix that soon; in the meantime you can add the invoicing email
319 (workaround for postgres before 6.5) (unlikely to ever be implemented)
320 In the mean-time, this could probably be fixed with the reverse of
321 the kludge in FS::Record::new. This removes `$' and `,' from money fields
322 coming out of the database. Something which fixed up the data so Postgres
323 was happy with it could go in FS::Record::_quote, for data going into the
326 our data display problem might be a Freeside problem wrt not using
327 Oracle-compatible DBI syntax (uses the return value from $sth->execute as
328 a number of rows). Fixing this is on the TODO.
330 hooks for arbitrary commands out of configuration files
331 svc_acct.pm svc_acct_sm.pm etc.
333 Add this to a FAQ, along with doing it for middle names:
336 > What I'm finding difficult is how to easily
337 > customize fields. For example, I am trying to add a "middle name" field
338 > to the Customer Edit, view, etc. If I'm going about it right, it appears
339 > I have to edit the cust_main.cgi under edit and edit/process and the
340 > site_perl/cust_main.pm, as well as other things. Perhaps you could shed
341 > some light on the best way of doing this.
343 You have the basic idea. To implement that completely, I would:
344 - Add the new field to bin/fs-setup for new users
345 - Document the field in htdocs/docs/schema.html
346 - Document the change in a new file, htdocs/docs/upgrade4.html
347 * Run bin/dbdef-create
348 * Add the new field to edit/cust_main.cgi and edit/process/cust_main.cgi
350 For bonus points, I'd grep around for the various bits which use "$first
351 $last" or "$last, $first" and replace them with a method call in cust_main.pm,
352 , like search/cust_main.cgi
354 document security model:
355 Don't forget about Apache usernames - since, via the mapsecrets file, each
356 user can login to the SQL database with a different username and
357 password, you can utitilize the security model of the SQL database as
358 well. Also, each username here can point to a different configuration
359 directory where you could store user-specific configuration info. Then
360 you could link each username to one-to-many agents.
361 (The web demo works using a trivial version of this.)
363 Yes, queue processing or the equivalent via checkpoint fields on various
364 talbes (which you pick up via a pretty simple SELECT) would be really
367 default (and ordering) state/county/country config file
369 cust_main_county table to provide a preferred ordering, so the most common
370 entries would be at the top of the selection box. automatically, based on
373 hmm... maybe svc_acct__shell should check off the legal shells list if
374 applicable? yeah... cool.
376 payinfo field should me much larger than 16
379 [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.
381 javascript (yuck!) "are you sure?" confirmation on cancelations, etc.
382 (view/cust_pkg and view/svc_*)
384 get rid of time2str("%D") which formats dates in a non-y2k-safe looking fashion
385 (all the actual date handling uses UNIX timestamps and is fine)
387 uncomment expire in view/cust_pkg.cgi and find the expire cron from fsold
390 one-time/per-customer/? changes in rates and descriptions ('remembered
391 invoices'): implement by creating a new package on the fly... but it isn't
392 associated with any agent types so it won't show up for other customers to buy.
393 (but also... make sure they go away when the customer does! - need this? :
394 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
395 with custnum and partpkg (like type_pkgs)
396 (what happens if you hit "custom pricing" but the pricing is already custom?)
398 Lay out any remaining ugly forms better.
400 remove "records identical" warning? gets in the way of more important stuff.
401 or fix logic which tries to update identical records??
402 1.2 should be quiet enough that the error log is useful, hopefully.
404 Postgres has a maximum column length of 31 characters (but see NAMEDATALEN in
405 postgres_ext.h). part_svc has columns like: svc_acct__radius_Attribute_flag
406 (22 characters!) It seems that stuff over the limit is silently ignored,
407 so we get 4 characters back. So, Radius_Attributes are max 13 characters with
408 stock Postgres. see rfc2138 for what's affected
409 What's a good fix? (besides recompiling postgres with NAMEDATALEN 64)
410 (mysql has a 64 character max column length. others?)
412 [Mon Mar 29 06:57:56 1999] -e: Use of uninitialized value at /usr/lib/perl5/Date/Format.pm line 333.
413 (when sending mail in cust_main.pm::bill or svc_domain.pm)
415 look at DBIx::Recordset! (and Tie::DBI, and...)
417 undefined conf/lpr gives this uninfomative error:
418 [Fri Feb 26 16:42:36 1999] bill.cgi: Can't do bidirectional pipe at
420 l5/site_perl/FS/cust_main.pm line 629.
421 [Fri Feb 26 16:42:38 1999] bill.cgi: Error closing : Broken pipe at
423 l5/site_perl/FS/cust_main.pm line 631.
424 So give a meaningful error!
426 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
428 i10n: Apache::Language
430 Apache::Session? Other useful Apache::* ?
432 email invoices are only sent for the BILL payby. If setup, should statements
433 (since they're not invoices) be sent for COMP and CARD as well?
435 $cgi->keywords is causing the (hard to trace) error:
436 Use of uninitialized value at (eval 5) line 5
438 edit/cust_main.cgi gives an uninformative error message:
439 > Can't call method "agentnum" without a package or object reference at
440 > /usr/local/apache-ssl/htdocs/freeside/edit/cust_main.cgi line 116.
441 if there are no agents.
443 (is this missing on any web screens? (easy with $cust_svc->label)
444 Add the ability for services to filter information up to the package level
445 for web screens, so you can select a particlar package based
446 on username or domain name, etc.
448 Allow a cancelled/suspended/active status from packages to bubble up to
449 the customer lists. Put active, then suspended, then cancelled accounts.
450 Similar ordering on the package listing inside a single customer.
452 false laziness: edit/cust_main.cgi got some parts copied from edit/svc_acct.cgi
453 the web interface in general needs to be redone in a more abstract way.
455 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.
457 Portability: in FS::Record, $sth->execute does not return a number of rows for all DBD's. see man DBI
459 subroutine the where clause (eventually all SQL) as OO perhaps (has anyone done this?)
461 add a select method to FS::Record?
463 one-time/per-customer/? changes in rates and descriptions ('remembered
464 invoices'): implement by creating a new package on the fly... but it isn't
465 associated with any agent types so it won't show up for other customers to buy.
466 (but also... make sure they go away when the customer does! - need this? :
467 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
468 with custnum and partpkg (like type_pkgs)
469 (what happens if you hit "custom pricing" but the pricing is already custom?)
471 You can't delete the stuff under administration yet. Add this,
472 _including_ making sure the thing you are deleting is not in use!
474 add links on view/cust_main.cgi to setup services, like view/cust_pkg.cgi
476 FS::cust_pkg _require_'s FS::$svc, but this won't work with %FS::UID::callback
477 loading of configuration. (pry need same idea, but will run immediately if
478 context allows). Looks like error is masked by 'use FS::cust_svc' which in
479 turn 'use's FS::{svc_acct, svc_acct_sm, svc_domain}' which is now explicit
482 Allow a cancelled/suspended/active status from packages to bubble up to
483 the customer lists. Put active, then suspended, then cancelled accounts.
484 Similar ordering on the package listing inside a single customer.
486 svc_domain.pm mail sending uses Date::Format which doesn't seem to pick up
489 view/svc_domain.cgi needs to know the domain might be unaudited (cosmetic)
491 remove whois_hack set to 1 for svc_domain.pm? add all known registries and
493 .us domains and others!
494 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...
496 turn on the depriciation warnings for [e]idiot in FS::CGI. Stop using [e]idiot
497 the last places it is (htdocs/search/ htdocs/misc/ htdocs/misc/process)
499 (test cust_main.pm with cybercash v2 and v3, especially with the callback
500 stuff AND with mod_perl w/cybercash v2 kludge in package main)
501 (callback stuff should be eliminated by now)
503 bah, table/itable/*table in FS::CGI is silly.
505 doc Apache::AuthDBI as well
507 Provide sample httpd.conf files.
509 hey look: Tie::DBI! Check that out. Override its commit with something that
510 does perl-side caching for ? a performance improvement and as an emulation
511 layer to plug in f.ex mysql's atomic transactions
513 Record.pm uses does some non-portable DBI things. MySQL and Pg seem fine.
514 Fix it anyway unless we migrate to Tie::DBI.
518 cust_bill.pm uses '==' comparison on dates because they're currently ints
520 config file for allowed card types
522 write instructions for adding new services w/svc_Common.pm. Get rid of all
523 places where svc_* tables are hardcoded (rename svc_acct_pop to part_pop so
526 test and document libapache-dbi-logger (woo!)
528 radius logfile parsing and perl expression check.
530 Fix in cust_bill BUGS:
531 There is an off-by-one error in print_text which causes a visual error (Page 1
532 of 2 printed on some single-page invoices).
534 fields should be a method against a FS::Record or derived object, as well as
535 being something you can call as FS::Record::fields('tablename'). Might
536 even be able to handle both in the same routine (that would be neato).
538 Immediate removal of incorrectly entered check payments (can't take too
539 long to do this, or accounting is fubared).
541 Add code to move from one service to another (POP to SLIP/PPP, etc.).
542 This _should_ be possible by working off the rules in part_svc rather than
543 hardcoding anything in. The rules in part_svc may need some elaboration,
546 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.)
548 (bring back from fsold, ) Generalize config-sending stuff and make more configurable.
549 Expand the HylaFAX interface (also possibly generalize for other fax
550 softwar ie .comfaxe); allow things like arbitrary faxes of sales
551 literature, specific troubleshooting documents and so on. Maybe even
552 allow users to do this (though that might not belong in Freeside).
554 misc/process/sendconfig.cgi
555 Configure fax recipients via a separate box rather than using the finger
556 name or first+last from cust_main.
558 move all phone number logic out of Freeside - let HylaFAX or whatever
561 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?!
563 should be able to link on some field in email alias (right now you can link
564 on username or domain with a fallback to svcnum)
566 generalize and make configurable new invoice printing scheme in FS::cust_main::collect (past due)
568 deleting an svc_domain should delete all associated svc_acct_sm records.
569 same with a svc_acct.
571 periodic password encrypter
573 Automated, configurable notification, suspension and cancellation of
578 Allow for a future setup date on accounts.
580 sub AUTOLOAD in FS::Record should warn? die? if used with a non-existant column
583 edit (not just import, export and allow default/fixed) arbitrary radius stuff
585 edit/svc_acct.cgi and edit/process/svc_acct.cgi should deal with arbitrary radius stuff
587 radius import should take DEFAULT entry and put it in /var/spool/freeside/conf/radius-default ; svc_acct.export should use it (and doc)
589 in UI, s/State/State\/Provence/go and s/County/County\/Locality/go
591 what else (besides l10n) for i18n? (money!)
593 audit htdocs/* for things that should be libraried and things that should be
594 new methods on the objects (need to do this before implementing a new UI)
595 all the big things are done
597 some places we die() where we should &FS::CGI::idiot (and perhaps vice-versa).
598 Decide based on whether or not the "error" should show up in logs.
600 all .cgi's should use standard header/footer and idiot() subroutines. maybe HTML:: perl modules
601 for HTML creation. Maybe Embperl or something along those lines. ?
603 When running bin/bill, Fix this (Annoying but harmless):
604 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 99, <ADDRESS> chunk 4.
605 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 102, <ADDRESS> chunk 4.
606 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 105, <ADDRESS> chunk 4.
608 all cgi (but internal to the isp) places where package names are listed should also have
609 comment (like agent_type)
611 clean up $recref and other silliness and use -> calls where possible, or
612 one other alternative. clean up everything else.
613 should FS::Record use Tie::Hash? That would be very clean, but where do we
614 store the other information? Maybe you could ask any FS::Record object for a
617 change all file access from regular open(FILE,) stuff to OO, because of
618 problems scoping and passing filehandles like that.
620 the web interface should create a new object and use it instead of a blank
621 form for new records. the create method of svc_ objects should set defaults
624 sub check in man FS::table_name should be rewriteen. Get rid of $recref
625 stuff. Make sure all fields that refer to other database are checked.
627 Integration with signup disks (are there any free ones? Netscape?).
629 One-button cancel (+refund) for lusers who can't get online.
631 Keep information on virtual web servers (hostname, IP, host machine,
632 directory, etc.) and export this information for importation into the ISPs
635 Remove requirement that the first mail alias be the catchall? Still make
636 sure only one catchall per domain is defined in any case, of course.
638 Ability to move cust_pkg records from one customer to another? (proably
639 will need to cancel the old and create a new like when we move services
642 Auto-increment expired cards one year, and try again?
644 More non-US stuff - zip codes, country codes, foreign currencies, etc.
646 cust_refund.{cgi.pm} need to do cards xaxtions. (now we only have cust_credit)
648 Nicer set of integrated reporting possibilities, like weekly sales totals
649 by customer, package, agent, referral, etc., aging reports sorted by lots
650 of different things, and so on.
652 Client/server setup for users to modify their own passwords, shells, etc,
653 via passwd or secure web interface (prelminary passwd/chfn/chsh
654 replacement done). Complicated by the fact that we don't want to allow
655 incoming connections to the machine running Freeside, so we probably need
656 to have a daemon on each external shell or web machine that is contacted
657 by the Freeside machine. Be very very careful for both traditional
658 security issues and DoS problems.
660 An extension of the above to allow users to modify selected parts of their
661 own information, order and cancel services. A web interface for new
664 Expand domain name stuff to house all domain information. Export
665 named.boot/named.conf (primary and secondary) and named.{domain} files.
666 Add more registries (not just InterNIC's com org net edu)
668 Nice postscript paper invoices, rather than current ASCII invoices.
670 think about race-condititions in FS::Record and derived ->check ->insert
671 and so on, uid and username checks in svc_acct, etc.
673 Move to rsync over ssh file exportation rather than scp.
675 check 'n fix the proactive password checker. (cracklib?)
677 refunds of "BILL" payments: generate pseudo-check.
679 write batch senders and batch parsers for the different credit card processors
681 More CC processors/methods.
683 you should be able to fiddle the setup date in cust_pkg. (at least initially)
685 delete options in administration section
687 write a generic batch senders and batch parsers.
689 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
690 type stuff from cerkit)
692 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)
694 you should be able to get column types as a method against an FS::Record object
695 as well as dbdef->table($table)->column($column)->type
697 move to perl module for fuzzy and soundex searching.
699 package view needs to list extraneous services; we need to prevent the
700 creation of them so this never happens (and mark it as such in the source)
701 (the creation problem should be fixed - though they will still happen if people
702 fsck around in the data manually, so list them anyway)
704 add attribute dictionary to fs-setup as a menu, plus analyze users file to
707 Check for and report on duplicate billing accounts (cust_main, though many
708 will have a need for these so probably don't disable them outright.)
710 create a ->warn as well as a ->check method for all FS::table classes?
713 something to automate making a release and updating the web demo
715 export a debian-style (also redhat and?) /etc/group file aswell!
717 svc_acct_sm.import qmail import should pull in recipientmap people too.
719 .pm's like svc_acct.pm which need to do time-consuming things like ssh remotely
720 should fork and do them in a child.
722 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.
724 get some of { city, county, state, zip } from the missing bits if
725 possible (where can i get the data to do this? usps.gov?)
727 additional interfaces (perltk? java?)
729 Put the GPL notice in all files.
731 integrate w/IDEA's signup server
733 $cust_bill->owed database field to be eliminated, replaced by a method call
734 that calculates on the fly. make sure to grep for ->(get|set)field('owed')
735 same for cust_credit->credited
737 Export quota information.
739 move all configuration to a central place. maybe in blob's in the
740 database. maybe even things like the code to execute when a username is
741 changed can be in there, so less of the distributed scripts change between
744 Implement setup and recurring fees as Safe perl expressions rather than
745 numbers, to allow for variable-rate services. Backwards compatibility is
746 obtained because { 43 } in perl is still 43. :) Define API to pass
747 starting and ending dates and any other necessary data to expression
748 (fees are currently evaluated as Safe expressions but more work needs to
749 be done to define an opmask for various needs, write examples
750 (usage-based billing, etc.) and so on).
752 Add the ability to modify the next billing date in cust_pkg, and take
753 appropriate action. This will allow the implementation of pro-rate/1st of
754 the month billing as well as the ability to manually fiddle with
755 anniversary dates in cust_pkg, so you can sync a customer's anniversary
756 date even if you're using anniversary billing (manually or automatically).
757 (now with above, we need to have a way to automatically pro-rate /^(\d+)$/
758 charges - anything more complicated should figure it out itself given
759 starting and ending dates [document that!])
761 Daily Radius log parsing into database; other logfile formats?
763 Callbacks to enforce hourly limits on accounts (suspend until the end of
764 the billing period?), for those who limit customers rather than tack on
767 Flag packages (part_pkg) as taxable or non/taxable as some ISPs (for
768 example) need to charge tax on equipment but not service (separate flags
769 for setup and recurring fee... or perhaps a setup_tax, setup_notax,
770 recur_tax and recur_notax fees, and possibly something more flexible if
773 Allow for a variable number of invoices for customers who need multiple
776 Add a mail alias service with table svc_acct (not domain mail aliasing
777 which is domain with svc_acct_sm)
779 (bring back from fsold) Change customer comment field from its current kludge to something more
782 Better work orders with more information. Should eventually open a ticket
783 when we have such a thing.
785 edit/process/svc_wo.cgi
786 Call tracking and trouble tickets.
788 More accoutability for complimentary accounts: approval, expiration, term
789 (no more than x months in advance) and notification.
790 Flag particular users (or all users, for that matter) as having their
791 passwords hidden and/or locked from users of Freeside (maybe need Freeside
792 security levels first?).
794 Better Freeside-level configurable access, for those ISP's who have
795 employees they can't trust. Right now you're "stuck" with setting up
796 .htaccess stuff yourself. This should really just be integrated.
798 configuration/setup should get web interface
800 /usr/local/etc/freeside should be configurable
802 (probably as part of some automated installation process?)
804 This requires some serious magic in FS::Record:
805 ok, if date_type in fs-setup is to be something besides int,
806 now we need to create wrappers
807 for them so they behave identically across RDBMS's, ie date pops out as as
808 UNIX timestamp (or an object of some sort? maybe even a blessed $obj which
809 is a string not a hashref for backwards compatibility?) and so on. (remember
810 to treat '0' as Not a Date instead of 1/1/70.
812 Add Freeside-level transactions for RDBMS's which don't support
813 transcations? (Currently we assume a minimal RDBMS which has no rollback,
814 transactions or atomic updates). Or just require a RDBMS that supports
815 rollback and/or atomic updates and get rid of the work-arounds? The /rdb
816 interface had this kludge on top of it but is a technical dead-end in most
817 other ways, unless it can gain an SQL parser and DBD interface.
819 if i'm really bored, find the /rdb interface in fsold and port it to NoSQL,
820 and while I'm add it add interfaces for AnyDBM_File tied hash.. hmm. Shouldn't
821 an FS::Record have something to do with a tied hash? But we don't want
822 performance to go gaga... maybe something with commit to help out here?
824 Ok: FS::Record gives you a tied hash, and you get methods for commit, etc.
826 Better automated comparison of our CC records with processors (CyberCash,
827 at least, has not always had 100% accuracy, though recent versions are
830 Expect or other pty based login check, where we actually connect to a
831 terminal server or shell machine and test logging in as the user (if we
832 are keeping a cleartext password for that user) (This is something tech
833 support often needs for new customers)
835 Use cust_main table for pre-sales tracking as well?
837 Automatic commision report and check generation via freq and prog (to
838 become a Safe perl expression) fields in agent table, and possibly others.
840 Database and add a mailed-out date and method for disk/CD mailing, so a
841 customer can call and you can say, "sent on xx/xx/xx via {US Mail, Fedex,
844 Inventory tracking for physical items such as routers (for sale or
845 lease... probably doesn't make a difference in the ordering... but if you
846 cancel a router lease the inventory should come back. hmm.)
848 -- Matt's wishlist ---
850 From matt@michweb.net Fri Feb 20 16:39:53 1998
851 Date: Thu, 19 Feb 1998 23:20:11 -0500
852 From: Matt Simerson <matt@michweb.net>
853 Reply-To: quadran-developer@netgoth.com
854 To: quadran-developer@netgoth.com
855 Subject: Re: Welcome to quadran-developer
857 >Whats it based on and what is it supposed to do? I'm interested, but
858 >unfortunatly, I don't have that much time to help on the project (I'm busily
859 >working on one of my own based around MySQL and Qt right now -- don't know
860 >if it will be GPL'ed or not yet -- we'll probably just use it in house since
861 >it is designed around our system)...
863 That's what I set out to find, but didn't find anything on the web site.
864 I'm looking for something that will do the following:
866 Single point of entry for users on a secure system:
867 Creates account on user (public) systems
868 update /etc/passwd/master.passwd file
869 update radius database (if necessary)
870 Set up up disk quotas (although I hacked adduser to do this)
871 Option for adding user to a mailing list(s)
872 Export of new user info to customizable report (for automated entry
874 accounting software, etc...)
877 Export credit card info for batch processing and have hooks built
878 in for other forms of electronic processing.
879 Batch-Payment (apply payments from formatted text file).
880 Customizable reports for manual entry/importing into Accounting
882 Email or laser print invoices
883 Sanity checks credit card numbers before processing (code available)
885 Simple method for disabling an account.
886 Arbitrary Expiration Dates (on a given day, in x days)
888 Changing password to '*'
889 Virtual customers disabling dns, http server, log processing, etc..
891 Billing for different account types:
892 Dialup monthly flat rate. Prorates for partial months.
893 Dialup monthly flat rate for x hours + hourly usage.
896 Virtual Web accounts - w/multiple mailboxes
898 Disk space used over quota.
899 Tech support minimum + hourly charges
900 Other for misc stuff (modem, RAM, etc...)
902 Per user definable RADIUS attributes (ties in with above)
905 IP filters (for dialup email only)
907 Keep logs of modem usage generated daily from radius accounting logs stored
908 on multiple radius servers.
910 Keep logs of disk usage generated from quota.
912 Method of adding virtual domains to your system:
913 Automatically grabs an IP address from a preassigned pool.
914 Creates a domain.com database file from database fields
915 Updates /etc/named.conf or /etc/named.boot and reloads named.
916 Add's virtual.com to /etc/sendmail.cw or qmail control files.
917 Edits your web servers httpd.conf file and restarts http server.
918 An optional section for adding vif's can be added if the users OS
919 supports adding them on the fly. Otherwise it's up to the end
920 user. Make a hook that can run a custom script that the user
921 tweaks for his system.
922 Update or create the config file your web stats analyzer needs. I've
923 done this for analog (free) and http-analyze. Probably
924 should only officially support analog and let users hack
925 it to their hearts desire.
926 I've already written scripts that do most of the virtual web stuff on my
927 system...in bash. Shouldn't be hard for a perlmeister to convert. In fact,
928 as long as all the info was stored in the database (username, domain name,
929 and ip pool) this could easily just be run as an external script that the
930 user tweaks to match his system.
932 We use a great accounting software (M.Y.O.B) that does all the AP, AR,
933 Payroll, Tax stuff, and most everything else we could need. It's already
934 set up for the type of checks we have, etc, etc... I just need something to
935 do the billing part. I can import/export sales and payments directly once
936 the billing part is done. You can't write accounting software as good as