[alexanderfoxc]

New version of Subscriptions add-on has been released. It has proper webhooks-related error handling now, so there should be no PHP errors for this. Errors will be logged into Stripe Payments debug log (if enabled).

[alexanderfoxc]

Hi.

Coupons are not added to links, but rather to product itself.

Perhaps you mean to add coupon field to a product generated by a shortcode? Please clarify.

[alexanderfoxc]

five times in the list of webhooks in the Stripe dashboard, with four of these actually tracking activity. Does that make sense?

Yep, this is definitely is the cause of PHP errors. Also looks like Stripe changed error handling in their SDK, this will be addressed in the upcoming version of Subscriptions add-on.

Anyway, you need to delete all plugin webhooks manually from your Stripe Dashboard that look like https://(domain)/?asp_hook=XXX (both Live and Test). Then create those from Subscriptions tab of Stripe Payments settings, let the signing secrets stay there as well. Then check your Stripe Dashboard to ensure only one of those created for both Live and Test modes.

Let me know if PHP errors are gone after that.

[alexanderfoxc]

Ok, try to delete both Live Webhook Signing Secret and Test Webhook Signing Secret from Subscriptions add-on settings (just leave those fields blank) and then click “Save Changes” button. This would tell the add-on to not try to check webhook validity using signing secret.

Let me know if this helps with PHP errors. Then we will see what can be done to make it work with signing secrets as well.

[alexanderfoxc]

Thank you, this is helpful.

Looks like your webhook signing secrets are invalid.

In order to fix that:

1. Go to Stripe Payments -> Settings, Subscriptions tab.

2. Click “Delete Webhooks” button.

3. Click “Create Webhook” buttons for Live and Test webhooks.

4. Click “Save Changes” button at the bottom of the page.

Let me know if this helped.

[alexanderfoxc]

Hi.

How do you tell people in your delivery area from others? Is it based on address or postal code etc.?

[alexanderfoxc]

Hi.

Check your live webhook on your Stripe Dashboard here https://dashboard.stripe.com/webhooks. Let me know if it’s there even when error message from Subscriptions add-on is displayed.

[alexanderfoxc]

Additionally, can you create a test mode product so we could try to make a test payment and see what might be wrong on the frontend during the process? You can force test mode on product’s edit page (“Force Test Mode” option).

[alexanderfoxc]

Regarding #4, I figured it is W3 Total Cache plugin. We have added support for it in the upcoming Stripe Payments version 2.0.36, it should be released sometime next week. Make sure to update it when it prompts. It automatically clears W3TC plugin caches when you make changes to products or plugin settings. You still need to clear its cache when you update any plugin though.

[alexanderfoxc]

Thank you.

1. I can see you have updated FPX add-on to latest version, this is good. It should fix the issue with “Error occurred: URL: Code 0” on your site. Thank you for reporting it.

2. I can see you’re using some caching plugin. Generally, it’s not a good idea to cache payment popup URLs. If your caching plugin allows you to add exclusions, please add ?asp_action=* to the exclusions list. It should not cache, minify and combine payment popup page\scripts, otherwise your customers may experience issues with payment popup.

3. Can you let me know which caching plugin you are using? We will try to add compatibility with it if possible, by telling it to not cache payment popup URLs internally.

4. Last, but not least – every time you make changes to plugin settings or products, or updating plugins, always clear all caches of your caching plugin. Expired cache can cause various issues at random, and not only with our plugin. To check if everything is working properly, access your site via Incognito (Private) browser mode as non-logged-in user.

[alexanderfoxc]

Hi.

We don’t have LMS integration currently. However, I think LMS offers some kind of API that can be used after successful payment to register a new user.

[alexanderfoxc]

Can you disable all countries blocking for now? We have people from different countries in our team, plus country detection isn’t always accurate.

[alexanderfoxc]

Hi.

Not yet, but this is currently being worked on.

[alexanderfoxc]

Hi.

Clear your caching plugin cache and it should be gone.

[alexanderfoxc]

Thank you.

Looks like caching plugin might cause the issue. Try to clear all caching plugins cache\combine\minify etc. If this won’t help, try to temporary disable those and see if MultiCurrency works.

Let me know the results and we’ll try to figure out how this can be fixed.

[Author]

Posts