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.
due to coding that affected noUiSlider, and also caused payment_type not to be
recorded in the database because of the correlating javascript issue. Also,
this caused the Deposit Range not to work correctly.
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.
1) Pages will go back to shop_welcome (original behavior) but for these two pages. This prevents transaction pages from going back.
2) Added an About/Help link to the left.
3) Changed the width/margin of the associated tables so that it would line up withe new table presenting the menu links.
- 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
1). Adds configuration options to turn off waiver & email_list options
2). Puts waiver in Connections/waiver.txt
3). New MySQL waiver column added, receive_newsletter used for email_list.
1). This allows "close" to produce errors, although not actually prevent them.
2). This provides a return code for "save" so that the transaction history can be saved.
1). Some css improvments.
2). The beginnings of transaction history.
3). Trying to find out why the window reloads twice on transactions without errors.
Jonathan Rosenbaum