Mahfuzur Rahman(woo-hc)

Hi @wpidl ,

Thank you for sharing the details! From the information provided, it seems that the error you’re encountering (Failed to load resource: net::ERR_BLOCKED_BY_CLIENT) is likely caused by an ad-blocking extension, such as Adblock Plus.

To test this, try the following:

• Open your site in an Incognito/Private tab, as most extensions are disabled in this mode by default.
• Alternatively, use a different browser or temporarily disable/uninstall the ad-blocking extension by right-clicking it near the URL bar and selecting “Remove from Chrome.”

Once the ad blocker is disabled, check if the issue persists. Let us know how it goes, and feel free to share any additional details!

Hi @fraom,

Thank you for following up! I’m happy to share that the issue has been fixed and will be included in the upcoming WooCommerce 9.5 release. Keep an eye out for the update, and once it’s available, upgrading to version 9.5 should resolve the problem.

Let us know if you have any further questions!

Hi @nubiesan,

I understand how frustrating it can be to deal with spam orders like this. To help prevent these, you can:

1. Enable the “Enable log-in during checkout” option in WooCommerce > Settings > Accounts & Privacy. This will require users to log in, adding a layer of security.

2. Use a reCAPTCHA plugin to block spam orders effectively.

These steps should help reduce or block unwanted activity.

Hi @kodej,

Thank you for reaching out! It looks like this topic is a duplicate of your other post here: https://www.ads-software.com/support/topic/where-is-the-company-field-in-checkout/

We’ve already addressed your query in that thread. To keep the forum organized and aligned with the guidelines, duplicate topics aren’t allowed. I’ll mark this thread as resolved and continue the discussion on the original post. Thank you!

Hi @kodej,

I understand how important the “Company” field is for your transactions, especially to ensure data is correctly passed to Authorize.net. This issue appears to be related to how the Divi theme is set up. I recommend reaching out to Divi support, as they’ll be in the best position to help you restore this field.

Thank you!

Hi @mohammedmalleck,

Thank you for the image!

Yes, the difference you’re noticing in the transaction fees is due to a 10% discount on Payment Processing Fees as part of a promotional offer. This is why the calculated fee is slightly lower than expected.

You can find more details about this promotion here: WooPayments Action Promotion 2023.

Let us know if you have any other questions!

Hi @velozsup,

The issue you’re describing could be related to your shipping zone or method settings. To assist further, could you please:

1. Share a screenshot of your Shipping Zone and Shipping Methods settings? You can use a tool like Snipboard.io to generate and share the screenshot.

2. Provide the site address where the issue is occurring so we can better understand the context.

Once we have this information, we’ll be happy to guide you further!

Hi @deyruby,

Thank you for reaching out!

The warnings and notices you’re seeing could be related to a plugin or theme conflict. To resolve this:

1. Please perform a plugin and theme conflict test by deactivating all plugins except WooCommerce and switching to a default theme like Storefront. Check if the issue persists.

2. If the problem continues, try recreating your shipping zones and classes by following this guide: https://woocommerce.com/document/setting-up-shipping-zones/.

If neither step resolves the issue, please provide the following details so we can investigate further:

? System Status Report: Go to WooCommerce > Status > Get system report > Copy for support.

? Fatal error logs (if any): Found under WooCommerce > Status > Logs.

You can paste the details directly here or use https://gist.github.com/ and share the link with us. Once we have this information, we’ll be happy to assist further!

Hi @gsng,

Thank you for the screenshot!

From the screenshot you’ve provided, it looks like the order status has already been updated to “Processing.” This indicates that the payment was successfully received, and the order is now being handled as expected.

If the issue reoccurs in the future, you may want to verify that any caching plugins or services aren’t delaying updates on your site.

Feel free to let us know if you have further questions or concerns!

Hi @missdjein,

Thank you for sharing your concerns.

The issues you’ve experienced with your Facebook/Meta account sound frustrating. When using the Facebook for WooCommerce integration, any account-related issues are typically managed by Facebook/Meta directly and shouldn’t affect your WooCommerce store itself.

If you’re considering reconnecting your store to Facebook, it’s generally safe to do so as long as your Facebook/Meta account is in good standing. If you’re worried, you might want to test the integration on a staging site first to ensure everything works smoothly without affecting your live shop.

For further peace of mind, you could also reach out to Facebook/Meta support to confirm your account’s status before reconnecting.

Let us know if you have specific questions about the integration itself. We’re here to help!

Hi @itsviney,

Thank you for the website link!

The issue you’re describing might be related to the Shipping destination setting. Please ensure you’ve selected “Default to customer shipping address” in the shipping settings. This ensures Local Pickup availability is based on the delivery address rather than the billing address. You can follow this guide to check and update the setting: https://woocommerce.com/document/configuring-woocommerce-settings/#shipping-settings.

If the issue persists after making this adjustment, could you please share the following details?

? A screenshot of your Shipping destination settings.

? Your System Status Report (via WooCommerce > Status > Get system report > Copy for support).

? Any fatal error logs (found under WooCommerce > Status > Logs).

You can either paste your response here or use https://gist.github.com/ to share a link.

We’re here to help further once we have these details!

Hi @wizardsrl,

Thank you for reaching out!

WooPayments doesn’t offer the option to customize the payment reference for bank transfers. The reference is automatically generated, including “WooPayments” followed by a unique identifier, and there’s no built-in way to modify it to include details like the order number or date.

If you’d like to see this feature in future updates, I encourage you to submit a feature request here: https://woocommerce.com/feature-requests/woopayments/. Your feedback is valuable and helps shape the direction of the plugin.

Feel free to reach out if you have any other questions!

Hi @tcgsalesaustralia,

Thank you for reaching out!

WooCommerce product galleries display only the images by default. If you’d like to add captions, you can follow this guide to add captions to your images in the media library: https://kinsta.com/knowledgebase/wordpress-image-caption/#how-to-create-image-captions-starting-from-the-media-library. These captions will show up when images are clicked and viewed in the lightbox.

If you’d like the captions to appear below the images in the gallery directly, you can explore the Gallery Captions for WooCommerce extension here: https://woocommerce.com/products/gallery-captions-for-woocommerce/.

Let us know if you have any further questions!

Hi @tcingenium,

Thank you for clarifying!

Since the issue involves managing translations across multiple languages, it appears to be related to how the Loco Translate plugin handles those strings. We recommend reaching out to their support team, as they’ll be best equipped to assist with ensuring the correct text displays in each language.

As this is not an issue with the WooCommerce Stripe Payment Gateway plugin, we’ll mark this thread as resolved. If you have any other questions or need further assistance, feel free to reach out.

Hi @wpexpert12,

Thank you for sharing the system report!

We couldn’t replicate this issue on our end, which suggests there might be a conflict causing this behavior. To identify the root cause, a plugin and theme conflict test would be the most effective next step. If it’s not possible to perform this test on the live site, we recommend creating a staging or local installation. This way, you can safely troubleshoot without affecting your live site.

Please let us know what happens!