Jonayed Hosen (woo-hc)

Hi @bilalzhd,

Thank you for sharing the details about the steps you’ve taken. Since you’ve already performed a conflict test, let’s take it a step further to narrow down the cause:

• Please ensure that only WooCommerce and Square remain active during testing. Even if you’ve done this before, there might have been configurations or caching affecting previous tests. You can follow this detailed guide on how to perform a full conflict test: WooCommerce: Testing for Conflicts.
• Since not all customers are encountering the error, there could be browser or device-specific compatibility problems. Could you gather more details about which browsers, devices, or operating systems are affected? This information might provide additional clues.
• If you’d prefer not to test directly on your live site, I recommend creating a staging environment. The WP Staging plugin can help you set this up easily. This allows you to safely test changes without impacting your live site.
• I would also suggest reviewing your error logs if you haven’t done so already. Check your WooCommerce logs under WooCommerce > Status > Logs, as well as your server error logs, as they may reveal relevant errors related to this issue.

It would also help us to review your current System Status Report to gain more insight into your setup. You can find this report in your WooCommerce dashboard by going to WooCommerce > Status. From there, please select Get system report and then Copy for support.

Once we have more details, we can explore further troubleshooting steps.

Hi @ktakahisa ,

I’m sorry to hear about the issue with your WooCommerce site language switching automatically from Japanese (JP) to English (EN). I understand how frustrating this can be.

After reviewing your System Status Report, I noticed that your WooCommerce version is currently running on 7.8.2, which is quite outdated. This could potentially be contributing to the issue, as older versions may have unresolved bugs or compatibility issues.

To address this, I recommend updating to the latest versions of both WooCommerce and WordPress. As noted by @bentjh , updating their WordPress to 6.7 and WooCommerce to 9.4.2 resolved a similar issue they were experiencing.

Before updating, it’s always a good practice to:

• Back up your site. Use your hosting provider’s backup tool or a plugin like UpdraftPlus to ensure your site is protected.
• Test in a staging environment: If possible, create a staging site to test the updates. You can use the WP Staging plugin to create a staging environment. This allows you to confirm that everything works as expected without impacting your live site.

Once you’ve updated, check if the issue persists. If it does, it might help to investigate any active plugins or customizations that could influence language settings.

Please let us know how it goes after updating.

Hi @apositivetwist ,

By default, WooCommerce displays all available shipping rates if the items in the cart qualify for multiple options, such as free shipping and flat rate. This is why both rates are showing at checkout if the cart meets the conditions for free shipping.

However, @seank123 has provided a great suggestion to resolve this issue. Adding the recommended code snippet to your site will automatically hide the flat-rate option when free shipping is available. If you’re comfortable with editing your site’s code, you can add this snippet to your child theme’s functions.php file.

Alternatively, if you prefer a safer method, you can use a plugin like Code Snippets to add the code without directly editing your files.

Please check and let us know if this helps you.

Hi @vaka2vaka,

I came across this thread and noticed that the user is experiencing a similar issue.

After reviewing your error log again, it seems the issue persists even after deactivating all plugins but was resolved by rolling back to version 9.3.3. This indicates the problem might be stemming from specific WooCommerce settings in the latest version. The content/plugins/woocommerce/src/Packages.php error points directly to WooCommerce, while the other errors are related to third-party plugins, which suggests they aren’t contributing to this issue.

It’s possible the issue is tied to your shipping configuration. Could you temporarily disable all major shipping options and only retain the Rest of the World shipping rates to see if the issue is resolved? Additionally, try tweaking other potentially related settings and then recheck the issue.

However, if this resolves the error but the search functionality issue persists, it will give us a better understanding if this the reason that blocking the plugin search functionality.

If you prefer not to test these changes on your live site, you can use the WP Staging plugin to create a staging environment. This allows you to safely test settings without affecting your live website.

Please try this out and let us know how it goes so we can investigate further.

Hi @cherrycoding ,

Thanks for sharing the screenshot. It is indeed not showing any Facebook sync scheduled.

There is something preventing the action from reacting. Can you please try deleting the plugin, reinstalling it, and reconnecting with your Facebook account again to see if this solves the issue?

Please make sure to perform a manual sync again to re-trigger the action hook.

However, it’s important to note that out-of-stock products in WooCommerce are not synced to Facebook by default. This means that when a product’s stock reaches zero, the update isn’t automatically reflected on Facebook. This can cause discrepancies where products appear in stock on Facebook but are actually unavailable in your store.

For more details, please refer to this documentation: https://woocommerce.com/document/facebook-for-woocommerce-products-are-not-displaying-in-facebook-shop/#cause-of-out-of-stock-products-not-showing

I hope this helps.

Hi @advps ,

I’m sorry to hear about the issue you’re experiencing. The error message “Uncaught TypeError: window[o] is not a function” usually occurs due to conflicts between the plugin’s JavaScript and other elements on the site.

Since you mentioned that the staging version of the website is also affected, even with caching disabled, I’d like to confirm: Is the WP-Rocket plugin activated, even though caching is disabled? If so, there could be an issue with WP-Rocket and its interaction with Google Analytics and Google Ads tracking. This issue is often caused by delays in JavaScript execution.

You can find more information about this issue and possible solutions in this article: WP Rocket – Google Analytics & Google Ads Tracking Issues.

If this doesn’t resolve the issue, I’d recommend temporarily deactivating all plugins except WooCommerce and the Google Analytics Integration plugin. Additionally, please switch to a default WordPress theme, such as Storefront, to see if the issue persists. If there’s any custom code added to your site, please remove that as well.

Please check it out and let us know if this is the cause of the issue.

Hi @dhanababums ,

I’m sorry to hear about the issue you’re experiencing. It looks like the order status changed. The “Processing” status fails when customers pay via the PayU payment gateway, but it works fine with default Cash on Delivery (COD).

To help us investigate further, could you please share the order notes with us? It will help us gain more insight. Additionally, does this issue happen with all orders when customers use the PayU gateway, or is it specific to certain orders? Have you noticed any patterns, such as specific countries being affected?

If you haven’t already, could you please share a screenshot of the issue? If you don’t have a screenshot tool, you can use Snipboard.io to easily share it.

Also, have you performed a full conflict test? This involves deactivating all plugins except WooCommerce and the PayU payment gateway plugin, and switching to the default Storefront theme. You can follow this guide to perform a conflict test: How to Test for Conflicts.

It would also be helpful for us to review your current System Status Report. You can find this report in your WooCommerce dashboard by going to WooCommerce > Status. From there, click Get system report and then Copy for support.

If you’ve come across any fatal error logs related to your PayU payment plugin or orders, please share them as well. You can find these logs under WooCommerce > Status > Logs.

Once you’ve gathered this information, please paste it into a code block in your reply or use Pastebin to share the link with us.

Please check and let us know how it goes.

Hi @bsmart10 ,

I understand you’re having issues with exporting your product list in WooCommerce. Even if you’ve uploaded your products sorted by stock code, the default WooCommerce CSV export doesn’t retain that order.

However WooCommerce’s built-in export function doesn’t offer advanced sorting options. If you have coding experience, or access to a developer, you can create a custom export function that retrieves products sorted by stock code. This can be done by using WooCommerce’s REST API or custom SQL queries to fetch and export the data in the desired order.

I also looked for plugins that could achieve this functionality but, unfortunately, couldn’t find one that fits your needs.

I hope this helps! Let me know if you need further assistance.

Hi @deelicewp ,

I’m sorry to hear about the challenges you’re facing with your WooCommerce store, particularly with the disabled “Save Changes” button and issues editing products.

Let’s work through some steps to resolve this:

• Please Ensure you’re using WordPress’s default jQuery version. Remove any custom code or plugins that modify jQuery, as manual updates can lead to conflicts.
• The error Uncaught TypeError: e(...).iris is not a function suggests a conflict with the Iris color picker, which relies on jQuery. Can you please deactivate all plugins except WooCommerce and switch to a default theme like Storefront to identify any conflicts.
• Confirm that both WordPress and WooCommerce are updated to their latest versions to benefit from recent fixes and improvements.
• Clear your browser’s cache and any server-side caches to ensure you’re loading the most recent scripts.

If the issue persists, could you please share a screenshot showing the issue on your end? If you do not already have a screenshot tool installed, Snipboard.io can be used to easily share screenshots.

Additionally, it would be helpful if you could share your current System Status Report so we can gain more insight into your setup. To find this report:

1. Go to your WooCommerce dashboard.
2. Navigate to WooCommerce > Status.
3. Click on Get system report and then select Copy for support.

If there are any fatal error logs, please share those as well. These can be accessed under WooCommerce > Status > Logs.

Once you’ve gathered this information, please paste it into a Code block in your reply or use pastebin.com and share the link with us.

Please check and let us know.

Hi @mervyntsao ,?

I understand you wants to separate the “Login” and “Register” functionalities on his your my account page, so first-time visitors see only the registration form and returning customers see only the login form

This type of request is a bit outside the support scope we provide here, as it involves custom code and core file modification. However, you can review our support policy, and we have a variety of resources that might help point you in the right direction!

For hands-on guidance, we recommend exploring our WooCommerce Developer Portal, which offers detailed documentation and resources to help you build and refine custom solutions. This is a great place to find information about hooks and filters, like the one you’re using.

If you’re looking for professional support, Codeable.io or one of our WooExperts can connect you with vetted developers who specialize in WooCommerce customizations. They can assist with tailoring the code to meet your specific requirements.

Additionally, you might want to share your query in one of the following channels, where experienced developers and the WooCommerce community can assist with customization questions:

• WooCommerce Advanced Facebook Group
• WooCommerce Developer Slack Channel

I hope this helps point you in the right direction!

Hi @legsammen,

I’m sorry to hear that the mini cart isn’t working as expected.

When I checked your website (https://www.legsammen.dk/), the mini cart seems to be functioning as intended, as shown here:

This might be a caching issue. Could you try clearing your browser cache? You can follow this guide: How to Clear Your Cache in WordPress. Alternatively, you could replicate the issue in an incognito browser window to see if the mini cart displays as expected.

If the issue persists, could you send us a screenshot or screen recording of what you’re seeing on your end? If you don’t have a screenshot tool installed, you can use Snipboard.io to easily capture and share screenshots.

Please give this a try and let us know how it goes!

Hi @joaquin2019 ,

Thanks for reaching out! It looks like you’re using a plugin to customize the permalink structure of your product URLs. I tested accessing the product without the /product slug by using the /CS slug, and it successfully redirected to the correct URL, as shown here:

This suggests that the plugin is generally handling redirection rules correctly. However, the issue may stem from how the plugin manages specific redirection rules after modifications.

From reviewing the plugin documentation, it seems that advanced features like 301 redirects are only available in the premium version and enabling this feature has been known to resolve similar issues in some cases.

To resolve this, I recommend raising the issue in the plugin’s official support forum: Plugin Support Forum. Their team or community should be able to provide guidance tailored to your setup.

I hope this clarifies things! Let me know if you have further questions.

Hi @musachi,

It looks like the URL parameter ?resize=100%2C100&ssl=1 is commonly generated by Jetpack’s Site Accelerator feature. To determine if this is causing the issue, you can temporarily disable the Site Accelerator and recheck in an Incognito browser window or after clearing your browser cache.

To disable the Site Accelerator feature:

1. Navigate to your WordPress dashboard.
2. Go to Jetpack > Settings > Performance.
3. In the Performance & speed section, toggle off the Enable site accelerator option.

Once disabled, check your image URLs. If the resize and ssl parameters are no longer being added, it confirms that Jetpack’s Site Accelerator was modifying your URLs.

If this resolves the issue but you still want to keep the Site Accelerator active for its other benefits, you can prevent it from resizing images by adding this custom filter code to your theme’s functions.php file or you can use Code Snippet plugin:

add_filter( 'jetpack_photon_override_image_downsize', '__return_false' );

This filter ensures Jetpack’s Photon (the image CDN component) uses the original image sizes instead of resizing them. For more details, you can refer to Jetpack’s developer documentation.

Please give this a try and let us know if it helps!

Hi @bledijaupaj ,

I’m sorry to hear you’re encountering the “ChunkLoadError: Loading chunk 4940 failed” message on your WooCommerce site. This error usually occurs when the browser is unable to load a specific JavaScript file, which can disrupt your site’s functionality.

This issue could be related to cached files in your browser or temporary data (transients) stored by WooCommerce. Clearing your browser cache and WooCommerce transients from your dashboard (under WooCommerce > Status > Tools) often resolves the problem.

If your site uses a CDN, it might also be a delivery issue. Temporarily disabling the CDN can help you identify if it’s the cause. If so, clearing the CDN’s cache or adjusting its settings may resolve the error. Another aspect to check is your folder permissions. Directories should typically be set to 755 and files to 644. Incorrect permissions could prevent files from loading correctly.

We’ve seen a similar issue discussed in this thread, where the error was caused by security rule settings in the .htaccess file. I recommend reviewing your file settings to ensure they’re not inadvertently blocking access to the JavaScript files.

Please try these steps and let us know how it goes!

Hi @userweb ,

Thank you for reaching out! Typically, invoices for the previous month are generated on the 10th day of each month. You should be able to access the monthly invoice reports for November on December 10th.

I understand you’ve encountered an issue with downloading other invoices, as it’s requesting a VAT number. Could you please provide a screenshot of how this appears on your end? This will help us better understand your current position and assist you more effectively. If you don’t already have a screenshot tool, you can use Snipboard.io to easily capture and share screenshots.

Please take a moment to check and let us know so we can assist further.