bug: use BASH as the interpreter for the rebuild file to see if that improves compatibility
bug: undo what I just did because it didn't help
Merge remote-tracking branch 'remotes/origin/dev/david/check_alarms' into dev/patrick/check_alarms
Added a sent field to the alarm content type

- added an integer/boolean field that will track if the text for
  an alarm has been sent yet. It's value will be 1 if sent, 0
  otherwise.
Added controls to prevent resending alarms

- Removed old measures to acheive the same task; they did not appear
  to work and were based on the user rather than the alarm. Also, it
  depended on keeping and searching through a log of users sent to.
  This increases the computational complexity a bit, and also raises
  the question of when such a log should be cleared.
- Used the field_sent field of the alarm content type in order to
  track whether a given alarm has been sent or not. This way
  we eliminate the need to track users.
Added the automatic sending functionality

- Moved the functional code from check_alarms_form_submit() to
  check_alarms() so that it could be called by the cron hook.
- Added Elysia Cron and other missed modules to the install profile
- updated tokens module to use the newest version
- NOTE: crontab has to be set up on the server.
Changed to send a question instead of timestamp
Added message filtering by question type.

- Added a subject and difficulty field to the alarms, consisting
  of term references
- filtered the question asked by subject and difficulty to match
  the subject and difficulty stated in the alarm.
Fixed install profile to include twilio library
feature: enabled the check_alarms module
added auto_nodetitle to the alarm feature

- featurized the variable that allows for automatic nodetitles for
  alarms
Added content editor role to alarms feature.
Added Auto-nodetitle settings to the flashcard feature

- used strongarm to featurize the ant variables
- added the content editor role to the feature
- added ant dependency
Fixed previous commit.

- removed reference to content editor role.
Fixed the flashcard feature

- fixed issue where feature was shown as overridden without
  actually showing what was overriden.
Added alarm settings feature, modified other features

- Added an alarm settings content type. It is basically a content
  type that allows us to easily set up a repeating alarm. The
  repeating date api was not ideal for this application since it
  requires an end date, where a repeating alarm goes on indefinitely

- modified the sent field in the alarm feature to be an actual boolean
  rather than a text field

- Added an entity reference to the alarm content type so that it can
  refer back to the alarm setting that created it. This is done to make
  adding/removing alarms from an alarm setting much easier.

- images/icons were added to taxonomies. This will make it much
  easier to create our custom form for creating alarms.
Added 'answered' and 'card sent' fields to alarms

- Added a boolean answered variable to the alarm content type. This
  variable must be set to 1 to mark that a question has been
  successfully answered.
- Added an entity reference 'card sent' that should contain a nid
  of the flashcard node that has been sent.
Added a module that reads recent incoming SMS messages and compares them to unanswered alarms
Created first version of create_alarms function

- wrote the create_alarms function, which will go through all existing
  alarm settings, and create the next week's worth of alarms. In the final
  version, this function should create the alarms for the week AFTER the
  current week, rather than the actual current week. Also handles the
  complexities involved with using differing timezones.
- Updated the features to match this new functionality. The entity reference
  joining the alarm settings and the alarms was moved into the alarm settings
  content type as opposed to the actual alarm.
Refactored alarm settings functions

- Moved this functionality into two different functions
    - check_alarms_node_presave implements hook_node_presave, and will check
      if a new alarm setting content has been created. If so, it will create
      all of the associated alarms for the next week.
    - update_alarms will, once a day, go through each alarm settings content,
      and add any alarms for 7 days from now.