Forum Replies Created
-
Posts
-
I have a similar need where I’d like to have a couple of conditions for a coupon and not just 1.
Is this something that is being considered?
Also, I know there is an option to turn on “coupon stacking”, but this just allows the same coupon to be used multiple times (even on page refresh). Is there any way to just allow multiple coupons (maybe a setting that could allow a user specified number of different coupons to be used)?
As an example, the user would create 3 coupons and could specify that a maximum of 2 coupons could be used on the checkout page.
Thanks.
I was manually unzipping and copying. That’s how I usually install plugins. I used the WordPress upload and install and everything worked fine.
Same problem.
Downloaded and extracted plugin that was emailed.
Deactivated old plugin, then deleted it.
Checked to make sure directory was gone.
Copied over to website.
Tried to activate and received the same error in the same file.
Looking at the file on my webserver, it looked like there were no line breaks, so the first comment (// Timestamp) on “line 10” actually commented out the rest of the code. The file on my computer didn’t look like this. Opened the file on my computer and then opened the file from the webserver. Manually copied code from file on my computer to file on webserver and resaved the file on webserver.
No other file had this problem.
Seems very odd.
I was sent a copy via email, so I used that copy. Deactivated then deleted old copy, then copied in new version from email and activated it.
That’s when I saw the error. Didn’t edit or change anything.
To fix it, I had to manually copy the proper code and resave the file.
Hey guys,
Sorry it’s taken me a while…got pulled off on some other items. Finished my initial testing and new code looks good except for the above problem. Thanks again for the great update!
Just deactivated my old version, deleted it, added the new one and upon activation I receive this error:
Parse error: syntax error, unexpected end of file in /home/realsol5/public_html/wp-content/plugins/wp-payment-gateway/wp_pg_debug_handler.php on line 1
Really not sure what the problem was here. When I looked at the file, it looked like there were no line breaks, so the first comment (// Timestamp) on “line 10” actually commented out the rest of the code. I deleted just that file and transferred it manually several times and nothing worked.
Finally, I manually copied the proper code and resaved the file. It activate ok. Now on to testing the new feature.
Ok, thanks. Went in my spam folder, so I just found it. Will start testing later today. Can you tell me where the ID is being saved?
Checking to see if there are any updates to the ID being saved (and where it is being saved). Thanks.
Ok, thanks. Please, let me know where you are storing it and when that’s done so I can grab a new copy of the plugin and use it if needed.
It looks like things are working well. The only caveat is that it appears to create a new customer for every charge.
This may be beyond what you’re interested in doing, but I’ll throw it out there for you to decide….but to take full advantage of the customer object in Stripe…
With Stripe, since you are now creating a customer object, you can charge the same customer object by simply storing the customer ID that Stripe assigns when you created the customer, then using that same customer ID for future charges instead of creating a new customer every time.
Now, from your end I realize this really doesn’t make sense from just the eStore perspective, because you’d never know what customer ID to use, BUT, if the person was using eMember along with eStore (as I am), then you would simply associate the customer ID with the eMember ID and use it when creating a new charge.
This is basically the same as showing a customers order history when they are using both eStore and eMember.
The real benefit here is that on Stripe, instead of having a new customer created for each and every charge a customer makes, there would just be one customer with all their charges.
Of course, this would be null and void if the customer isn’t logged in with eMember when they make their purchases (just like you can’t show them their purchase history if they’re not logged in when they make a purchase).
This would be a fantastic integration of eStore, eMember and Stripe.
So, I realize this is a long description and may be more than you’re interested in doing, but I thought I’d lay it out anyways.
Thanks again for updating the Stripe functionality to this point, it is greatly appreciated and will at least allow us to charge customers who call and want to “re-purchase” something over the phone (actually, we’ll also be able to use it as a “manual subscription” style purchase…what we call autoship purchases, where you buy a product (add to cart style)and want to receive it every 10 weeks.)
