Hi all,
@greggb : your extension already saved me about $6 yesterday
More than the money itself, it's the beauty of the automation I liked. I had all these codes lying around but was tired of trying them manually each time I had a new registration to make. I used a "tab opener" which I fed "cart urls" with each coupon hardcoded in, but that still required lot of manual work. YOU SAVED THE DAY !
Here is what I can give back: an
updated (deduplicated) list of coupons that contains your original list of 350 plus 171 I gathered on this forum and elsewhere.
It is already formated right, so for those of you who can't wait the update, just open the "background.js" file in the GD Coupon Checker file and copy paste the update list in lieu of the old one you will fine at the bottom of the file.
I won't upload the updated "background.js" file myself since that is not my code and I don't feel entitled to do so...
===
Here is how I plan to use the extension and maintain the coupon list
===
As far as I understand, there are several situation possible with coupons.
- The same coupon can be used more than once (with a wait period of ?? days).
- Some codes are country specific (I operate in France and sometimes a coupon that seems to work for everybody else does not work, though it's the first time I try it)
- Some codes are returned as "Invalid" by GoDaddy, so I guess these won't ever work for the person using them (maybe because of geo ?)
- Some codes seem to work up to payment time, where a "invalid card" red flag appears and stops the checkout.
Anyway : I intend to run the extension one or two times a month, just to check if the status of a given code has changed from "not-working" to "working".
===
Suggestions of modifications
===
1) I think the codes list should be in a separate txt file.
That would allow us to
- Update codes without ever touching the script.
- Replace the list with another list easily (If I have a new list of 30 codes to try, I just backup the old 500+ list and use the new list instead. I can always merge those 30 new into the old list to get my updated list for the monthly validity check)
2) Format of output would be easier to use (for me at least) if in csv format
I would use "coupon name, price, status" and leave the invalid ones in the list (issued with a "n/a" price).
With time that would help to build some prioritization in the coupons to test manually after the automated part.
Sorry for the long rap, but I feel very enthusiastic
Thanks again Greggb.