Forum Replies Created
May 16, 2020 at 1:05 pm in reply to: FPX error. When FPX is enabled, cannot use with Credit Card Payment #2945
FPX 1.0.1 has been released. Please update it via WP Dashboard and make a payment it test mode to see how it goes.May 16, 2020 at 12:55 pm in reply to: FPX error. When FPX is enabled, cannot use with Credit Card Payment #2944
Looks like FPX addon 1.0.1 was submitted for testing but haven’t been released.
Let me complete the testing and release it. You can then update it via WP Dashboard – Updates (like you would do with any other plugin).
Will let you know when done. Apologies for the inconveniences.May 16, 2020 at 12:49 pm in reply to: FPX error. When FPX is enabled, cannot use with Credit Card Payment #2942
Are you using latest versions of both Stripe Payments (2.0.29) and FPX addon (1.0.1)?
The issue you described was fixed 17 days ago in FPX addon. However, it requires newest version of core plugin as well.
We need to validate a phone number custom field
We need to validate character count on Client’s Name custom field
Just a heads up you cannot search your support forum. I tried to search for validate and nothing came up.
But to be frank, there were not much requests for custom fields validation, that’s why there is not much comes up when you search.
Hi and thank you for your report.
This seems to be either Stripe PHP SDK or CentOS\Curl issue.
I was unable to reproduce this on my test server (it’s not running CentOS though).
Anyway, I have just released a new testing version with additional settings option called
Disable Curl Persistent Connections. It can be found on WP Dashboard -> Stripe Payments, “Avanced Settings” tab.
When this option is enabled, it does the same thing that you code does – it instructs Stripe PHP SDK to disable persistent connections for Curl.
You can get latest testing version here: https://s-plugins.com/testing-version/
This is fixed in current stable version 2.0.28.
Please update it via standard WP means (WP Admin -> Dashboard -> Updates).
Cannot reproduce this. Tried from my Android phone (via Chrome browser) and there is no
Unauthorized Appmessage displayed.
Can you provide a screenshot? Or detailed steps to reproduce it?
This has been fixed in new testing version (2.0.28t2). https://s-plugins.com/testing-version/
Thank you for reporting this.
Just tried it myself and indeed, no coupon code is saved in Stripe metadata.
I’ve created an issue for this so the team could review and fix it.
The plugin adds metadata to Stripe when coupon is being used during a purchase. Product ID is also stored there. So you can export the data from Stripe (make sure the metadata is included when you configure export settings) and then analyze it as you prefer.
Please try current testing version of the plugin https://s-plugins.com/testing-version/
Situations similar to yours should be addressed in it.
I just “purchased” 360 days access via Google Pay without any issues.
When you make sure your product thumbnail is using https, the 90 days program will work fine as well 😉
Is there any way to export the data maintained by the plugin (e.g. orders, coupon, etc)? We would like to do some analysis of the data.
The plugin has no built-in data export functionality at the moment. But if you can describe your use-case scenario with a bit more details, perhaps we could find a way to either implement it in the plugin or to figure out some workaround.
You can also get the info from your Stripe account, it supports exporting of various data into CSV format. This is the reason why we don’t have our own data export since Stripe’s covers most of the needs.
and no credit card information will be kept by the site. Is that correct?
The plugin does not store any credit card info at all as this is PCI DSS compliance requirement. All the crucial info is processed and handled by Stripe on your behalf. Even the fields where your customers enter CC details are not controlled by the plugin, but the Stripe itself, so there is no way for the plugin (or its addons) to access those.
>I have changed the 90 day one to https. Still doesn’t work.
Can you try to edit your WP Settings and make sure your website address starts with https?
WP Dashboard -> Settings -> General,
WordPress Address (URL)and
Site Address (URL)options.
This should resolve all future random issues that could happen due to insecure contents on page (and not only with our plugin).