Issue with Grand Total

Hi @samuelspeed,
FYI, Pls kindly contact directly with our dev via https://wpclever.net/contact . Next, please include all screenshots, videos and additional information about your plugin settings as well as other WooCommerce plugins you are using if any. Be as specific as possible please because this could help us find the cause and solution faster. [redacted by moderator]
Best regards.

• This reply was modified 3 years, 8 months ago by Steven Stern (sterndata).

Hi @haithh93,

If I’m honest – I found your response to be lazy and very unhelpful.

In light of this, I did not expect to get very good customer service from your development team either, so instead of wasting time, I have managed to fix the issue by myself. For anyone else that comes across this issue the fix is VERY easy – And would have been even more so for one of the WP Clever Devs who could have just fixed the issue rather than sending me on a wild goose chase for answers!

So the issue relates directly to the ‘Change Price’ setting on the back end of this plugin.

By default, setting it to ‘Yes’ will either change most main themes price values dynamically when options are selected.

If set to ‘No’, the prices are static and do not change.

The issue was that I, like others on this forum, need the additions total to change – not the core product total. All you need to do to fix the issue is:

– Change the backend setting ‘Change price’ to ‘Yes, custom selector’.
– In the second text box that appears, input the code .woobt_total > .amount.
– That’s it. You have just changed the Java to update the woobt_total instead of the default value (or ‘Yes’ option) which is .summary > .price.

Please try and make this a default selectable option as part of your plugin.

• This reply was modified 3 years, 8 months ago by Samuel Speed.

@haithh93 I’ve deleted your offer to login to your user’s site. 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 https://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 vistors).
• 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.