[alexanderfoxc]

I apologize for a bit premature reply. I was able to reproduce the issue and already made necessary fix.

Please update Subscriptions addon to latest version (2.0.5) and get Stripe Payments latest testing version (2.0.17t2) here https://s-plugins.com/testing-version/

Try to make payment in test mode and let me know if the issue is resolved.

[alexanderfoxc]

If you know WP programming, you can get custom fields by hooking into following action:

asp_stripe_payment_completed

Here’s a quick example:

function get_custom_fields_data($data, $charge) {
if (isset($data['custom_fields']) {
// we got custom fields
$custom_fields=$data['custom_fields'];
} else {
// no custom fields
}
}

add_action('asp_stripe_payment_completed','get_custom_fields_data',10,2);

You’ll get custom fields in $custom_fields PHP array. You can then convert it to JSON or do whatever you like with it.

[alexanderfoxc]

Hi.

Are you using latest versions of both Stripe Payments (2.0.16) and Subscriptions addon (2.0.4)? Similar issues were reported in the past, however those should be fixed in current versions.

[alexanderfoxc]

Hi JX.

I have read through on Stripe API documentation to find this functionality, but unfortunately, Stripe API doesn’t offer anything close to it.

You can use following “workaround”:

1. Create “$1 trial” one-off product and let your customers pay for it.

2. After “trial” time is over, offer them to subscribe to your regular subscription.

This could be achieved via some marketing platform like MailChimp. E.g. when your customer pays for “$1 trial” product, you can add them to a sequence which would automatically follow up after set period.

I have created a ticket in our inner system with this feature request though. We will discuss with the team to see if some functionality to handle this situation could be implemented.

[alexanderfoxc]

Hi and thank you for reporting.

Looks like regression in zero-cents currencies handling (like JPY).

This should be fixed in new Stripe Payments version 2.0.15 (you can download it from here before it’s released: https://s-plugins.com/testing-version/ ) and in Subscriptions addon version 2.0.3 (check for plugin updates on your WP Dashboard).

Let me know if this helped.

[alexanderfoxc]

The URL for update checks was https://s-plugins.com:8080/

However, we have replaced it with the one without port number. I didn’t know outgoing connections to some ports could be blocked. I can understand if a server is blocking INCOMING connections, but why outgoing?…

Anyway, a new stable version (2.0.15) will be released soon (within 24 hours from now) and it should have this issue resolved. Thank you for reporting and helping to investigate this.

Also now you know that Siteground blocks all ports but those it has white-listed.

[alexanderfoxc]

Can you please install latest testing version (2.0.15t1) and see if it resolves your issue? I’ve removed port number from update checking URL (which might cause the issues if your server prohibits outgoing connections to non-standard ports).

[alexanderfoxc]

I can see update requests coming from your website and seem to be processed fine. At least Secure Downloads addon requested update today at approx. 10 AM UTC.

It might be the case when your server cannot access update server for some reason. But this should be definitely recorded in PHP error logs. Strange thing it’s not there.

Anyway, I will try to add reasonable timeout for updates checking. If error occurs during the process, it won’t stall WP admin area at least.

[alexanderfoxc]

It might be ./wp-admin/php_errorlog or ./php_errorlog, but it’s just a guess. Usually there should be just one error log file.

Try to enable the addons, then wait for gateway timeout and see which of the error log files has the newest date. It should have the latest error messages.

[alexanderfoxc]

Hi.

I assume you’re using latest versions of core plugin and addons?

Do you have access to PHP error logs on your server (those usually could be viewed via your hosting control panel)? There should be some error messages that could share some light on your issue.

[alexanderfoxc]

Thank you for reporting.

Subscriptions addon version 2.0.2 (that has the fix implemented) would be released shortly.

For existing products, you can edit names directly from Stripe Dashboard. Just replace the entity with hyphen where needed.

[alexanderfoxc]

Can you please send the URL with your payment button via contact form? https://s-plugins.com/contact-us/

[alexanderfoxc]

Is the addon enabled in the settings?

Also try to re-approve domain with Apple just in case (by clicking the button from the addon settings).

[alexanderfoxc]

Hi.

Update core plugin and APM addon to latest versions (there were some bugs fixed related to Apple Pay).

In new API, Apple Pay button appears in payment popup. When you click payment button that shows popup, Apple Pay would be selected as default payment option (if it’s supported by device). If it’s not – it won’t be displayed at all.

[alexanderfoxc]

For that, you need to construct your own thank you page using this guide https://s-plugins.com/customize-the-thank-page-message-of-stripe-payments-plugin/#customize-thankyou-page

I just checked and {custom_field_N} tag works just fine on custom thank you page.

Let us know if there are any issues with that.

[Author]

Posts