You will need to write a separate PHP file or put it at the top of each registration form that handles POST request. Look at examples using PHP's $_POST array.

To see what happens when you submit a form, try using echo print_r($_POST) to see the contents of the array.

Are we going to allow the user that's logged in to change his/her password? If yes, make a page for it.

Add/edit/remove stuff. Make sure all the basic functionality is working so a user who has never seen the system doesn't run into any problems.

Update columns so they fit properly

• Truncate notes to x characters (maybe 15?)
• Smaller font for Email, Phone, and Signed Up
• Active status: Y or N
• Standardize row height

Donors table does not update the entry after edit.

Look at the top of include/forms.php. Make sure all select boxes follow that same idea:
query the db, fill the options, print in the correct place.

Get the latest data from Google Docs and convert it to SQL inserts. Then insert into the production DB.

Then double check using the CPanel and ensure everything matches up with what was in Google Docs.

update what columns are written on exports for modified tabs (distribution sites, and others?)

Everything on the CPanel requires User Authentication (email and password). All views/edits/adds/deletes need to be enforced in ajax.php in the getters and setters.

enforce and validate required field on each Add and Edit Forms

Some of our select boxes are really big so it would be nice for the use to be able to start typing to filter the results.
Check out http://jqueryui.com/demos/autocomplete/#combobox

This is low priority but should be a quick fix.

Format the phone number regular expression for add/edit form inputs and add regex to any other inputs that require it.

Grower Registration Form

• It looks like the grower still needs to fill out the number of trees and the tree height in order to submit the form. I think we came to the conclusion that these should not be required because if they are registering their vegetables, these questions would not apply.
• Entering their email also shouldn't be required, as some of our growers are older and do not have email addresses.
• Under Tree Information, it should say, "How many different types of trees (or other kinds or produce) would you like to register?"
• Under "Tree Type 1" and before "Tree Type*" should include the line, "Produce other than tree fruits can be registered by selecting "Other" below."

Volunteer Registration Form

• In italics under "Preferred Days to Volunteer," it should read, "Note: Harvest Events are usually two hours and generally take place over the weekends."

This should be fun. I'm not sure which email addresses to use for testing so if you have a junk address, let me know. I want to do a batch of at least 50. Hopefully site88 has a mailserver we can use.

The add/edit form needs to use checkboxes, not a select box for the harvest months. See the registration-grower.php file to see how I did it. Also, remove None as an option from the DB since selecting 0 checkboxes is the same as none.

I just got off the phone with Gillian and we decided to make "Number of trees of this type" and "Tree Height" optional. This means the only required field is "Tree Type" and allows the grower to register vegetables (select "other" then enter information in the field for varietal).

When updating a volunteer from active to inactive do not show 1 or 0

We need to escape every string from the user that is appended to a SQL query. Anywhere you see $sql there should be no concatenation with $_REQUEST strings as they may contain apostrophes or other SQL queries.

We need to add a feature for custom searches (things that cannot be searched using the jquery datatable). This will actually need to send an ajax request which will query the DB. I suggest making a search.php with search cases in it similar to ajax. Maybe just include search.php in ajax.php to simplify.

trees - search by harvest months
distrib sites - search city, zip code
events - search date, city

Hide all fields that have "_id" in the name. Also make sure that all foreign keys in the db have "_id" in the name. For example "source" should be "source_id" in the volunteers table.

We need to create an email system that allows for mass emails to be sent "simultaneously" in order to inform volunteers of future events and such. It was mentioned that we may utilize blind-carbon-copies or queued messaging in order to do this efficiently.

Need to implement auto responses. See Auto Responses GWP.doc

We need forms to popup when a record is clicked in the table in order to edit the record (same form is used for adding). Just make a

<form id="volunteer">
<input type="text" name="first_name" required="required" />
<input type="text" name="last_name" required="required" />
</form>

You can add these to their own file and we can merge them later when we have a working backend.

Need to complete this html form and save a demo to gh-pages branch.

• git clone [email protected]:styfle/The-Harvest-Club.git
• git checkout gh-pages
• git add volunteer-registration.html
• git commit -m "Added volunteer registration form."
• git push origin gh-pages

That should do it!

It will eventually be changed but for now, we need to write a complete SQL DDL and maybe add some temporary inserts for debugging. Please append to the file I have already uploaded called createTables.sql and write well written comments.

Remember we are going to merge the admins table into the volunteers table and make sure to give them all permissions. Of course, standard volunteers will have no permissions and will have a NULL password.

Fernando, what's the status on this? It doesn't look like it is working.

The export function needs to be added to allow Harvest club volunteers and employees with sufficient permissions to export information in the database into Excel. We decided to use CSV in order to accomplish this.

Table

• Add event number as first field in event table. Probably call the column "Number" or "Event Number"

Dialog

• Change the field that says "Tree | Number | lbs" to "Tree | Number | Total lbs"
• Adding a new event without a time doesn't refresh the table for some reason.

Distributions needs Delivery Days/Hours in addition to Notes.

I would just add a new field at the end of distributions table to avoid breaking anything. Then just add a textarea on the form called "Delivery Day/Hours" and make sure the ajax.php can handle both add and update with the new field.

The Database class has a nice feature to escape your query for you. I haven't tested so tell me if it breaks.

include('include/Database.inc.php');
// say you get $tablename and $first_name from $_POST array
// make sure they are set first. if not die and tell the user why
$sql = "SELECT * FROM %s WHERE first_name = '%s';";
$r = $db->q($sql, array($tablename, $first_name));
// now do whatever you need to with result

That should get you started. See ajax.php for more.

Secondly, I think these can actually be included in the top of the form files by using require_once('include/submit-grower.php') and such. This will perform the checks and print the message on the current page. First fix the $db issue, then we can look at including it.

I found a huge flaw. Since the volunteers and growers are pre-processed, they never get updated unless you do a page refresh. So after adding a new grower...you can't add a tree for them! We need to fix this ASAP!

The forms affected by this are Trees and Events since they both have select boxes!

Each row needs a checkbox so users can select multiple rows and perform operations like email and export selected rows.

1. Exec
   • add/delete users
   • change permissions
   • add/edit/delete donor
   • only ones who can delete
2. Admin
   • view/add/edit/approve growers volunteers
3. Harvest Captain
   • add/edit/view events distribution
   • view growers volunteers
   • export growers volunteers
   • notified when grower or volunteer approved by admin (not email, but notification table)
4. Volunteer
   • none