Make sure an order is only synced once about spree_chimpy

[braidn]

Bryan,

That’s the plan! The old sync ability doesn’t even work with the new API so this will change.
-- 

On July 3, 2014 at 3:39:14 PM, Bryan Mahoney ([email protected]) wrote:

Removing an order only removes it (seemingly) from the campaign stats, but not the total order count. As such, calling remove and then add, as we do in the sync method, can cause inflated numbers in MailChimp.

[bryanmtl]

👍

[braidn]

Bryan,

This is my first whirl. Since there is no way to "sync" an order we need to rely on these two methods (add/delete). This alleviates our blanket use of delete but, will it still cause inflated numbers?

      def sync(order)
        add(order)
      rescue Mailchimp::InvalidEcommOrderError
        remove(order)
        add(order)

[bryanmtl]

@braidn - That is worth a try. Is sync only called once though?

[braidn]

It will be called when an order is updated or created.

On Jul 4, 2014, at 7:35, Bryan Mahoney [email protected] wrote:

@braidn - That is worth a try. Is sync only called once though?

—
Reply to this email directly or view it on GitHub.

[bryanmtl]

I think our best bet is to just call it when it transitions to complete.

[braidn]

Sounds good

On Jul 4, 2014, at 7:43, Bryan Mahoney [email protected] wrote:

I think our best bet is to just call it when it transitions to complete.

—
Reply to this email directly or view it on GitHub.