Forum Replies Created
-
AuthorPosts
-
alexanderfoxcParticipant
Hi Josh.
1. change the label to say “Name as appears on Card”
You can change any message in the plugin by “translating” it to English.
1. Install Loco Translate plugin https://wordpress.org/plugins/loco-translate/
2. Go to Loco Translate – Plugins, look for Stripe Payments and click it.
3. Click “New Language” and select the one that is set as default for your website. Let’s assume it is English (United States). Also make sure to select “Custom” location, otherwise your changes will be overwritten by plugin or WP update.
4. Now you can “translate” the messages you want. Look for “Name”, which should be marked as “Customer name” and change it to whatever you like.
You can change ANY text in ANY plugin like that.
Note: it will only work with current testing version of the Stripe Payments plugin. It has some code added necessary for this. You can get testing version here: https://s-plugins.com/testing-version/
2. add a hint text to the box that says the same thing.
This can’t be done unfortunately, as the field does not have a hint. There is a default browser hint for required fields.
June 13, 2020 at 12:29 pm in reply to: Price of product different than what is actually charged. #2996alexanderfoxcParticipantLooks like it was precision inconsistency between frontend and backend calculations. JavaScript is trying to represent 19.99 with as much precision as possible. Since computers don’t have infinite precision, it picks the number that is closest: represents 19.99 as 19.98999999999999. So after the value is processed on backend, multiplied by 100 (Stripe API requires amount to be passed in cents) and gets fractional part removed, it becomes 1998.
This will be fixed in the upcoming version of the Subscriptions addon. Note you might have to re-create your plans if they still show improper amount.
Thank you for reporting this.
June 13, 2020 at 12:11 pm in reply to: Price of product different than what is actually charged. #2995alexanderfoxcParticipantHmm, I was able to reproduce the issue.
I will investigate this further and get back to you.
alexanderfoxcParticipantThis is most likely your site\server glitch as I couldn’t reproduce the issue on my test server. Tried WP update from 5.4.1, from older versions, also tried fresh install.
Glad you have it resolved though.
alexanderfoxcParticipantHi, Which page of the plugin are you referring to?
alexanderfoxcParticipantHi.
Try to edit your product and see if newly added custom fields are enabled for it (Custom Field meta-box).
alexanderfoxcParticipantMailerLite API doesn’t seem to allow adding users to specific segments or campaigns. It also doesn’t look how it supposed to work anyway.
So if you have a segment for each product, you should also create a group for each product. Then you can configure each segment to only have users from a specific group.
Example:
You have Product 1 and Product 2.
You have Segment 1 (for Product 1) and Segment 2 (for Product 2).
You need to create two groups in your MailerLite account – Product 1 and Product 2.
Then set corresponding group for corresponding product on your site.
Then configure each of your segment for corresponding group. E.g. Segment 1 should use users from group Product 1.This way it should work how you want.
alexanderfoxcParticipantHi.
If this can’t be configured from within MailerLite dashboard itself, we can add the option to add a label for specific product.
I will investigate this and get back to you shortly.
alexanderfoxcParticipantNo problem 🙂 Don’t hesitate to post if you’re facing any issues.
alexanderfoxcParticipantHi Tosha.
There should be no plugin-specific issues with SMTP as the plugin is using default wp_mail() function to send emails. So the issue is probably related to your SMTP config.
I’ve also updated the from name/email in Stripe plugin to match what I set in SMTP plugin.
I think this is the right direction to look at. From email should be set to the one that is configured\allowed on your SMTP server. For example, if you’re using your server’s SMTP, then the from email should be [email protected], otherwise the email might not be sent.
alexanderfoxcParticipantHi.
When you were creating Dropbox APP, have you provided Full Access to it like on this screenshot?
https://s-plugins.com/wp-content/uploads/2018/07/creating-app-in-drop-box-for-stripe-payments.jpg
If not, you can only choose files inside the app folder (Dropbox->Apps->{your_app_name}), not the whole Dropbox.
alexanderfoxcParticipantHi Jennifer.
We need to validate a phone number custom field
We need to validate character count on Client’s Name custom fieldIf you’re ok with JavaScript RegExp, we can add its support for ACF addon. If you’re not very good at JavaScript RegExp (I’m not much of an expert here either), I can try to assist you in composing the rules, provided you can explain the rules of validation for your Customer Name and Phone Number fields.
Just a heads up you cannot search your support forum. I tried to search for validate and nothing came up.
https://s-plugins.com/forums/search/validation/
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.
alexanderfoxcParticipantHi 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/
alexanderfoxcParticipantThis is fixed in current stable version 2.0.28.
Please update it via standard WP means (WP Admin -> Dashboard -> Updates).
alexanderfoxcParticipantFound this in Stripe docs:
Note that when using Google Pay, including Android Pay, with a test mode key, you might see an “Unrecognized app” warning. This is expected, and does not show up in live mode.
-
AuthorPosts