Anonymous subscription not assigned to correct user

Oh, interesting ... thinking there's some kinda caching issue here where one subscriber doesn't know what a previous subscriber has done to the order? Not just a matter of priority, is it?

I don't know that I am confident in that assertion -- been a while since I had my head in this code. Certainly it would be nice if this fix weren't necessary -- it's a little clunky.

We should pass "initial_order" and not "order" to match the field name, will go ahead and commit the attached patch. I think the change makes more sense, always better to do this rather than expecting the reference to be up to date.

Automatically closed - issue fixed for 2 weeks with no activity.