Hi
It looks like a payment method specific issue, as we dont see suh issue on our end. Send us your website link will try the checkout page. and also send full page screenshot of how you have configured the payment method fees
I didn’t see your response so I am sorry for the long delay. Right now I handle the store on the backend as I’m a repair shop so there isn’t a way for your to test on your side. I send them a bill and they pay so I would have to create an account for you and create a bill so you could see it.
I did see on the settings for the plugins page, when I go to select a option for payment method, I have like 20 WooPayments in my list and I am wondering if this is part of the problem, that there is some database or configuration issue. I’d upload an image but WordPress just seems to never want to add it to my post, just continues to spin like it’s trying to upload it.
I don’t know if you want to reach out to me directly or by another means so I can set this up for you would be great, just kinda annoying right now that it’s working fine sometimes then randomly adds in two lines for a $5 fee just by clicking between the two same options.
-
This reply was modified 9 months, 2 weeks ago by
KyleStilkey.
@rajeshsingh520 Your reply which was archived made it clear you are asking for login access to the user’s site. That is not permitted.
While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
- Ask the user to install the Health Check plugin and get the data that way.
- Ask for a link to the http://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
- Ask the user to create and post a link to their phpinfo(); output.
- Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
- Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site visitors).
- Ask the user for the step-by-step directions on how they can reproduce the problem.
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.