Forum Replies Created

Viewing 15 replies - 1 through 15 (of 1,043 total)
  • Hi @k_shah_in ,

    Thanks so much for getting in touch!

    I’m really sorry to hear that Google is showing a ₹2,000 delivery charge for your products, especially when your site offers free shipping. That’s understandably confusing, and I’d love to help you sort it out.

    What’s likely happening here is a mismatch between your actual shipping setup and what Google is able to read. Google doesn’t always support more advanced or dynamic shipping rules — like those based on coupons or conditions like Cash on Delivery. If your shipping is determined this way, Google might not detect it correctly and ends up assigning a default or incorrect amount instead.

    To rule out any plugin conflicts — especially those related to discounts or payment methods — could you try temporarily deactivating all plugins except for WooCommerce? If possible, it’s safest to do this on a staging site. You can spin one up easily using this free plugin: https://ww.wp.xz.cn/plugins/wp-staging/

    We also have a helpful guide here for doing a full conflict test: https://woocommerce.com/document/how-to-test-for-conflicts/

    If the issue still shows up after that, it’d be super helpful if you could share your System Status Report from the staging site. Here’s how to grab it:

    1. Go to WooCommerce > Status in your dashboard
    2. Click Get system report and then Copy for support

    If there are any fatal error logs showing up, please send those over too. You can find them under WooCommerce > Status > Logs.

    Once you’ve gathered that info, feel free to paste it into a code block here or upload it to pastebin.com and send us the link. That’ll help us dig deeper and get you a clearer answer.

    Looking forward to your reply!

    Hi there,

    Thanks so much for reaching out, and I’m really sorry to hear about the issue you’re running into with the woocommerce_refresh_order_count_cache action firing every second—that definitely doesn’t sound ideal.

    It looks like there are a couple of recent discussions around this on GitHub that might be related:
    👉 Pull Request #58586
    👉 Pull Request #58535

    From what I can tell, this behavior may have started with version 9.9.2. Just to help us narrow things down, could you let me know which version of WooCommerce you’re currently running?

    Also, have you had a chance to test with only WooCommerce active and all other plugins temporarily disabled? That step can help rule out if another plugin is triggering the hook unexpectedly.

    It would also be super helpful if you could share your System Status Report. To grab that:

    1. Head to WooCommerce > Status in your dashboard.
    2. Click Get system report and then Copy for support.

    If there are any fatal error logs showing up, please send those over too. You can find them under WooCommerce > Status > Logs.

    Once you’ve gathered that info, feel free to paste it into a code block here or upload it to pastebin.com and send us the link. That’ll help us dig deeper and get you a clearer answer.

    Looking forward to your reply!

    Hi @conrad-gz ,

    Thanks so much for reaching out! I’m really sorry to hear about the issue with the related products section trembling when you hover over it—definitely not what you’d expect, and I can see how that would be distracting.

    To get a better idea of what’s happening, would you mind sharing a screenshot or a short screen recording? If you don’t have a tool handy, Loom.com is great for quick videos, or Snipboard.io works well for sharing screenshots.

    I took a look at your product page and noticed the “View Cart” button is showing up just below the “Add to Cart” button. Normally, that message should pop up as a notice at the top of the page. Is that something you’re concerned about too, or is your main focus the related products section shaking? Just want to make sure we’re zeroing in on the right part.

    It looks like you’re using the Divi Builder to design the page. If the cart notice placement is what’s bothering you, you might need to adjust the WooCommerce notice module in Divi’s settings. But if the trembling effect on the related products is still showing, that might be something tied to the theme itself—Divi’s support team would be a good place to check in with for that kind of issue.

    Let me know what you find!

    Hi @chumidor ,

    Thanks for the update!

    Just checking — were you able to track down which plugin might be causing that notice?

    I added this to the function php snippets area but it did nothing to stop the logging of it

    If that doesn’t do the trick, you can try using a Must-Use (MU) plugin. These load before regular plugins, so they’re great for things like suppressing deprecated notices early in the process.

    Here’s how you can set it up:

    1. Create a folder called mu-plugins inside your wp-content directory (if it doesn’t already exist).
    2. Inside that folder, create a file named disable-deprecations.php.
    3. Add the following code to that file:
    <?php
    // Run early to suppress PHP deprecated notices, including WooCommerce's
    error_reporting(E_ALL & ~E_DEPRECATED & ~E_USER_DEPRECATED);
    add_filter('deprecated_constructor_trigger_error', '__return_false');
    add_filter('deprecated_function_trigger_error', '__return_false');
    add_filter('deprecated_file_trigger_error', '__return_false');
    add_filter('deprecated_argument_trigger_error', '__return_false');
    add_filter('deprecated_hook_trigger_error', '__return_false');

    Once that’s in place, it should help suppress those notices.

    Give it a try and let us know how it goes!

    Hi @atlantis1525 ,

    Thanks for reaching out to us about this.

    I’m sorry to hear the database isn’t updating properly, even after switching to Storefront and deactivating all other plugins. That can definitely be frustrating when you’re trying to keep everything up to date.

    Starting in WooCommerce 9.9.x, database updates happen automatically in the background — you can see more on that here: WooCommerce GitHub – Background DB Updates.

    To make sure the update process is actually running, would you mind checking for any pending or failed actions related to woocommerce_run_update_callback? You can do that by heading over to WooCommerce → Status → Scheduled Actions, and filtering by “Pending” or “Failed.” If you see any actions with that name, try clicking Run (or Run Now) next to them to trigger the update manually.

    Let us know what you find — we’ll be happy to help you take it from there.

    Hi @jmabbas ,

    Thanks for reaching out — and I’m sorry to hear that the review option isn’t updating as expected in the Gutenberg editor.

    Since this setup involves custom code, it’s a bit outside what we’re able to support directly. Custom modifications like this fall outside our support policy, but you might consider reaching out to a trusted developer through Codeable or one of our Certified WooExperts who can help get everything working just the way you need.

    That said, if you’re open to trying something new, we do have a beta version of our new product editor that might be worth exploring. You can enable it by heading to: WooCommerce > Settings > Advanced > Features, then toggle on “Try new product editor (Beta)”.

    Here’s more info if you’re curious: https://woocommerce.com/document/new-product-editor-beta/

    I hope this helps point you in the right direction!

    Hi @websitende ,

    Thanks so much for reaching out! I totally get how important it is to make it easy for your customers to leave reviews—especially when you’ve already set things up to allow guest reviews.

    That said, the login requirement is actually controlled by a WordPress core setting, not WooCommerce. Here’s how you can fix it:

    Head to Settings > Discussion in your WordPress dashboard. Look for the option that says “Users must be registered and logged in to comment” and make sure it’s unchecked. Then click Save Changes.

    After that, be sure to clear your site cache—or try viewing the page in an incognito/private window—to make sure the update takes effect right away.

    Give that a try, and let us know how it goes.

    Hi @egdotcom ,

    That’s awesome to hear — I’m so glad the CSS worked out for you!

    However, If you have a moment, we’d truly appreciate it if you could share your experience with our support by leaving a review: https://ww.wp.xz.cn/support/plugin/woocommerce/reviews. Your feedback goes a long way in helping us improve!

    Please don’t hesitate to create a new topic if you need further assistance.

    Cheers!

    Hi @aroeditor ,

    Thanks so much for reaching out, and I appreciate you sharing the screenshot — it looks like you’re working on a pretty sleek layout with the product container on the left and the sidebar on the right. That setup’s looking great so far!

    From what I can see, it sounds like you’re aiming to box in just the product container — keeping the content centered with some nice spacing on the sides. That kind of layout tweak usually does require a bit of custom CSS, especially if you’re working outside of a full-width template.

    then how do I adjust the product container to only be boxed? Or other options? 

    Since your site isn’t live yet, I can’t pinpoint the exact CSS class for you. But in general, you’d want to adjust the width and padding of the product container and possibly tweak the layout wrapper around it to get that “boxed” feel.

    That said, just a quick heads-up: our support covers the core WooCommerce plugin, so we’re limited when it comes to helping with custom code or layout changes tied to themes or third-party plugins.

    If you’re looking to take the design further, I’d definitely recommend reaching out to Codeable or a WooExpert, who can help craft something pixel-perfect for your site.

    I hope this helps point you in the right direction

    Hi @xoyozo ,

    Thanks for reaching out!

     If I have a standard WordPress instance and additionally installed the plugin WooCommerce (no further plugins or custom code snippets), is the role “Shop manager” able to edit users by default (Users -> All Users -> Edit)?

    By default, the Shop Manager role in WooCommerce doesn’t have permission to edit other users in WordPress — they won’t be able to go to Users → All Users or edit profiles like an Administrator can. The Shop Manager role is mostly focused on managing store-related tasks like orders, products, and reports, but not broader site management like user roles.

    If you’d like a Shop Manager to have access to user editing, you’ll need to manually grant that permission. One easy way to do that is by using a plugin like User Role Editor. It lets you adjust roles and capabilities right from your dashboard — no coding needed.

    Please note that our support is limited to the core WooCommerce plugin, and we’re unable to assist with modifications involving custom code or third-party plugins.

    For more advanced customizations, I’d recommend reaching out to Codeable or a Certified WooExpert, who can help tailor the solution to your site.

    I hope this helps!

    Hi @esther0708 ,

    Thanks for getting in touch, and I’m really sorry to hear you’re running into trouble with Cash on Delivery — I know how frustrating it can be when something doesn’t behave the way you expect at checkout.

    Just to confirm: it sounds like you’ve enabled the COD payment method, and you’ve unchecked the “Virtual” option for your product — but it’s still showing as available during checkout for that product. Is that right?

    If so, could you please share a link to the product that’s having the issue? That way, we can take a closer look and help pinpoint what’s going on.

    If the issue is a bit different from what I described, no worries at all — a short screen recording would be really helpful! You can use Loom to record your screen and send us the link.

    Looking forward to your reply, and we’ll do our best to get this sorted for you!

    Hi @chumidor ,

    Thanks so much for reaching out, and I totally get how those deprecation notices can feel a bit overwhelming in your logs.

    Just to share some quick context: the wc_current_theme_is_fse_theme() function is a WooCommerce wrapper that’s now deprecated as of version 9.9. Behind the scenes, it simply calls wp_is_block_theme(), but starting with this update, WooCommerce logs a deprecation notice anytime that older function is used.

    That’s likely why you’re seeing messages like this in your logs:

    PHP Deprecated: Function wc_current_theme_is_fse_theme() is deprecated since version 9.9.0! Replace with wp_is_block_theme().

    If you’re not sure where this is coming from, a good first step is to try temporarily deactivating your plugins one by one and check if the message disappears — that can help narrow down which plugin might still be using the deprecated function.

    You could also install the Query Monitor plugin, which is great for catching where specific notices or warnings are coming from.

    If you’d rather not dive into plugin testing right now, there’s also a quick way to suppress those deprecation messages so they don’t flood your logs. You can add this snippet either to your theme’s functions.php file, or use the Code Snippets plugin to add it safely:

    add_filter( 'deprecated_function_trigger_error', '__return_false' );

    Let us know how things go after giving that a try!

    Hi @noctura400 ,

    Thanks for reaching out, and I’m sorry to hear that some of your subscription orders are being auto-cancelled — I know how frustrating that can be.

    It looks like you’re using the SUMO Subscriptions plugin from CodeCanyon:
    https://codecanyon.net/item/sumo-subscriptions-woocommerce-subscription-system/

    Since that plugin manages the subscription functionality and payments, their team would be in the best position to assist with this issue. You can contact them directly for support here:
    https://fantasticplugins.com/support/

    If that’s not the plugin you’re using, no worries — we’d be happy to take a closer look. To assist you better, could you please provide a few details:

    Are you using the official WooCommerce Subscriptions extension alongside SUMO, or is SUMO handling all subscription management? When the orders auto-cancel, do you see any error messages or logs in WooCommerce > Status > Logs? Are there any specific triggers or patterns you’ve noticed related to the cancellations (e.g., payment failures, expired cards)?

    It would also be super helpful if you could share your System Status Report. Here’s how to get it:

    1. Go to WooCommerce > Status in your WordPress dashboard
    2. Click Get system report, then click Copy for support

    Also, if there are any error logs related to the SUMO plugin, you can find those under WooCommerce > Status > Logs — feel free to include anything that looks relevant.

    Once you’ve gathered that info, you can paste it here in a code block or upload it to pastebin.com and share the link with us.

    Looking forward to your reply, and I hope this helps point you in the right direction!

    Hi @digitalscheune ,

    Thanks for sharing your findings with us!

    I’ve tested the issue on my end using a similar setup with the latest WooCommerce version (9.9.4), and I wasn’t able to reproduce the problem https://prnt.sc/sYP8CjAdznRz. That suggests the issue might be specific to your site environment.

    Looking at your System Status Report, it doesn’t appear that any plugin or theme is directly overriding the order email template. That said, it’s still possible that your theme or another plugin is affecting the output in a less obvious way.

    Just to confirm—have you had a chance to run a conflict test yet? That involves deactivating all plugins except WooCommerce and switching to the default Storefront theme. This can help rule out whether a plugin or theme is causing the issue.

    If you’re not comfortable doing that on your live site, you can use the WP Staging plugin to create a safe testing environment.

    Let us know how it goes—we’re happy to keep digging with you from there!

    Hi @dominoevers ,

    Thanks for reaching out—and I’m really sorry to hear that your Danish templates are now showing a mix of English and Danish after the update. That’s understandably frustrating.

    Just to clarify, is the issue only happening in your email templates, or are you also seeing mixed languages on your live site pages?

    If you haven’t already, I’d recommend checking for any available translation updates by going to Dashboard → Updates, then clicking “Update Translations.”

    Also, it’s a good idea to compare your custom email template files (if you’re using any) with the latest default templates in: wp-content/plugins/woocommerce/templates/emails/ If the structure has changed in recent versions, you might need to re-copy and reapply your custom translations to match any new placeholders or hooks.

    It’s also worth mentioning that if your translations were hardcoded, they might get bypassed after an update. For a more reliable approach, you can follow this guide for custom translations: WooCommerce Localization Documentation

    If that doesn’t resolve things, it would be super helpful if you could share your System Status Report. Here’s how to grab it:

    1. Go to WooCommerce → Status in your dashboard.
    2. Click Get system report, then Copy for support.

    If you’re seeing any errors, you can also check WooCommerce → Status → Logs and share any recent fatal error logs with us.

    Once you’ve got that info, feel free to paste it here in a code block or upload it to pastebin.com and send us the link—that’ll help us investigate more deeply.

    Looking forward to hearing back from you!

Viewing 15 replies - 1 through 15 (of 1,043 total)