CORE POS - Fannie
The CORE POS back end
Public Member Functions | List of all members
MailChimpTask Class Reference
Inheritance diagram for MailChimpTask:
FannieTask

Public Member Functions

 run ()
 
- Public Member Functions inherited from FannieTask
 setThreshold ($t)
 
 setConfig (FannieConfig $fc)
 
 setLogger (FannieLogger $fl)
 
 setOptions ($o)
 
 setArguments ($a)
 
 run ()
 
 cronMsg ($str, $severity=6)
 
 lazyGetOpt ($argv)
 

Additional Inherited Members

- Public Attributes inherited from FannieTask
 $name = 'Fannie Task'
 
 $description = 'Information about the task'
 
 $default_schedule
 
 $schedulable = true
 
const TASK_NO_ERROR = 0
 
const TASK_TRIVIAL_ERROR = 1
 
const TASK_SMALL_ERROR = 2
 
const TASK_MEDIUM_ERROR = 3
 
const TASK_LARGE_ERROR = 4
 
const TASK_WORST_ERROR = 5
 
- Protected Attributes inherited from FannieTask
 $error_threshold = 99
 
 $config = null
 
 $logger = null
 
 $options = array()
 
 $arguments = array()
 

Member Function Documentation

MailChimpTask::run ( )

Examine all list members

Print progress meter in verbose mode

MailChimp has a POS member number tag

If subscribed list member has been tagged with a POS member number, compare MailChimp fields to POS fields. If name disagrees, use POS value for both. If email disagrees, use MailChimp value for both.

Just track the number to avoid re-adding them to the list

Cleaned in MailChimp means the address isn't deliverable In this situation, remove the bad address from POS and delete the address from MailChimp. The member can be re-added when a correct email is entered into POS.

If list member is not tagged with a POS member number, try to locate them in POS by name and/or email address. If found, tag them in MailChimp with the POS member number. This whole situation only occurs if the initial list is imported without member numbers.

Unsubscribed are currently ignored. The can't be updated as is. They could be deleted entirely via unsubscribe, resubscribed with an owner number, and then unsubscribed again. That's not currently implemented. It does check for the email address on the POS side to prevent re-adding it.

Cleaned are bad addresses. Delete them from POS database then from Mail Chimp.

Removed bounced from the MailChimp list now that POS has been updated

Finally, find new members and add them to MailChimp


The documentation for this class was generated from the following file: