Other than setting a Handling Fee in the box above the Table Rates in the screenshot you posted (I can’t see it in the screenshot though), there’s nothing in our plugin that would increase the price. So if it’s not that then it might be some other plugin adding something to the cost.
Good evening,
Thank you for your feedback.
I’ve just checked, I don’t have any other extension installed that could impact the shipping price.
Is there any way I can privately give you the login credentials to the dashboard so you can see inside?
Plugin Support
Gordan
(@gordano)
No, absolutely not! That’s strictly against the forum rules. Please do NOT send us any login credentials.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
GREAT ANSWER!
@alexisfontana74 Please don’t even consider doing that. It is not safe for you, it is not safe for the developer.
Had they asked for that, and they did not ask for that this would be the reply to them
—
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.
—
But again, they did not ask for that. Please work with them here instead and take care not to post any sensitive data.
Hello,
Thank you for your feedback.
I’ve finally found the source of the problem, I should have used dots instead of commas on the shipping costs.
Best regards,
