shahzeen(woo-hc)

Hi there,
Thank you for reaching out to us about this.
I understand you’re experiencing some trouble with theme translations not applying as they should. I’m happy to assist you with this in the following:
The issue at hand arises from a recent update in WordPress (version 6.7), where the function that loads theme translations,?load_theme_textdomain(), isn’t functioning as expected. This is due to a timing conflict with how WordPress loads translations just-in-time, which is part of recent enhancements meant to improve performance and efficiency.
Here’s what you need to know:

• What’s Happening?When translations are loaded, the timing of these loads is critical. In WordPress 6.7, changes caused translation loading to happen at a different point which led to translations not applying to themes if not loaded in sync with WordPress’s new timing.
• Possible Workaround:As an immediate solution, developers have been using a workaround that alters when translations are loaded. This involves adjusting from using the?init?action to the?after_setup_theme?hook, as well as additional adjustments like resetting certain cached translation entries manually. (Reference) — This level of customization is outside of our WooCommerce plugin support scope, so we would not be able to assist you with this workaround. We appreciate your understanding.
• You may consider reverting WordPress version if possible. (Please reach out to your host about this option if you are interested.)
• Loco Translate is a popular plugin that also works to translate text string, However, Loco Translate may not be sufficient enough to solve this issue since this might depend on how the theme files are handling translations. But we recommend checking Loco Translate documentation,?their recent announcement, and?their public forum for any guidance.
• Long-Term Fix:The good news is that the WordPress core team is actively addressing this in the upcoming version 6.7.1, as reported in their development tracks. They have a patch ready that re-attempts to load translations effectively and resolves these timing issues. See the progress and discussion on this issue here:?core.trac.www.ads-software.com/ticket/62337

I understand how such issues might affect your website’s functioning, and while this can be inconvenient, the development team is making sure the fix is tested thoroughly before release.
Here is also Woo community discussions you might keep an eye out for: www.ads-software.com/support/topic/translations-broken-in-woocommerce-after-wordpress-core-upgrade-to-6-7/
We are very sorry your business is impacted by the latest release. Rest assured, an official and stable fix is on the horizon.
Thanks again for checking in with us.

Hi there!

I’ve seen that many users have encountered the same issue, where the free shipping method appears even though the minimum limit hasn’t been reached. All of them were able to resolve the issue by adding the minimum amount without any commas (“,”) or dots (“.”).

Since you mentioned that you added the amount as 100, just to confirm, has your issue been resolved by entering the minimum amount as 100 (without a comma or dot)? The amount will indeed revert to 100,00 after saving the changes, but sometimes using a comma or dot can cause this issue.

If you’re still facing the problem after entering the amount as 100, please send us a message, and we’ll be happy to assist you further in fixing the issue.

Hi there!

I tried to replicate the issue on my test site, and I can see the button styles are appearing fine on our end. Additionally, the classes you mentioned are not appearing on my test site, but the buttons still look fine.

For testing purposes, could you please activate a default WordPress theme like Storefront or Twenty Twenty-Four and check if you’re still facing the issue?

We suggest changing the theme because if the issue is related to the code you’re referring to, it should create issue on all sites, including my test site.

Let me know how it goes!

Hi there!

It sounds like you’re on the right track by testing the staging site with Elementor and WooCommerce reinstalled. Monitoring the site for a few more days is a great approach to ensure the issues don’t resurface.

If you encounter the issue again, please don’t hesitate to reach out to us. We’ll be happy to investigate further and help resolve it as quickly as possible.

Hi there!
It seems that the plugin has an option to hide the PayPal button on the checkout page. Here are instructions to guide you on how to hide the PayPal button on specific pages or on all pages: WooCommerce PayPal Payments Documentation.

For more details or further assistance, I suggest contacting the plugin support team here: WooCommerce PayPal Payments Support.

Thank you

Hi there!

I understand your concern. I’ve tried to replicate the issue on my test site and was able to reproduce it with the latest version. However, rolling back to version 9.3.3 resolved the issue.

I noticed that this bug was reported here: https://github.com/woocommerce/woocommerce/issues/52931, but it was closed by our developer. I suggest leaving a comment on that thread so they can see that others are experiencing the same issue and either reopen the bug or provide an alternative solution.

In the meantime, if you want to remove the error, I recommend rolling back to version 9.3.3 to see if that resolves the issue for you.

Thank you!

Hi there!

You’re welcome! I’m glad the custom code is working as a quick fix for now. Since I wasn’t able to replicate the issue on my test site, this does suggest it could be related to your theme. To further troubleshoot, I recommend temporarily activating a default WordPress theme, such as Storefront, and checking if the issue still occurs. This will help determine whether the issue is related to WooCommerce itself or the theme you’re using.

If the issue resolves with the default theme, it’s likely a theme conflict, and reaching out to your theme provider will be the next step.

Thank you for your cooperation and understanding

Hi there!

Thank you for sharing the system report. From what I can see, everything appears to be working fine. I also noticed that you mentioned speaking with the Gift Card plugin support team, who suggested increasing the PHP max size.

To clarify, has the issue been resolved if you deactivate that plugin?

The issue you’re facing seems to be related to a plugin conflict or a theme issue. Have you tried running a conflict test? Does the issue persist when only WooCommerce and WooPayments are active?

For more details on how to run a conflict test, you can refer to this guide: How to Test for Conflicts.

Let me know how it goes!

Hi there!

Apologies for the confusion. I understand you’re looking for help adding the shippingDetails and hasMerchantReturnPolicy fields to your shop. Currently, these fields can only be added through custom code.

Please note that we don’t provide support for customizations. If you require more in-depth assistance, I can recommend?WooExperts?and?Codeable.io?as options for getting professional help. Alternatively, you can also ask your development questions in the??WooCommerce Community Slack?as custom code falls outside our usual?scope of support.

Additionally, I can see that this issue has already been reported by another user here: https://github.com/woocommerce/woocommerce/issues/41060
https://github.com/woocommerce/woocommerce/issues/41061

Thank you for cooperation and understanding

Hi there!

Thank you for sharing the SSR. Everything appears fine in the SSR from what I can see.

To assist you further, could you please create a staging environment for your site for testing purposes? On the staging site, activate a default WordPress theme like Storefront or Twenty Twenty-Four, along with only the WooCommerce plugin. Then, try placing a test order to check if the email issue persists.

This process will help determine if another plugin on your site is causing the issue. Currently, we’re unable to replicate the problem on our test site.

For detailed instructions on how to perform a conflict test, you can refer to this guide: How to Test for Conflicts.

Let me know how it goes!

Hi there!

Thank you for reaching out! I understand how important it is to maintain consistent order numbers when switching plugins.please note that we only provide support for Woocommerce core features. Since you’re using the WooCommerce Order Status Manager plugin for this functionality, I recommend contacting the plugin developer directly. They’ll be able to provide the best guidance on migrating to another solution while preserving your custom order numbers.

If the new plugin you’re considering also supports importing or preserving custom order numbers, the developer of that plugin may have specific instructions for the migration process as well.

Thank you

Hi there,

Thank you for sharing the screenshot! From it, I can see that you’re trying to translate “Choose an option,” and it’s not working on your end.

However, I checked this product page: https://shopdoacademico.com/promovendo-o-cuidado-e-a-saude-na-comunidade-2/, and I can see that the translation is working fine, with “Choose an option” already replaced with the new text, as shown in this screenshot: https://go.screenpal.com/watch/cZXr6JnVyld.

Could you please confirm if your issue has been resolved, or are you still experiencing it? If the issue persists, could you share the URL of the product page where you’re seeing this problem? This will help us investigate further.

In the meantime, please try clearing your browser cache and let me know if that helps.

Hi there!

I understand your concern. I tested the above code on my site, and it’s not working correctly either. However, I was able to successfully change the text using the Loco Translate plugin, as demonstrated in this screenshot: https://go.screenpal.com/watch/cZXr6AnVy6g.

Could you please try using the Loco Translate plugin to update the text? If you prefer not to use the plugin and want a code-based solution, please note that we don’t provide support for customizations.

If you need more in-depth support or want to consider professional assistance for customization, I can recommend?WooExperts?and?Codeable.io?as options for getting professional help. Alternatively, you can also ask your development questions in the??WooCommerce Community Slack?as custom code falls outside our usual?scope of support.

Hi there!

I understand your concern. I was able to replicate the issue on my test site. However, the problem only appears when I navigate to WordPress Dashboard > Analytics or Dashboard > WooCommerce. The issue disappears when I return to the site dashboard.

It seems like a bug. I recommend creating a bug report on GitHub so our developers can investigate and potentially fix the issue in future updates: https://github.com/woocommerce/woocommerce.

Thank you!

Hi there!

I understand your concern. I’ve tried to replicate the issue on my test site and noticed the same error appears only when selecting the page number on the Product Categories page, while pagination works fine for Posts and Pages.

It seems like pagination isn’t working for product categories. Since we’re using WordPress’ default pagination, I suggest you create a ticket on the www.ads-software.com support forum and inform them about this error message. They may be able to assist you in resolving the issue.

In the meantime, you can access the pages directly by adding the page number to the URL, as shown in this screenshot: Screenshot link.

If the www.ads-software.com support team advises you to contact the plugin support, you can report the issue by creating a bug on the WooCommerce GitHub repository here: https://github.com/woocommerce/woocommerce.
Thank you