* based on the SWEAT_EQUITY_LIMIT with discounts applied,
* based on 1 to 1 (1hr of volunteering === 1hr of free stand time) regardless of the SWEAT_EQUITY_LIMIT
When and existing contact was updated it would produce an error that the
contact already existed, and a new middle name needed to be used, also when
created a contact without adding a first and/or last name the same error was
produced. This fix corrects that bug.
0) concurrency issue, one contact_id was edited by 2 or more terminals
1) Better than having a new contact_id created everytime the contact_add_edit page is opened which was the behavior of the original program.
2) Still need to clean-up the code a little, and do a little bit more testing, but appears to be working nicely.
3) Still uses GET for initial setup, a todo to change.
4) Glad the bug was found, and now is fixed.
Originally, deposits of $0 (amount > 0) would not be considered real deposits, however, there may be shops where only non-monetary transactions occurred (amount >= 0) which would be useful to record in an accounting program.
One caveat, if a monetary transaction is recorded, but the depositor only enters $0, the deposit will show "Difference: n/a", however this should be a cue since it should be obvious that a real world deposit of $0 would not be made at a bank.
- mailman specific
- has been tested to work properly for both subscribe, and unsubscribe
- uses node.js
- two stage security
1) password is specific to connector for recognization
2) password used by list not kept local
- ssl used for all communication
- yeah!
Define a url for an email connector that will connect to an email list.
The url can be a server:port, program, etc.
Name (First, Last) email address, and connector password will be sent to the connector.
The purpose of email connectors is to provide autonomy in the choice
of email services and programs. E.g. mailman, googlegroups
See ./examples for an example connector
Jonathan Rosenbaum