1). In confs, update works well, delete has an issue with on delete cascade.
2). Saves state properly. Now just need to create a front-end to query for volunteer organizers.
1). Directions are in database_functions.
2). Initial population occurs on first submit.
3). Interests can be changed or deleted
4). It isn't a GUI interface, but it is useful for those without a MySQL understanding.
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.
also ..
1). zip to Zip Code .. some day will need to make international
2) changed Fill-in Form to "Check them out!" for volunteer interest .. subject to real world testing.
- 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.
1). This selector turned of edit when clicked, but because of the way it was construed it was hiding the label. Only became obvious when the validation tests were added.
1). Most collectives require only one shop at a time, but YBDB provides a way to handle 2 concurrent shops in the same location. The current shop will be shown, and users will have to remember the number of the previous shop to enter into the transaction. Note: Remote shops function independently via there IP identification.
1). Relates an on load selector with hide() that has been preempted
by the new error validation. But will watch to make sure new
bugs haven't been introduced.
Jonathan Rosenbaum