Question on ccaps

#1

Hi Everyone,

Just in the last year or so I have been having issues with customers that order large numbers of ccaps. When they add them all to there account either something on my end fails or something on PayPal fails. For example an order of 60 ccaps at once will most likely fail to load them all. It seems to fail around the same number too. ccap_01 - ccap_60 for example will likely get 01,02,03,04,05,06,07,08,09,10,11,12,13,14,15,16,17 and then fail to load the rest 18-60. I use 6 digit ccap codes, not 2 like the example.

In PayPal I also see where the email they send stops at the same number that leaves off on the account. Is there a limit to the number of ccaps that can be ordered at once?

It is now in my daily habit to go through all orders within a few hours of purchase to be sure that they got what they purchased and to correct the failed ccaps.

If there is a limit, is there a way I can apply another ccap to the s2member folders access-s2member-ccap-. to have multi values?

If I could bunch the ccaps together at the time of purchase without adding all the files again in new folders it would be a help. Maybe 01-12 breaks down to ccap-ALL2017 meaning anyone that owns ccap_ALL2017 would get all the included ccaps for that year still allowing for separate ccaps to still work. Is there such a way to have either or on the ccaps like can be accessed by either 012017 or ALL2017.

All the protected folders of ours files equals at about 50 GBs and we are only in our 4th year, I would like to not have to double our usage at this point just to all combining of the ccaps.

For the longest time this was working perfectly fine with orders up to 72 ccaps but then maybe 8 months ago or so it started doing this, at first hit and miss but now it does it 100% of the time and it is typically after the 17 ccap is added to the account. All my ccaps are in the date format of XXXXXX and breaks down to 012017 meaning they have access to all files in the month and year of January 2017.

For another note: there are 102 characters plus 16 commas making it 118 before it fails. 203 if you count the ccap_ along with the month and year codes along with the commas.

Thanks for any insights to this issue I am having.

Ross

#2

There is limitations of about 120-160 chars (can’t remember the exactly number) for “your domain”+“ccaps”, Paypal set this and no way to “jump over”… I would create a mechanism to “compress” all the ccpas in a single one, by the DB, not like you explain, this way will fix the transaction, but this is not easy way…

#3

Thanks Krum,

I will have to hire that out then cause I understand the concept but have not a clue on how I would to get xyz123 to translate into something else at the db.

Thanks for the leads on fixing this.

Ross

#4

Easer variant I find:

  1. Collect (assemble) a string (or array) with all need ccaps for “this” user, before the payment.
  2. Save it as usermeta.
  3. Create another (maybe unique) short string, that will remind the script that this user have a complex ccaps in the metas, maybe tie it to the mets ID.
  4. Pass the string from p. 3 as user’s ccap in payment form/button. That’s only 1 ccap, can’t be a problems.
  5. Create a script, that will get/find that ccap, then will find the need usermeta by it. Extract need ccaps.
  6. Remove this (temporary) ccap from the user, and add the need ccaps
  7. Create need “payment notifications” that will run the script you create at p. 5

Well, that’s a fast description, maybe I miss something (and ton of details…), but hope you will understand the idea: the “real ccaps” are replaced with a temporary one, and after payment passes temporary one is replaced by real ones.