If site has over 60,xxx users, Subscriptions break

D'oh! I didn't ever notice that. I guess I have proven the limit, then. All the subscribers are not being allowed to subscribe, because the IPNs aren't matching their UID's. Is there any possible way I can get this fixed? Right now, I have to keep checking for errors, and manually editing users who are subscribing. It's quite a pain...

If you could even just point me in the right direction, that'd be great. I think we'd be willing to offer a bounty, if it comes to that.

So if I upgrade to 2.0 alpha 1, this problem should disappear? Or should I grab the -dev release. I'd like to roll this out live a.s.a.p., as I'm manually adding the 'subscriber' roll to anyone who subscribes right now.

@ lyricnz - ah well. Might you be interested in a bounty to fix this issue, or to complete more dev on the updated version? I think I might be able to get a small budget for that :-)

Just updating the title to make it more sensible.

It would seem that there's a problem with the "custom" IPN field being matched from the lm_paypal_subscriptions table to the "custom" field in the ipn table.

I noticed this code tacked onto the end of the core lm_paypal.module:

/**
 * Extract data from the 'custom' field in an IPN.  The old way LM Paypal did it
 * was by bit-packing into a 32-bit integer. The new way is PHP serialized data.
 *
 * @return array
 *   An associative array with at least 'uid' and 'other'
 */
function lm_paypal_unpack_ipn_custom($ipn) {
  if ($ipn) {
    if (is_int($ipn->custom)) {
      // Old bit-packing format for 'custom'. The uid is in the bottom of 'custom'
      return array('uid' => $ipn->custom & 0xFFFF, 'other' => ($ipn->custom >> 16) & 0xFFFF);
    }
    else {
      // New serialized data
      return @unserialize($ipn->custom); // In case the passed string is not unserializeable, FALSE is returned and E_NOTICE is issued.
    }
  }
  else {
    // Not set
    return array();
  }
}

And I'm guessing you're still working on this IPN system - it's passing through the completed payments properly, but the subscriptions are never being set up after the IPN is received and validated. (My IPN table has 8 records in it, all with the proper uid values and "custom" field information, but nothing's being added to the subscriptions table).

I might go back to 1.x until this is fixed; I am definitely willing to help!